Keyframe Warp Stabilizer

I'm going to end up doing this the hard way, but I thought I'd ask to see if a workaround exists--I haven't found one anywhere online.
I am stabilizing a jib shot for a series I'm working on--the move on the jib is fluid and perfect, there is just a little bit of sway at the end of each move.  There is one of these shots, roughly the same but slightly different for each episode.  What I need to do is stabilize only the part of the clip that sways--that is, put no stabilization on the actual move itself.  Using autoscale or crop invariably makes the image pop out of place when the stabilize effect is applied to the swaying part of the clip.
Is there a way to keyframe the stabilizer on and off, so that I can leave it off and have it fade on over 10 or 12 frames when I need it? 
Right now the only solution I have is to split the track and stabilize just the unwanted sway, and then crossfade the nonstabilized shot while scaling/rotating to match the position of the stabilized clip.
Actually--if there were any way to simply paste the scale and warp parameters from the first frame of the stabilized clip to the whole of the unstabilized clip, that would work for me.
Thanks for any advice.

Splitting the clip is the way to go. You'll learn quickly that you don't want to waste time processing anything you are not going to use. For example I taught a class a year ago where one of the student rotoscoped 40 seconds of a shot. It took him more than 3 hours to carefully cut out the entire actor when he only needed about 30 frames of the left side of the actors body to pull off the effect.

Similar Messages

  • 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.

  • Warp Stabilizer CS6 scales down last frame

    Hey,
    Every time I add the Warp Stabilizer in Premiere Pro CS6, it auto-scales the footage, except for the last frame. It just changes to 100% again, so I'll just have to cut it off. Any others experiencing this issue, or any ways to solve it?
    Thanks in advance.
    Edit: turns out it's probably not the warp stabilizer, but the position. When I adjust the position, the same thing happens, and since the stabilizer changes the position, the position will probably be causing the issue. Keyframing is disabled.

    This strikes me as a bug that hasn't been corrected.
    Is there a way to see if it has even been reported? (I don't want to add a redundant bug report).
    I'm having what I think is the same- or similar - problem in PPro CC.
    Machine: Windows 7 Pro,
    i7-3930K @ 3.20 GHz with 32 GB memory
    nVidia GeForce GTX 670.
    Both CC and CS 6 installed.
    I have a single clip of video footage exactly 19 seconds  (00;00;19;00)  long in Track V1.
    I have added the Warp Stabilizer effect to Track V1, let it analyze and stabilize, and when playing, the last frame is "chopped off" by a noticeable percentage.
    When selecting the Effect Controls tab, the Opacity keyframe icon is "active", though still set at 100%.
    I lowered the clip Opacity, moved the pointer a few seconds to the left via left-arrow, and re-played.
    The last frame is still chopped off.
    I returned the clip Opacity to 100%, moved the pointer a few seconds to the left, and re-played.
    The frame is still chopped off.
    This "solution" appears to have no effect for me.
    I also need the Timecode effect for this same clip, and have noticed strange things with it.
    Although my footage in Track V1 is exactly 19:00,
    - AFTER I've added the Warp Stabilizer effect to Track V1, AND
    - have added an Adjustment Layer to Track V2 in the sequence, AND
    - have added the Timecode effect to the Adjustment layer in Track V2,
    when I point to the last frame, the Timecode effect shows 18:29, not 19:00. After moving 1 frame to the left, i.e. hitting left-arrow once. the Timecode also shows 18:29. so the Timecode is showing the same numbers twice.
    It seems that the Timecode effect is somehow "losing track" of what frame is being displayed.(Is it "counting from '1' instead of '0')?
    Any help available in this?
    I've even gone so far as to:
    1) change, i.e. lower, the Opacity, save the project, then return the Opacity to 100%, then saved the project again; last frame still "chopped off".
    2) once the opacity was lowered, I've also rendered the sequence, saved the project, then returned the Opacity to 100%, and re-rendered, but the problem remains.
    3) I even "cleared" both the Warp Stabilizer effect from the footage clip, AND the clip from within the sequence, then added the clip back to the sequence WITHOUT the Warp Stabilzer effect, then pointed at the final frame, and that final frame is STILL chopped off.
    For this project, I'm "sticking" with CC, because I'm working on it from both my home studio and another location which has only CC.
    I haven't checked CS6 to see if the Warp Stabilizer and Timecode effects are working correctly, but both seem to have gone a little "haywire".
    Is there some other way to fix the problem of the last frame being "chopped off"?

  • Trying to get value from Warp Stabilizer

    Hello everyone!
    I want to write a script which can get value "Auto-scale" from all stabilized footages and, depending from the number, will change the colour of footage (layer).
    "Auto-scale" isn`t keyframable effect, so I got stuck on how to get it`s value.
    Thank you in advance!

    If you're after the percentage number, this should help. It assumes your stabilized layer is layer 1 of the active comp:
      var myComp = app.project.activeItem;
      var myLayer = myComp.layer(1);
      var myEffect = myLayer.property("Effects").property("Warp Stabilizer");
      var myName = myEffect.property("ADBE SubspaceStabilizer-0017").name;
      var numIdx = myName.indexOf("(");
      if (numIdx > -1){
        var myPct = parseFloat(myName.substr(numIdx+1));
        alert (myPct);
      }else{
        alert("No percentage found.");
    Dan

  • Warp stabilizer "Reverse Stabilization" mode with synthesized edges intact?

    So here's the end result I need:
    My original shot, non-stabilized but with synthesized edges beyond the original frame edge (it's a panning shot so that image information is possible to derive).
    I tried using Warp Stabilizer with method "Position", "synthesize edges", and "reversible stabilization". The results are great in terms of creating image beyond the frame edge, but when I use "reverse stabilization" in a duplicated instance of WS it ignores/discards the sythesized edges.
    Is it possible to get the position tracking data some other way, so I can use the ol' null object method of inversing the stabilization?
    Thanks in advance for any help.

    Warp stabilizer produces no tracking information that is accessible by expression or keyframe data so you'll have to try a pre-comp with collapsed transformations.
    BTW, once you do the stabilizing you can change the size of your comp and render out a DI (digital intermediate) of your larger video to use in your project. I might try that.

  • Warp Stabilizer VFX, did you know

    I have been using After Effects 5.5 [AE] for a while and this is about Warp Stabilizer is After Effects CC [Ae]. Yes Warp Stabilizer in [Ae] is about 3 times faster that [AE] and also offers some very good added features.  Sometimes you need the added features, other times you do not. 
    But did you know:
    While you cannot run multiple instances of [AE] or [Ae] on a single computer, if you have [AE] and [Ae] both installed, you can run both of them on a single computer because they are separate programs.  So now you can do two things at once including Warp Stabilizer.

    Yes, both Warp Stabilizer and the 3D Camera Tracker run as separate, external processes that send their results back to the main After Effects application when they're done.
    Details here:
    memory and storage tips for Warp Stabilizer and 3D Camera Tracker
    Regarding the speed improvements: You say that you've noticed a 3x speedup. We've found that the speedup varies a lot depending on the characteristics of the footage being processed, so I wouldn't count on it being 3x in all cases. I think that our marketing materials ended up saying that the speedup was ~80% (so nearly a 2x speedup) across all of our various tests.

  • Steps to send a clip to AE to utilize Warp Stabilizer VFX then back to Premiere Pro CC

    So I use Warp Stabilizer for about 200 clips per project. It's effectiveness has shaped how I shoot. It's awesome. Now there's VFX in AE...Can someone layout the steps involved in the following:
    a) Taking a clip from Premiere Pro CC and sending it to After Effects CC (I'm not that versed in using AE having not used it in quite a while)
    b) Then how to apply the new Warp Stabilizer VFX (I assume just go to effects>distort>WarpStabilizerVFX ???) ... (if there are tutorials on how exactly to use it, especially detailing exactly how to utilize the new feature of isolating what in the frame is to be stabilized that would be great too)
    c) Then how to send it back to Premiere Pro CC. (I'm guessing I just save it and let dynamic link take care of the rest?)
    I've tried right-clicking on a clip and selecting "replace with AE composition" (is that what I should do?), then applying the effect but I get a "warp stabilizer VFX analysis doesn't work with Collapse Transformations" message so I stopped. If it makes any difference, the majority of my footage is shot at 60p and then interpreted and edited at 23.976fps. Thanks!
    NOTE TO STAFF: I've said it before and I'll say it again as someone who uses warp stabilizer several hundred times per week, I still think the default "method" in the settings should be "Position, Scale, Rotation" instead of Subspace Warp because it works FAR better (less wobble and less scaling about 90% of the time). Can't help myself I had to bring that up again here.

    a) Select a clip in PrPro timeline, right-click and choose 'Replace With After Effects Composition'. Take care of handles if you might need them (that's rather general tip).
    Warning about Collapse Transformation switch indicates that you have 'Scale to Frame Size' option enabled for your clips in PrPro timeline. If that was done intentionally, you can simply toggle the Collapse Transformation switch (small sun icon) off. If not, rather disable 'Scale to Frame Size' for your clips in PrPro timeline.
    b) Quite a boring but covering almost all necessary details tutorial on basic work with Warp Stabilizer in AE CC from Adobe TV:
    Some advanced techniques from Lynda.com
    and Mathias Möhl:
    c) When you're happy with your work in AE and going to lock it, render a digital intermediate out of AE, import it into PrPro and replace your dynamically linked composition in the timeline with that DI (see this good old thread on Dynamic Link workflow, pay attention to Todd's comments).
    If you leave the 'Include Project Link' checkbox in the Output Module Settings dialog enabled while rendering your DI, you can easily get back to appropriate AE project so as to maybe tweak some settings: just select your DI in PrPro timeline, right-click and choose 'Edit Original'.
    Mind the bloating issue, keep the amount of applied Warp Stabilizer instances in a single AE project reasonable.

  • 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.

  • 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

  • AE project crashes on startup - due to Warp Stabilizer and Highlight/Shadow

    I've got a head scratcher here...
    Firstly, I have been working on this project file for several days with no problems. Everything was running smoothly... working, tweaking, rendering... all successful.
    A couple days after doing a final render, I went to re-open the project and got these two errors, followed by AE crashing:
    To the best of my knowledge, I changed nothing on my system.
    I've tried removing my 3rd parth plugins (Video Copilot Optical Flares, Element, etc...) but to no avail. The program still crashes when opening this file.
    I've since installed the updates to AE CS 6, but still no luck.
    Removing Warp Stabilizer and Shadow/Highlight allow me to open this project file (obviously telling me that its missing both).
    I've tested out both plug-ins in a different file, and I'm able to open those no problem.
    I'm running this on a Mac Book Pro running OSX 10.6.8
    Model Name:
    MacBook Pro
      Model Identifier:
    MacBookPro8,2
      Processor Name:
    Intel Core i7
      Processor Speed:
    2.2 GHz
      Number of Processors:
    1
      Total Number of Cores:
    4
      L2 Cache (per Core):
    256 KB
      L3 Cache:
    6 MB
      Memory:
    8 GB
    AMD Radeon HD 6750M:
    Chipset Model:
    AMD Radeon HD 6750M
      Type:
    GPU
      Bus:
    PCIe
      PCIe Lane Width:
    x8
      VRAM (Total):
    1024 MB
      Vendor:
    ATI (0x1002)
      Device ID:
    0x6741
      Revision ID:
    0x0000
      ROM Revision:
    113-C0170L-573
      gMux Version:
    1.9.23
      EFI Driver Version:
    01.00.573
    Any thoughts???

    We've isolated the bug that is causing this behavior. It seems to only affect instances of the Shadow/Highlight effect on an adjustment layer over layer(s) with the Warp Stabilizer.
    There are a couple of workarounds:
    - One is to remove the Shadow/Highlight plug-in from the plug-ins folder and then open the project (and then fix the project to not have this effect on an adjustment layer over a Warp Stabilizer instance).
    - Another is to precompose the layer(s) with the Warp Stabilizer effect.
    We're working on a fix for this.

  • How to apply warp stabilization to the same clip used twice in the same timeline

    If I use the same source clip in a timeline (say 3 or 4 different sections of the clip by dropping the same clip on the timeline and just trimming it differently) and want to stabilize them all, how do I do that?  The first instance of the clip lets me use warp stabilization, but then when I try to apply it to later instances of the same clip in the timeline, it says I can't do that.   How do I apply the stabilization to later instances of the same clip in the timeline?
    Thanks

    After trimming the clip just apply the warp stabiliser to it without copying and pasting. You can't copy and paste the warp stabiliser because it needs to analyse the pixels of each clip everytime its applied.

  • Warp Stabilizer through After Effects Dynamic Link Locks up in CS6

    Hey Gang,
    I've been using Warp Stabilizer through dynamic link in CS5.5 without issues.  However, when I go through dynamic link into AE, then apply Warp Stabilizer, AE locks up?
    I can apply any other effects through this path in AE without issue, but when I try to apply WS, I get the "Analyze", but AE stops cold there. 
    I've tried:
    -Opening new project in PP with basic 5 second clip.  Then going through dynamic link into AE, and applying warp stabilizer first thing.  AE locks up there with the simplest flow.
    -I have the latest downloads of the entire production CS6 suite.
    -If I apply warp stabilizer directly in Premiere CS6 (which I did not know previously I could do), it works fine! (Just noticed Warp Stabilizer is present in PP CS6, but not in CS5.5). 
    -If I try to import the Premiere project from AE, AE locks up doing that?
    It appears there are multiple issues here:
    1. I can't apply Warp Stabilizer in After Effects, and doing so crashes AE.
    2. I can't import a Premiere project into After Effects, and doing so crashes AE too?
    I'm assuming I'm going to need to download AE again?
    Thank you for any help and suggestions you may have!
    Derek...
    Message was edited by: Derek Emmett

    Hello Mylenium,
    thank you for your input.  Naturally I would expect if my work flow in CS5.5 works great, I would not have to make any changes in CS6 to accomplish the same task.  With that said, I made it as simple as possible for CS6 AE to handle the Warp Stabilizer effect, and it crashed?  If I went directly back to CS5.5, no problems at all in AE (same source footage, but of course different projects).  When I first tried CS6 AE it appeared to work fine, even when doing Warp effects.  So when I ran into the issue I saw above, I started thinking it was possible the update I did to AE may have caused some other issue.  By the way, the projects I open in both CS5.5 vs. CS6 were independent, meaning, I did not convert a CS5.5 job to CS6, etc...   (See notes below).
    My setup is standard:
    i7 960
    16G mem
    Nvidia Quadro 4k
    Footage is Canon 5D Mkii 1080p
    All drivers up to date.
    -I think going back and forth between CS5.5 and CS6 may have caused some issues?  When I rebooted my system, CS6 AE seems to work fine when applying Warp Stabilizer effects again. 
    -What I did find more interesting and effective, was that CS6 Premiere has Warp Stabilizer right in its own effects now!  Works great in the premiere flow and plays back far better then going through the Dynamic Link with After Effects!  When playing Dynamic link effects back in Premiere, I'm sure everyone sees performance issues in the playback.  However, in at least with applying Warp Stabilizer directly in Premiere, the playback performance is much better.
    Thank you
    Derek...

  • 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.

  • Warp Stabilizer crops bottom of video if videos layers are beneath it for no reason.  Why???

    Warp Stabilizer crops bottom of video if videos layers are beneath it for no reason.  Why???
    remove the layers beneath and it's fine.  Hopefully adobe addresses this issue asap to save all of us a good amount of time.

    I have noticed similar: apply crop to a layer and with all settings at 0 a line of underlying video can be seen at the bottom.

  • FR: Big yet incredibly simple improvement to Warp Stabilizer

    I love the Warp Stabilizer effect in PP.  It's great!  But depending on the footage and the effect's settings, sometimes it can actually make things worse.  This means that any time this effect is used, users must review of the results after the effect finishes analyzing the clip.
    Here's the problem:
    Analysis takes a long time, often far too long for a user to stop editing and wait to review the results.  In my case, I keep editing, but often I forget where my stabilized clip for review is located.  In a multicam sequence, where every video clip occupies the same track, there's little to no visual cues to remind me where the Stabilized clips are.  Setting an in and/or out point as temporary markers can work if you have up to two Stabilized clips.  But what if you just stabilized 5 clips, and you want to keep editing while they're being analyzed?  How do you visually recognize which clips they are?  All current solutions add work for the editor, such as moving stabilized clips up a track and then back down after approval of the effect's results, etc.  If you have transitions between a Stabilized and an adjacent clip, or clips on a track above it, the situation gets worse.
    Here's the (incredibly simple) solution:
    Give us a visual color cue any time a clip has the Warp Stabilizer effect added to it!  This could be done through a new user selectable color category in the Preferences window's 'Label Defaults' panel.
    It's interesting to note that while 8 different colors can be set in the Label Colors tab, only 7 are currently used by PP in the Label Defaults tab, so setting a unique color to this new eighth item should be even easier to program.
    Adobe, this would make a great little addition to your next PP update!
    What do others think?

    Jim Simon wrote:
    Your request calls for easy visual recognition of that one effect, mine calls for easy visual recognition of any effect, which I feel would be far more useful to far more editors.
    Be as it may, even though I highly doubt that editors need an easier way to determine which clips have any effect applied in general, WS clips would still have to have a different color, otherwise editors wouldn't be able to differentiate WS effects from any other old effect that simply does not require the editor pause or return later to see the results.  I've explained this pretty clearly but it seems you're determined to not get it.
    Jim Simon wrote:
    Or, if you don't want to wait for the effect to finish, add it after editing, as most editors do with most effects anyway.  Then you'll have the time to wait to see the results.
    Adding effects is part of editing, or isn't it?  In case you don't know, editors work differently.  If I want to add effects as I do my cuts, what's wrong with that?  The software should be intelligent and flexible enough to accommodate a user's workflow.  And if it isn't, then it should be improved.  If you're an advocate against this kind of progress and think users should adapt to and accept a programs limitations, rather than speak up, which version of Premiere are you using?  4.1?
    Jim Simon wrote:
    Mark them, as you can do now. 
    The whole point of this thread and FR is for Premiere to remove steps from our workflow!  Still don't get it, do you?
    It seems that every time I expose a limitation in Premiere or an area for improvement, you suggest that I should change my workflow rather than have the software improve in a way that could benefit countless other editors.  At this point, I really have to ask... what's in it for you Jim?  What's your point?
    "Then you'll have time to wait to see the results"  Is that what you do, wait 10 minutes for a long clip to finish analyzing so you can see the WS results?  You're just sounding more and more ridiculous IMHO.  It would be nice if overall you made more intelligent contributions to my threads.
    Frankly, I'm getting tired of this nonsense Jim.  If you have something intelligent to say, please, by all means.  If you don't, please stop diluting the message of my threads with your nonsense arguments/comments.  If you want all clips with effects applied to them to be labeled with the same color, and thus make WS clips visually indistinguishable (which is the current problem I'm asking Adobe to fix), go ahead and start your own thread.

Maybe you are looking for