Warp Stabilizer bug in new Premiere update

Made the mistake of updating mid-project. Now Premiere warp stabilizer isn't working and causes rendered frames to flicker to black. Tried the stabilizer on new projects with same results. Contacted tech support and they said "this is being rushed to get fixed". Anyone else having this problem?

Mark -- No need to test for me, that scenario perfectly describes my original problem.
And from the System Information report:
Intel Iris Pro:
  Chipset Model:    Intel Iris Pro
  Type:    GPU
  Bus:    Built-In
  VRAM (Dynamic, Max):    1536 MB
  Vendor:    Intel (0x8086)
  Device ID:    0x0d26
  Revision ID:    0x0008
  Displays:
Color LCD:
  Display Type:    Retina LCD
  Resolution:    2880 x 1800
  Retina:    Yes
  Pixel Depth:    32-Bit Color (ARGB8888)
  Main Display:    Yes
  Mirror:    Off
  Online:    Yes
  Built-In:    Yes
DELL P1913:
  Resolution:    900 x 1440 @ 60 Hz
  Pixel Depth:    32-Bit Color (ARGB8888)
  Display Serial Number:    75VDV3211D6U
  Mirror:    Off
  Online:    Yes
  Rotation:    90

Similar Messages

  • Premiere Pro CC's Warp Stabilizer BUGS...see for yourself. (7.0.1 & 7.1)

    I'd love to hear from Adobe Staff on this one. Hopefully they can focus on fixes over features for the next update, especially for one it's most touted effects.
    Warp Stabilizer works great at stabilizing clips in Premiere Pro CC...but I'm beginning to learn that it's quite buggy. The two bugs below simply cripple the user experience when you use the effect a lot like we do. Here's a link to a sample project with just 2 clips (around 1 minute in length each) on two separate timelines with each clip stabilized using the Warp Stabilizer effect. It's only a sample/test project meant to show the issue which can be MUCH larger in a longer/bigger project. Relink to any longer media and you'll quickly see what happens when you have multiple warp stabilizers applied to a Premiere Pro CC project and how problematic it can be.
    https://dl.dropboxusercontent.com/u/105331144/Warp_Stabilizer_SAMPLE_Project.prproj
    See for yourself.
    Two VERY Annoying BUGS and One Unfortunate Feature:
    BUG #1: (It affects 7.0.1 and the new 7.1 Release/Update)
    1) With GPU Acceleration Enabled and both sequences open, once the timeline render bar has turned yellow, hit save.
    2) Now toggle to the 2nd sequence and you'll notice a delay/freeze as the render bar switches back to red and then yellow again.
    3) Now toggle back to the other sequence and you have the same thing occur. Then, you can toggle back and forth with no delay...until...the project saves (or auto-saves) again...and then the delay/freeze will happen all over again.
    4) Side Note: Even when you right-click on the sequence in the Project window, there's a delay. Right-click on a sequence with no Warp Stabilizers and the drop down list pops up immediately.
    What's the Big Deal?: When you have tons more warp stabilizer effects applied to multiple sequences, not only does it take a while to save, but when it does, you are forced to wait while Premiere Pro freezes momentarily. This affects AUTO-SAVE too!!! The more warp stabilizers, the longer the wait. Our sequences have delayed up to 30-40 seconds depending on how much we've used warp stabilizer in each sequence. Imagine if you have Auto-Save set to every 30 minutes or less, well that means that every 30 minutes or less you'll be forced to stop while premiere freezes up for 30-40 seconds or so (depending on how much this effect is used). Other effects do NOT have this issue.
    BUG #2: (It affects only the new October Release/Update of Premiere 7.1...this issue is NEW and does NOT occur in 7.0.1!!!)
    1) Take the above project into Premiere Pro CC 7.1 (again, this does NOT occur in the previous 7.0.1 release) and hit FILE>EXPORT>Media.
    2) You'll notice a delay while the EXPORT SETTINGS popup opens.
    3) Toggle to different "FORMATS" in the export settings window and there's more delays every time the format is switched.
    What's the Big Deal?: Again, this is a small sample project. When you have a much bigger project with lots more Warp Stabilizers applied to many more clips this "delay" can extend up to several minutes!!! Yes, on a recent project over an hour with MANY warp stabilizers applied to lots of clips, it took 7 minutes for the Export Settings window to pop up after hitting EXPORT>Media. And there was about a one minute delay now when switching formats. This occurs whether GPU Accleration is enabled or not. It ONLY occurs on Premiere Pro CC 7.1
    UNFORTUNATE FEATURE #1:
    We obviously use Warp Stabilizer A LOT. It's a great effect. The above bugs cripple the user experience. This last issue isn't a bug, but rather a default setting on Premiere Pro's warp stabilizer that should be changed. Within the settings of Warp Stabilizer there's a section called "Method". The default setting is "Subspace Warp". That sounds pretty cool. But in practice, and we have had lots of practice (eg. THOUSANDS of clips stabilized in just the last few months alone (no exaggeration)), we've found that switching the default method to "Position, Scale, Rotation" is a MUCH more effective way to stabilize a clip. Most of the time it cuts down on that "wobble" that you might see in complex moving clips...but more importantly, 9 out of 10 times it crops the video either the same or less than when you use the default method. By "crops less" I mean that the "Auto-Scale %" is less. Of those 9 times, I'd guess 7 or 8 of them would crop in on the video less while the other 1 or 2 times there would be no change to the Auto-Scale %. Less scaling = better.
    What's the Big Deal?: Well, as cool as Subspace Warp sounds, our numbers don't lie. Again, we use this effect on HUNDREDS of clips every week. When you have to go into hundreds and hundreds of clips every week and keep switching the setting so the effect will work better, it gets old real fast. We end up wasting so much time doing this but it's worth it because the results are undeniable. Why not create a CUSTOM PRESET???! Well, that'd be nice if it worked...but it doesn't. The problem with a custom preset like that is that when you drop it on a clip, it doesn't activate/analyze the clip automatically so you have to manually go into the settings and hit analyze which negates any time saved. It's be great if the default "method" was simply changed to Position, Scale, and Rotation. Or at the very least, it'd be great if one could create a custom preset that would automatically activate/analyze the clip it's dropped on (just like the original effect does). 
    (BONUS FEATURE: It'd also be nice to have the ability to set a "max scaling %" too so you never crop in more than a preselected amount...but first things first...fixes over features.)
    NOTE: I'm on a 2011 suped up iMac running OSX 10.8.5

    [r]Evolution wrote:
    Would it help to  Render these Warp Stabaliized clips instead of leaving them in the sequence w/ the Effect applied?
    Any way to "Batch" Warp Stabalize your media before editing so the effect is not needed during the edit?
    Sounds like you guys could benefit from having your shooters use a "Stabalizer".
    Thanks for the rendering tip rEvolution. Rendering the clips does help with BUG#1, however, I'm not sure if it would truly save us any time because of the constant need to render and rerender tons of very short clips with this effect as we make adjustments to the edit. Warp Stabilizer is GPU Accelerated so playback is really smooth which is great but why does saving a project have any effect on this and cause it to freeze up? And then it works great...until the next time the project is saved. Using any other effect, there is no issue (that I've found) when a project is saved or auto-saved.
    Rendering unfortunately has no effect on BUG#2 in Premiere 7.1 (again, this bug/issue did not occur in Premiere 7.0.1)
    Regarding "batch" stabilizing...I'm not entirely sure what you mean. We do stabilize dozens of clips at a time before editing because it's imperative for us to know which clips (the sections we've pulled) will stabilize effectively. And then once the longer edit is complete we end up pulling all the best shots from that long sequence and copy/paste it to another sequence to make a 2nd shorter edit.
    To say we've gone back and forth about the use of stabilizers would be an understatement. The fact is that we've spent almost 4 years creating a unique way to shoot based almost entirely around the effectiveness of warp stabilizer. It's taken years of trial and error but our style of shooting effectively allows us to mimick and thus replace the need for stabilizers, sliders and cranes. The extra freedom allows us to get MUCH more varied coverage of live events. It's different, I know, but it's fun and rewarding having a unique style. Granted the extra work is passed on to the editing side, but it's worth it IMO especially if these issues were addressed/fixed.
    Regarding the "unfortunate feature" I mentioned, I would be satisfied knowing the default method works great for others if one were simply able to apply a custom preset of the clip with the adjusted method and it activated automatically and began analyzing the clip without the need to manually go into settings and hit analyze. That would be nice.
    Thanks again for your input.

  • Premiere Pro CS6 - Warp Stabilizer BUG causes project to crash

    Hi!
    Sometimes Warp Stabilizer causes Premiere CS6 to crash. I found out what steps cause this so hopefully a fix can be made in an update soon:
    1) Add the WARP STABILIZER to a clip. It Analyzes and then is applied to the clip.
    2) TOGGLE OFF the effect in the effect controls window
    3) Adjust the clip duration and RE-ANALYZE while the effect is TOGGLED OFF still and Premiere crashes.
    Happens every time. BUG Report was filled out.
    (If the effect is toggled ON when you RE-ANALYZE it, everything works okay.)
    So why not just not do this? Well, I usually don't but sometimes in the middle of working with hundred of clips I toggle on/off the effect to check certain things and then leave it off. If the clip is adjusted later or I come back and try to click ANALYZE again while the effect is toggled off, everything crashes.
    That's the pop up. If Premiere doesn't allow for you to re-analyze a clip while the effect is toggled off, then the ANALYZE button should not be active or at least a popup saying "Cannot Analyze this clip while it is toggled off". Instead Premiere crashes and upon reopening the project you are forced to rename the project which fortunately is usually fully recovered.
    Running 6.0.2 on a suped up 2011 27" iMac with 16gb ram and AMD 6970M 2gb video card.

    I know I'm piggy-backing on an old post here, but I've just had real issues with a similar thing on Mac. Unfortunately, my Premiere CS6 is crashing and becoming totally unresponsive whenever I simply apply the Warp Stabilizer. The moment I drop it on my clip, BLAM! I get that same pop up you posted. I click 'OK,' and then nothing. Just beachbal of death until I force quit. What's more annoying is that, not only has the camera operator made the stabilizer essential, but I've been using it for the past week with no issues up till now.
    At first I thought I was overloading Premiere by dropping the effect onto two clips at the same time. But I tried it one at a time and had the same problem. My recovery project files seem to be ok, but that's not even nearly the point. I simply can not use a great and essential tool. Help?

  • Bug in new OS6 update

    Just wondering if anyone else has a bug in the new os6 update where when updating apps they disappear from the home screen? already tried unhiding and deleting and reinstalling.

    Mark -- No need to test for me, that scenario perfectly describes my original problem.
    And from the System Information report:
    Intel Iris Pro:
      Chipset Model:    Intel Iris Pro
      Type:    GPU
      Bus:    Built-In
      VRAM (Dynamic, Max):    1536 MB
      Vendor:    Intel (0x8086)
      Device ID:    0x0d26
      Revision ID:    0x0008
      Displays:
    Color LCD:
      Display Type:    Retina LCD
      Resolution:    2880 x 1800
      Retina:    Yes
      Pixel Depth:    32-Bit Color (ARGB8888)
      Main Display:    Yes
      Mirror:    Off
      Online:    Yes
      Built-In:    Yes
    DELL P1913:
      Resolution:    900 x 1440 @ 60 Hz
      Pixel Depth:    32-Bit Color (ARGB8888)
      Display Serial Number:    75VDV3211D6U
      Mirror:    Off
      Online:    Yes
      Rotation:    90

  • Warp stabilizer not working with latest update

    After latest update (updated 10/10) Warp stabilizer stopped working. Already stabilized clips in project show black / transparent in preview, besides small area left or right upper corner. Changing Video rendering from GPU acceleration to Software makes stabilized clip come back... however now it creates flickering to all stabilized clips. Deleting "Warp stabilizer" effect from clips removes flickering. What might help?
    Editing with Lenovo Thinkpad, i7 2.4ghz, 8GB, Intel HD integrated graphics
    Message was edited by: Mikko Lehvilä
    Added picture

    I'm experiencing a similar thing.
    2014.1 (October Update) on OSX 10.9.5
    For me, Warp Stabilizer is working on regular clips. But when I try to apply it to a nested sequence, the result is exactly as you describe. Video is fully visible while analyzing and stabilizing, but once stabilized it's just black (actually, I did some tests, and it's actually transparent).
    I can replicate this even with codec-agnostic footage like bars & tone.
    Adobe - what's up here?
    Edit: sometimes I get the top-left-corner thing, and sometimes it's completely blank. Trying to track down the pattern.

  • AE Warp Stabilizer (C5.5) Vs. Premiere Pro Warp Stabilizer(CS6)

    Was wondering what folks experience was in CS6 with WS in Premiere Pro ?
    Is it the same WS as in CS 5.5 in AE ? Has it been improved ?
    My expereince with WS in CS5.5 (AE) has been very hit and miss. Some scenarios it works very well, others it tends to "warp" the footage so that it appears to be a disco scene on speed.
    Any CS6 folks care to chime in ?
    Thanks.

    It seems that Premiere CS6 stabilizer is identical to AE CS5.5
    Sometimes it helps to use Detailed Analysis, but in my case it did not work. I have a boat in the storm because stabilizer hooked to the moving object. I would like Adobe to add the ability to mark some key points, because full auto is not a professional style of work. However, even if I'll do a feature request it will not be implemented until CS12. I would be very surprised to see some improvements in CS6.5/CS7, but it is not Adobe style. This issue is known for 2 years from now and it is sad that they think about features quantity, but not feature quality (in terms of functions).
    Sorry for being emotional, but 2 bugs for one project is too much for me for today.
    However, I would like to thank them for adding Adjustment Layers. Saves time a lot.

  • Warp Stabilization not working on Premiere Pro CS6 or After Effects CS6

    I've imported a 30 second clip both on Premiere Pro and After Effects. I am using CS6. I used a Canon 600D and my footage is 23.976 and 24fps. I've tried both frames to see if it made a difference. All what happens is that it says step 1 out of 2. It finishes and tells me to analyze again. It doesn't actually make it to step 2 so my footage doesn't change and its getting frustrating. No idea what im doing wrong. HELP PLEASE?

    As Rick says, it looks like you didn't update all of your software.
    What version of Premiere did you have before?
    What version of AE did you have before?
    What version of Premiere do you have now?
    What version of AE do you have now?
    Exact version numbers down to the last decimal, please.
    In the future, I'd suggest NOT updating in the middle of important projects.

  • Clips from Panasonic ag-ac160 has unsupported compression type with new Premiere update

    Updated Premiere Pro and now my Multicam project is not supporting the files from my Ag-ac160 camera. The files from the Canon 5d work fine but won't load the others. I am going to do a system restore until this is fixed.

    Took the advice of another reply and everything works fine now.
    Empty Media Cache database in the Preference
    Rename folder the files are in and relink.
    See if that will work.

  • Premiere CC 2014.1 bugs in new UI

    Is anybody noticed that bugs in new Premiere UI? The first I noticed is when i use bezier curves on audio in track, the line is always strait. It shows curved when the line is near left end screen of timeline, and when you move the clip to the right then is strait again. The secound one is when i use audio effects on audio. The tab in wich is the EQ plugin is messed up and shows half of the plugin. Also the thumbnails in bins must be adjustable in much smaller size as it is now when the slider is all way down to smalest size. This new UI sucks because the fonts are too big when looked on 27" monitor.

    There is a known bug in the H.264-Bluray export. I assume it has nothing to do with your issue, but perhaps it will give you something to consider.
    https://forums.adobe.com/message/6848505#6848505
    It appears due to a malformed xmpses file. It creates a problem on import into Encore, and I think it should do the same upon import into Architect or it would be ignored entirely. The test is to delete the xmpses file and see if that avoids the issue.

  • Projects Not Opening with Multicam and Warp Stabilizer - "[..\..\src\TickTime.cpp-207]"

    Editing a sequence with multiple nested multicam clips and warp stabilizer, if I close Premiere and reopen it, it says "Premiere Pro has encountered an error. [..\..\src\TickTime.cpp-207]" repeatedly until killed by Task Manager. I have restarted the computer, cleared the media cache and deleted preferences. I can import the sequence into another project and continue editing but if I close PPro I have to create another project and import the sequence again or I get the same error. Help!

    Hi Kevin!
    That is great news. I had a feeling the issue would be gone in the Next PPro. The issue can be easily duplicated by following these steps in CS6:
    1) User warp stabilizer on several clips (like maybe 6 or more or so).
    2) Take two clips and nest them and sync them for multicam on the same timeline as the stabilized clips (NOTE: these two clips don't actually have to be sync'd...just grab any two clips, stack them on top of each other, highlight them both and right-click and choose "nest", then right-click again and "enable" multicam.
    3) Save project. Close project. Re-open project and you'll get the error.
    If you do that in the NEXT version, does the error come up? Also, just while I have you...if you go into the settings of Warp Stabilizer, what is the default "method"? Is it still defaulted to "Subspace Warp" or did they smarten up and realize the option "Position, Scale, Rotation" is actually MUCH more effeciet causing less wobble and less cropping of the video 90% of the time? Just curious.
    Coltom Media Productions,
    I feel your pain. What also stinks is that the error pops up again when you export (or I should say when you queue) up the project into AME. I originally thought the number of continues equalled the number of warps applied but that's not always the case. Although, the more warp stabilizers applied the more times you'll have to hit continue. It often goes in numbers divisible by four. Why do I know all this crazy, useless info...hours and hours of trying to "solve" the issue. Every project I do, every single week has more than 100 clips that are stabilized and multiple multicam sequences so I often have to hit "continue" on the error 300-400 times or more on EVERY project. Can't wait til the next version!
    To see more on this issue you can see the original post on it here (note that the staff has recently (and graciously) led the charge to help isolate and resolve the issue):
    http://forums.adobe.com/thread/956692?start=40&tstart=0
    And then also, it definitely made my "Top 15 list" here:
    http://forums.adobe.com/thread/1179004
    Good luck!!!...oh, one more thing...the project will open...you just have to keep hitting continue. Sucks, but again, hopefully it'll be resolved soon.

  • When is Adobe going to fix Warp Stabilizer?

    I asked this question back in February but I only got one reply. Warp Stabilizer may provide decent footage stabilization, but it is incredibly poorly coded, especially when compared to Mercalli Pro, or the Edius 7 Pro stabilizer, which I believe is a lite version of Mercalli Pro. One would think that since it was introduced at least 3 years ago (I can't remember if the first version it came with was CS6 or a previous one), Adobe would have troubleshot it and fixed its terrible performance. I mean, we're not talking about a stabilizer that is half as slow as Mercalli Pro. Warp Stabilizer is 14.5 times slower than Mercalli Pro. These are times for one minute of footage, the same footage in both NLEs:
    Edius Pro 7 Stabilizer: 29 seconds
    Premiere Pro Warp Stabilizer normal analysis and solving: 12 minutes 16 seconds
    Warp Stabilizer detailed analysis and solving: 14 minutes 28 seconds
    This is on a six core i7 3930k CPU with 32 GB of RAM and two GTX770 cards with 4 GB each (even though WP doesn't use the graphics card for analyzing and solving, only for playback)
    And the terrible analyzing and solving times are not the only problem. If you decide to run WP on a long clip, say 13 minutes long, even after the two hours that it takes to analyze and solve, the next time you open that project, be prepared to not be able to use Premiere for who knows how long. I say who knows because about 30 minutes ago I opened Premiere, loaded the project, and it froze completely when it was loading the footage files. For the last half hour, Premiere has been stuck with the spinning circle mouse pointer. Task Manager shows that Premiere has zero CPU usage and about 3 GB of RAM usage. So it's doing nothing at all, just frozen because Warp Stabilizer is one of the worst coded pieces of software not only from Adobe, but from any company.
    Putting aside the terrible analyzing and solving times, and the eternal wait next time you load the project, there's the fact that as soon as you use WP on a few clips, or on one long clip, saving times are unbearably slow.
    So I'm just asking, what makes a company with the huge resources Adobe has, not only launch a plugin that performs so terrible, but also doing nothing to fix it for three years or more?

    In this case, yes, I have a 13 minute long take that I have to stabilize. However, the original footage clip is a few minutes longer, so I'm not trying to stabilize the full clip, only most of it.
    I could spend a lot of money on the plugin, but I usually don't have a lot of footage that needs stabilization. Besides, I already have the plugin that came bundled with Edius 6, so I just use that when I need to. However, since Adobe advertises Warp Stabilizer as part of Premiere, and the plugin is absolutely dreadful, it seems to me that it's false advertising. I would much rather use WP in my Premiere project rather than having to load the footage in Edius and then export to a gigantic file to avoid losing picture quality.
    As for drive space, I have two 3 TB very fast hard drives that have plenty of empty space. Besides, Mercalli Pro in Edius analyses and solves this long clip in about ten minutes, as opposed to the over two hours WP needs for the same clip. In fact, in Premiere I only applied WP to part of the clip, when in Edius I loaded the original AVCHD clip so I can just do a replace in Premiere and have the same ins and outs.

  • Precomposing & Cropping & Warp Stabilizer? *Beginners Question*

    Hi guys,
    I'm new to AE and have been trying to follow instructions from this link (http://www.sinusdigitalus.de/2011/05/06/my-first-test-with-the-new-adobe-cs55-warp-stabili zer/)
    I've taken out the important bit here -
    "i´ve imported my sequence and applied the warp stabilizer on it. the first instance of the stablilizer was to stablize only the movement of the position, scale and rotation with a crop but with no rescale to keep the image quallity. i´ve precomposed the shot and resized the comp with the new dimentions of the shot after the crop. on this i applied a new warp stabilizer and this time i´ve stabilized the perspective also with crop but no rescale. again precomposing and rescaling the comp to the new dimensions. then i applied a third warp stabilizer on this new comp and did it again. this time with the subspace stabilization."
    - As he mentions at the begining, it's not an indepth tutorial so where I'm tripping up is the precomposing and cropping.
    I'm trying to stabilise a jpeg sequence using this guy's method (he passes it through Warp Stabilzer 3 times).
    When I hit the Precomopse button it gives me 2 options and a box to tick whether or not to open new composition, which ones do I pick? And when that's done, how do I crop it so it's applied to the whole jpeg sequence before I use Warp Stabilzer agiain?
    Thank for your help.

    Not tried it but could you make a 2.7k sequence and warp stabilise that, using stabilise only or stabilise and crop. Then add this sequence to the 1920x1080 sizing to suit.

  • Warp Stabilizer Usage Limitations

    Thank you Adobe team for the intergration of Warp Stabilizer. It has fundamentally changed the potential of much of the footage I typically work with.
    But the limitations, such as the clip must match the dimensions of the sequence, can't be time stretched or time remapped, are a formidable handicap.
    It's easily solved by nesting the clip and applying the warp stabilizer to that new sequence instead. I'm curious if this is so easy for us, why the software can't handle it natively? Can we expect any changes to this in the future?

    Some issues were addressed and performance should be better, but no major changes for the CC release due out next week. (informally known as 7.0)
    I think (but I'm not sure) that AE's warp stabilizer has some capabilities that ppro's does not. So you might try it there once that's all available to you. Ben's request is good (please submit a FR if you have not yet) but everything takes time and that time has to be prioritized.

  • Adobe Premiere CC 2014.2: losing rendered files when using warp stabilizer

    Hi,
    I am constantly losing rendered files when using the warp stabilizer. So far I have tried about every hint I could find on the web such as cleaning the cache, rebuilding the rendered files, creating additional sequences etc etc.
    Honestly I am getting tired of using a product that isnt cheap in the first place to rent and where a bug like this apparently persists over several product versions without being fully fixed (I have had this problem throughout 2014 but according to forum postings others seem to have problems with much earlier versions as well).
    I would be really grateful if somebofy has any suggestion how this can be addressed.
    I am also happy to help testing fixes - if there are any fixes available.
    Thanks a lot and Happy New Year!
    Martin

    Hi Catherine,
    Welcome to the Adobe forums.
    Please try the steps mentioned below and check if it works for you.
    1. Launch Premiere Pro and create a Project, go to File menu>Project Settings>Renderer and change the Renderer to Software only mode, delete previews if you get a prompt and then try to import the clip.
    2. If step 1 fails or the Renderer is already on Software only mode, go to Start Menu and search for Device Manager, go into Display Adapters and Right click on the Graphics card to select Update driver software option, on the next screen choose "Browse my computer for driver software", then choose "Let me Pick from a list..." option and from the list select "Standard VGA Graphics adapters. You might need to change the screen resolution of your screen and once done restart the machine again.
    Launch Premiere Pro and import the clip to check.
    Regards,
    Vinay

  • The Next Version of Premiere Pro CC - Warp Stabilizer

    With the recent post of what's coming in the next version of PPro CC, I was sad to see no mention of Warp Stabilizer. As amazing of an effect as it is, it needs a bit of help. I know there are improvements and fixes that probably weren't mentioned in the post so I'm still holding out hope. We use Warp Stabilizer more than anyone I know. Several hundred times per week. Yes, per week, no exaggeration. Over the last few years, we've built an entire style of shooting around the strengths of this awesome effect that emulates the use of a slider, steadicam and crane all without having to have them. So we've become really familiar with its PROS and CONS.
    Here is a short list of SEVEN things that should be addressed with regards to warp stabilizer within Premiere Pro CC to maximize its effectiveness (and yes we did submit multiple Feature Requests for these so far to no avail):
    FIrst and foremost and by far MOST IMPORTANT to us - Allow users to create a CUSTOM PRESET with any altered settings that will engage (or begin Analyzing/Stabilizing) automatically when added to a clip!! This is huge. If you double click on Warp Stabilizer with a clip selected, it is applied to that clip and begins the process of stabilizing that clip. However, the vast majority of the time we need to alter the settings of the effect. If we create a custom preset, that's all fine and good, but when we add that to a clip, it does NOT begin stabilizing. Instead you have to manually go into the Effect Controls for each clip and select ANALYZE. Huge waste of time when adding this effect to hundreds of clips. PLEASE FIX!
    BUG when saving projects!!! - If this is not a bug, it needs to be fixed because it's awful. - If you have more than one sequence with multiple warp stabilizations added and GPU ACCELERATION IS ENABLED, then after you SAVE a project (or if it auto-saves) when you toggle between the two sequences you are hit with a delay or freeze while the render bar goes from Yellow to Red...and finally back to yellow again. No work can be done during this delay/freeze. The more stabilized clips, the longer the delay. For us, on our larger projects this delay is sometimes 30 seconds to almost a full minute! Once it turns back to yellow, you can toggle between sequences without the delay...but as soon as it saves again...and you toggle between sequences, the delay hits again. If this is a bug, or somehow a result of Premiere Pro's way of CACHING projects after it's saved, then I sincerely hope it's fixed asap. It's awful!
    The third is more of a feature request than a fix - Add the ability to set the maximum scale to work WITH the smoothness control so that if you never want your clips to scale more than say 105%, you can set that and have Warp Stabilizer stabilize the clip and adjust the "smoothness" percentage from the default "50%" down to whatever it needs to be in order for that clip to be fully stabilized and scaled to no more than 105%. Correct me if I'm wrong, but this is not possible currently. Right now we have to manually adjust each clip if it is initially scaled too much by dropping down the Smoothness %.
    Another great feature would be the ability to manually keyframe the scaling so that if you have a longer clip that starts fairly steady, then needs to be smoothed out a bit more in the middle, before it ends relatively steady again, you can slowly and seamlessly ramp up the stabilization/scaling so that the whole clip doesn't have to be scaled to make up for the misgivings of one portion of the clip.
    Minor bug - sometimes when you have extended the length of a clip, the clip needs to be re-analyzed again. However, the "analyze" button is often greyed out. You need to click away from the clip and then click on the clip again to make that button appear again. Nothing big, but still, a small bug.
    After Effects Warp Stablizer VFX feature carried over - It would be nice to carry over to Premiere the ability to isolate what in frame is supposed to be stable (sometimes someone nodding their head can trick the effect into thinking that it's the camera shaking). Great to have it in AE, but would be nice to carry over to Premiere Pro CC.
    Finally, I've always believed that no matter how cool "Subspace Warp" sounds, it is not as effective as "Position, Scale & Rotation". This SHOULD be the deafult "method" within the Warp's settings. I'd say 95% of the thousands and thousands of clips we've stabilized we ended up switching the "Method" within the settings to "Position, Scale & Rotation" because it either scaled the shot less or created less "wobble" in the resulting stabilized clip. I know everyone shoots differently, and sometimes Subspace Warp is the way to go, but we have stabilized all sorts of shots with great success by simply switching this setting. Granted...if #1 on this list was taken care of we could then easily have this set as our default setting.
    Hopefully this list either reaches someone within Adobe that can do something about them or at the very least inspires others to write feature requests and bug fixes as we have. Even resolving #1, #2 and #3 would be HUGE and would save our editors probably 10 hours per week.  It's an awesome effect, far better than "smoothcam" on FCP7, it just needs a little love.

    CoSA_DaveS wrote:
    All good points, thanks for posting.
    For #1, you can make this work in AE at least. This tip is from my colleague DanW:
         If you make a preset by only selecting the values you change (and not a preset for the whole effect) then it will auto-analyze on apply.
         Simplest way: apply WS, make edits, hit UU to reveal changed params, select all "i-beams" in the Timeline, drag them to the Effects & Presets panel.
    For #4, you can get manual control over the scaling by setting Framing to Stabilize Only, and then keyframe Additional Scale to taste. At one point we were going to try to automate this, but found automatic scaling to be very subjective as to the best way to handle it.
    For #6, Warp Stabilizer will not track areas with zero alpha channel. So you can pre-mask the input to reveal just the parts you want to stabilize. Do this inside a nested sequence, with Warp Stabilizer applied downstream (in the outer sequence). The just-announced masking & tracking capabilities of the next CC version should be handy for this.
    -DaveS, Adobe Dynamic Media, Advanced Product Development
    Hi DaveS!
    Great to hear that you guys are taking a look at this list. Hope it helps make it better.  #1, #2, and #3 are by far the biggest time killers for us so hopefully they'll be able to be fixed/resolved within Premiere soon.
    Regarding your note about #1: Allowing this functionality within Premiere specifically would be very helpful. Would it be possible to eventually allow Premiere to auto-analyze when a saved custom preset is applied to a clip? I tried it in AE as you suggested, and couldn't figure it out. But realistically we use Warp Stabilizer on so many clips that round tripping literally hundreds of short clips to AE would be just as time consuming as going into the settings in premiere for each one and adjusting the parameters. We usually adjust the method and then adjust the smoothness scale so that it doesn't "Auto-Scale" more than 104%. That's where our #3 suggestion would help. I didn't quite understand how to make a preset of specific changed values. I tried, but couldn't follow DanW's suggestion. Granted, I'm not that great with AE. I really just use it for the Warp VFX's ability to isolate what in frame is stabilized (hope that comes to Premiere one day) and that's about it. And I really only have to do that a couple times per project. Anyway, I'm sure I'm doing DanW's suggestions wrong but regardless, I'm not sure it would save us much time when we have several hundred individual little clips that would all need to be sent to AE. Any hope for adding this auto-analyze functionality (hopefully allowing a custom preset on the whole effect and all it's adjusted parameters) in Premiere CC?
    Regarding your note about #4: That is a valid work around for now. I appreciate that thought. Thanks!
    Regarding your note about #6: I think I half understand what you described. I'd have to try it. Although, as I said before, the AE way of doing it is ideal and I just hoped that ability to show the tracking points and delete them over time would come to Premiere CC one day. When the next CC comes out I'd love to try this masking method although I think I'll have to claify exactly what you want me to do just to be safe. Is there no hope to port this added functionality that's in AE's Warp VFX over to Premiere's Warp Stabilizer? Again, not the end of the world for us. I'd rather #1, #2 and #3 be addressed inside Premiere Pro CC for now.
    Fixing the first 3 on this list would be HUGE time saver for us.
    Thanks again DaveS to you and the rest of the Adobe team for looking into this list. Very much appreciated.

Maybe you are looking for