Optimizing Warp Stabilizer processing time

I just want to share my experience with the warp stabilizer and ask if you have other ideas to make warp stabilizer works faster.
If some of you knows anyway to makes analysis faster please share it.
So far I tried two different memory/ram settings:
Mode 1:
Mode 2:
Analysis takes the same time with both settings but render to file took less than 1/5 with setting shown in mode 2.
If you work your shaky clips in Premiere, replacing them with AE composition, I notice that it takes much less time to render the stabilized clip in AE to a new file and then manually replace it in premiere timeline than rendering the preview in premiere. Lot of difference in time.
Please share any experience related
Thanks

I'm not sure that warp stabilizer will process in the background with multiple comps. I'd create a new project, create two or 3 compositions from the clips, add warp stabilizer to each of them but close all of the comp timelines except one. I'd then open up AME and add the AE project and all the Compositions to the cue and give it a go. You'll be able to tell if that works.
If it doesn't then you'll have to open all 40 comps in the timeline and let each percolate overnight before rendering.
If it were me I'd make a rough cut of your project first so that I had an idea of exactly whick portion of which shots I needed then I'd stabilize only those sections.

Similar Messages

  • CS6. Need to have time remapping and warp stabilizer work together.

    This should be obvious for most people. These two effects must be made to work together.
    If you're shooting with a glider you're usually moving very carefully (read: slower than normal) so the footage in post would need to be sped up plus stabilized a bit.
    Currently warp stabilizer and time remapping cannot be applied at the same time. But I *need* it to be applied at the same time. I need a workaround.
    Should I:
    1. shorten the clips, export them, re-import them into the project, and then apply stabilizer?
    2. apply the stabilizer, export them, re-import them into the project, and then shorten them?
    How do I export individual clips as just seperate clips while Premiere? Do I have to drag them into an empty timeline one by one, apply the stabilizer/remapping, and export, remove the clip, put in the second clip, etc all one by one?
    I've used Mercalli in the past and I time remap the footage and then apply Mercalli to the accelerated clip. Mercalli doesn't mind a bit.

    ComputerNovice25 wrote:
    Adobe might have written the code in a way that doesn't include the ability to deal with that extra variable. I'm assuming that when it's nested it then makes the timeline it's in just read it as a normal clip again instead of a clip with a non-supported variable included.
    Although I'm totally just guessing, but if what I'm saying is correct it would mean a fix wouldn't be very much work at all. Which means in the future they could simply provide a quick and easy patch to fix this. I'd highly suggest to make a feature request.
    https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
    Does Adobe read these feature requests? I often have a hard time justifying spending time to type out something when I feel like it's just being thrown into a black hole. I'm sure the team gets thousands of feature requests. It's like the lottery. Statistically you will never win. Sure, you'll never win if you don't play, but it's still a waste of time to play. I know, I'm pessimistic. Just don't have much faith in conglomerates - although Lightroom 3 is by far the most perfect program I have ever used and I would kiss the LR3 team if I could.
    With Lightroom, Photoshop is hardly needed anymore unless absolutely necessary or for truly intensive chop-like edits. Premiere DESPERATELY needs a Lightroom equivalent.
    I have half a mind to guess (nicely) that you video guys have absolutely no idea what you're missing out on, workflow-wise. It's life-changing. Literally.
    I'm doing a video right now and I can't stop thinking about how if I had a Lightroom workflow, this video consisting of 40 clips, 40 titles, 40 transitions, audio tracks could be on the way to final export in 5 minutes. 5 MINUTES. And be 100% as good as if I had to spend an hour doing this in traditional Premiere.

  • Warp Stabilizer analysis process stopping and never ends (AE CC 2014)

    I'm running the latest 2014 AE CC and I've been getting this issue running Warp Stabilizer on my clips.  Intermittently, warp stabilizer analysis process would stop at certain frame and never ends.  I have to quit / kill AE.
    I'm running AE on 15" retina macbook pro 2013 with dedicated nvidia 750M video card, 16GB of RAM and plenty of disk space (over half a terabyte left), running Yosemite 10.10.2.
    Has anyone experienced this?  How do I solve this issue?

    "During the analysis and solving stages, the Warp Stabilizer effect and 3D Camera Tracker effect use memory outside of the pool shared by After Effects and Premiere Pro. Therefore, you can allocate more memory to the analysis and solving phases for these effects by increasing the RAM Reserved For Other Applications value in the Memory & Multiprocessing preferences."
    Thank you for that link.  I'm going to check the "RAM Reserved For Other Applications" and increase the value if it's too low.

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

  • Crashes after effects with warp stabilizer

    I have some problems with after effect cs6.
    When I try to warp stabilizer an mov file  in after effects I have crashes every time.
    My Pc runs Win 7 Ultimate
    12 G Ram memory
    Graphic card NVidia GTX 480
    In the preferences I have no GPU accelleration it tells me that tha graphic card is not compatible , in stead in premiere pro I can select the redering
    In Premiere Pro I can select  this option and it works fine

    Thanks for the reply.
    After modif the raytracer_supported_cards.txt file now I can select the GPU option . Here are the settings for the GPU informations.
    Fast Draft:
    Available
    Texture Memory:
    1000,00 MB
    Ray-tracing:
    GPU
    OpenGL
    Vendor:
    NVIDIA Corporation
    Device:
    GeForce GTX 480/PCIe/SSE2
    Version:
    3.0.0
    Total Memory:
    1,45 GB
    Shader Model:
    4.0 or later
    CUDA
    Driver Version:
    5.0
    Devices:
    1 (GeForce GTX 480)
    Current Usable Memory:
    1,24 GB (at application launch)
    Maximum Usable Memory:
    1,50 GB
    Results Event viewer
    Faulting application name: AfterFX.exe, version: 11.0.1.12, time stamp: 0x4fab6f50
    Faulting module name: hdavasiopx.dll, version: 2.0.0.7, time stamp: 0x4db8e7b1
    Exception code: 0xc0000005
    Fault offset: 0x0000000000002932
    Faulting process id: 0x53c
    Faulting application start time: 0x01cd91cef9878216
    Faulting application path: C:\Program Files\Adobe\Adobe After Effects CS6\Support Files\AfterFX.exe
    Faulting module path: c:\windows\system32\hdavasiopx.dll
    Report Id: 26ff269f-fdcb-11e1-9d44-20cf300b0ea6
    After modif the settings the problem is not solved.
    I have the following message after the crash : Last logged message was:<xxx><alalyzer Server><5><Start xxxxxx.....>
    I will try to convert the file and se wat the results are.

  • 5 things which should be improved in the Warp Stabilizer

    1. Performance.
    When stabilizing any footage I always ask myself: "What the heck is he doing there?!" not even a single core is really working hard. It looks like an idle background process  The GPU is idle as well, as the analysis pass is only run on the CPU.
    This maybe okay if you still need much work to do in Premiere. But often, the next steps DEPEND on the stabilization and you have to WAIT and WAIT and WAIT...
    It's just painful to imagine that, running a machine with 8 cores, more than 8 times the amount of video material COULD be analyzed.
    The free Deshaker for Virtualdub actually uses more cores (even though not at 100%) but analyzes at about 20-21fps compared to the Warp Stabilizer at about 4-8fps.
    Admitted, the Deshakers results aren't nearly as good (especially with rolling shutter, which can be configured though, but you don't always know the right percentage for the cam you're using).
    This also applies to opening projects with much stabilization data. It opens... and opens... rarely any disk activity and rarely any CPU or GPU activity. Again: WHAT IS HE DOING THERE? Just waiting for the clock itself?! Or is he sending it all to the NSA? That at least would explain the unneccesary delay:P (just kidding!)
    2. Stabilization data.
    For me, I wouldn't have any problem with storing it just inside a project folder or a separate file. Just add a checkbox into the plugin settings:
    [x] Store stabilisation data in separate file/folder.
    This may be then called [projectName].stabilization
    Inside that folder, there will be maybe one file for every effect used in the project.
    ...or you can use the old way, if you don't have so much stabilization work to do.
    3. Small bugs.
    When using "stabilize only", the resulting frame, at least in Premiere Pro, has a HUGE "DC offset" sometimes. This is a term from music producing, but exactly fits in here. You can clearly see it when there are still images that shouldn't receive much of stabilization. They're somtimes shifted far out of the viewing frame, leaving big black borders, so you have to manually adjust the frame position to fit back into a "neutral" position. This could be resolved to let the whole correcting curve undergo something like a "low pass filter" which will try to keep the resulting frame SOMEHOW centered.
    In this image above, from a longer clip, there isn't much motion at all. But you can see how far the offset from the actual video frame is. I have to do this for almost every video, also after I change the "smoothness" setting.
    4. More control
    I would LOVE to be able to disable "zoom detection", because it gives me lots of "Vertigo Effects" in many cases.
    I heard this has been alredy addressed for CC.
    5. Improvements / new features
    One thing I always do with every stabilized video:
    Instead of synthesize edges, which takes AGES to render, I just do the following:
    I place the same clip, unstabilized, behind the stabilized clip (stabilized, borders only) and give the stabilized clip softened borders with "rough edges". This even still renders fine on the GPU.
    This would make a great option for the stabilizer. Just call it "overlay over original with blurred edges" or something like that.
    This has worked extremely well for any stabilized footage so far and isn't nearly as disturbing as the synthesized edges.
    I'm considering to join the Creative Cloud, because unless I do this I don't expect to see any improvements in my old and out-dated Premiere PRO CS6...

    https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform to file a feature request... insert a reference to this message link

  • Warp Stabilizer Script Request

    There is an operation that is taking me looong looong time, and I would like to know if there is someone who can write me a script to make the operation faster, that would be fantastic !
    I have my edited video in the timeline, with transition applied and ready to be color corrected, but all my clips are shaky (aerials and handheld) so I need to stabilize all clips.
    So far the best a faster way I found out asking help in the forum is to move every single clip to the upper track, add some handles (1 second each side if available), select "replace with AE composition", in AE select "Stabilize Clip" and setting the options while AE analyze the clip (most of the time I just need to select "smooth motion" or "no motion" and leave everything default, once stabilized I render the clip in lossless format with a codec of my choice, then I go back to Pr, import the rendered clip and replace the original with the rendered one, push it back in place where it was before the handles creation and add the transitions again.
    It's long way.. especially for me that I work with clips that have to be 100% stabilized.
    Is it possible to make a script that makes all these operation automatic ?
    Anyone who can do it for me ?
    Thanks a lot !! that would be VERY appreciated
    Maybe it would be a lot easier if warp stabilizer was a Pr built in filter... hopefuly on next release...

    I wasn't suggesting that stabilizing won't help your shots, I was suggesting that more care be taken in pre-production to save time and money. Any mistake made in production, any shortcut, like not taking the time to properly handle or mount the camera may, and usually does cost more in time and money to fix than it would have taken to do right in the first place. Even a tiny handy cam or DSLR can be held steady if you take a moment to brace yourself, attach a weight or even attach a small tripod that you use as a counter balance and mini steadycam to the camera.
    You can't make a script that will do a round trip from AE to Premiere and back, but you can make an animation preset for stabilizing. May I suggest this workflow.
    Rough cut the sequences that you want to stabilize in PPro leaving handles on each shot. Render the rough cut to a production codec (mpeg streams from DSLR's and GoPros all the way to Panasonic P2 and XD cam take more time to decode and stabilize than a production codec or even a jpeg compressed QuickTime). A handle is a little extra footage at the head and tail of a shot so you can slide things around in editing or use transitions.
    Now bring the rendered footage into AE, create a new comp, and run the Magnum Edit Detector script in AE to detect the edits. This will detect the edits and split the footage into layers. Now create an animation preset by selecting the first layer in the comp, applying stabilize with your favorite settings. Now select Warp Stabilizer in the ECW and go to Animation>Save Animation Preset. Once the preset is saved select the rest of the layers in your comp and select Animation>Apply Animation Preset and push the button.
    Now kiss your computer goodnight and get some rest while it works stabilizing the shots. When the process is complete render your comp, bring the render back into Premiere Pro and do the final edit. Do a scene at a time instead of trying to a whole movie at once. If you want to render individual shots Magnum Edit Detector will even create trimmed pre-comps with the name of your choice for you. This will be much faster than using dynamic link on the entire sequence, it will render in less time, and you'll have more time to enjoy life.

  • Possible to turn OFF "Rolling Shutter Ripple" correction in CS5.5 Warp Stabilizer?

    Is Rolling Shutter Ripple redcution on by default in CS5.5 Warp Stabilizer?  Can I turn it off?
    I am having some strange results trying to stabilize some night-time astro timelapse sequences I shot from a moving car.  There seems to be some warping and "zooming" of parts of my frame, regardless of which stabilization options I choose -- motion, no motion, scale-crop-rotate, subspace, etc.  I've tried every combination possible, including the various border options.  The only thing I can think of, at this point, is that the Rolling Shutter correction function might be struggling to deal with frames shot from a moving car at 4/10ths of a second at night.  Is there any way to turn off the rolling shutter compensation?
    Thanks!

    Thanks Jim.
    The source stitched 176 frames for my test are about 1gb. So trying to get to the bottom of it without someone having to dl them (and it will take a while to put them up). The 8 frame version shows the same effect happening, just exaggerated. But its a fair call to assume maybe it would not happen with enough information to work with.
    The original http://dl.dropbox.com/u/7070604/full_ae_1080.mov I had tried at the time using detailed analysis as well to see if it fixed the issue, and the results were very similar.
    I'd also found that using subspace warp instead of PSR (position, scale rotation), or even just P (position) seemed to generate some additional warping there in the output, and certainly for my footage did not result in making it better.
    However, I have re-run the full footage starting from frames not a movie using detail analysis and subspace warp since you running that over the originally processed 1080 footage seemed to do a pretty good job.
    The results are here : http://dl.dropbox.com/u/7070604/full_ae_1080_warp.mov?dl=1
    You can see the warp is really messing it up, and the zooming is not fixed. Left hand side easiest place to see it.
    Note I've found putting ?dl=1 on any of the links actually downloads them for anyone having issues with it simply playing in their browser. The way I am visiually checking any of these for issues (as many are at 1fps) is to load them into quicktime, change it to View, loop. Then In quicktime 7 holding FFWD. In quicktime 10 hitting forward until it runs at 8x. Looping at 8x is where you can really see the issue.
    The files I had not broken out seperately that are in the source files upload were the results in after effects just using the 8 frames. Here they are seperately.
    http://dl.dropbox.com/u/7070604/1080_rez_p.mov?dl=1
    Position only.
    http://dl.dropbox.com/u/7070604/1080_rez_psr.mov?dl=1
    Position scale rotate.
    http://dl.dropbox.com/u/7070604/1080_rez.mov?dl=1
    Unstablized.
    I presume even with subspace warp you get the same results or worse using these 8 frame files.
    If you ignore the extra warping/twisting in the new file, you have the same results as the original http://dl.dropbox.com/u/7070604/full_ae_1080.mov?dl=1
    played at 8x. The easiest place to see it is the mid left side where you can see it zooming in and out. The fact that it really only starts happening a 3rd the way through makes me think its simply not dealing with the changes in zoom, or the later pan changes in the source file. It wierd the photoshop processed version comes out fine though.
    I was really hoping it was a case of, "ah, I see why it can't deal with those 8 frames, it really needs a manual tracker/stablizer doing x,y,z" But of course I'd be even happier with a tweak to the automated warp stabilizer.
    If I do a 2nd run on the sample file http://dl.dropbox.com/u/7070604/full_ae_1080.mov I notice selecting P, or PSR does not fix it. Selecting Perspective or Subspace (which probably includes perspective) seems to go a long way and have a similar result.
    Leads me back to thinking selecting subspace on the original footage just warps it, selecting P or PSR fixes all but the zooming thing, and then reprocessing with perspective is tackling the persective in isolation which it could not effectively do before. I don't know if that is because you cannot select P&R without S scale. Or because AE's perspective adjustment cannot work effectively with images that have scale variences in them or ?
    I've now run the ouput from a frames start via P and PSR. Brought them back in and prosessed with subspace and P and PSR. Results seems to be no better. There is some special sauce here somewhere with the reprocessing. Maybe its the codec I am going out to in the middle, maybe its the aspect ratio, maybe its ???
    Might be time to u/l the full source files I guess.
    Thanks for sticking with me.

  • Why is Warp Stabilizer so slow?

    I love Premiere, but I just don't understand why the Warp Stabilizer is so slow. I did a test with one minute of footage, exactly the same in and out points, comparing Edius Pro 7 and Premiere CC 2014. Edius Pro 7 includes a stabilizer filter, which I believe is a stripped down version of Prodad's Mercalli Pro. However, the result is still excellent.
    So these are the processing times from the moment I drag the stabilizer effect onto the clip in the timeline for both programs until it's ready for playback:
    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
    So Edius Pro 7 has the footage ready in less than half real time, while Premiere Pro takes between 12.25 and 14.5 times the time of the footage. Surely the result of the Warp Stabilizer is very good, but it seems to me that the way it runs the analysis is very inefficient to say the least.
    The other thing in which the Warp Stabilizer is extremely inefficient is that it saves the result of the analysis in the project file, therefore even after one clip has the Warp Stabilizer applied to it, saving the project takes much longer than it does without it. If you add the W.S. to several clips, the project file becomes gigantic and it takes forever to save.
    It seems obvious to me that Adobe should re-write the code for the Warp Stabilizer from scratch, or license Mercalli from ProDad.

    i agree the warp stabilizer needs improvement, and there are issues with larger project files. so storing this data in the project file would only add to or possibly create the problem.
    it has an accelerated icon next to it, suggesting it uses the gpu. while it might for playback, it doesn't use it for the analyze.   does the edius pro stabilizer use the gpu to get such fast times?

  • Warp Stabilizer progress status

    Hi,
    I need to get an alert when the stabilization process is complete.
    So i try this :
    i am reading the first three text labels on the effects panel :
    During analysis:
    the first label is empty
    the second label display alternatively 
    Time remaining : 41 seconds
    or
    64 % (frame 70 of 188)
    the second label display :
    Stabilization
    During stabilization:
    the first label is empty
    the second label display
    188 frames @ 0:00:21:18
    and the third label display alternatively
    Stabilization ..
    (the number of dots and spaces varies)
    When stabilization is complete :
    the first label is empty
    the second label display
    188 frames @ 0:00:21:18
    and the third label display
    Stabilization
    So i can read the label and deduce the process state.
    // in a scheduled task
    function checkStabProgress()
    var effect = currentComp.layer(1).Effects.property(1);
    var label = effect.property(1).name;
    var label2 = effect.property(2).name;
    var label3 = effect.property(3).name;
    if(label == "" && label2 != "" && label3 == "Stabilization"){
         alert("Stab Complete");
    It's seems to be a crappy way and sometimes an alert prompt before stabilization complete.
    Is there a better way to do what i do ?
    like event listener ? or something more clean and formal ?
    thanks ++

    Although it's easier (more convenient) to accomplish the mission in After Effects, you can do it in PrPro as well:
    1. Nest your shaky footage.
    2. Within the newly  created nested sequence apply Garbage Matte onto the footage to separate the woman on the foreground. E.g. draw Eight-Point Garbage Matte around the woman.
    3. Create a Color Matte, pick e.g. R:7 G:7 B:9 to more or less match its colour to your footage background and drop this Color Matte above your footage with Garbage Matte.
    4. Copy Garbage Matte from the footage and paste onto the Color Matte, delete or disable Garbage Matte on the footage. Optionally apply Fast Blur effect onto the Color Matte and dabble with Blurriness value so as to soften (feather) Matte's edges, adjusting Garbage Matte points if necessary.
    5. Jump back to your master sequence and apply Warp Stabilizer onto the nested sequence, formerly your shaky footage. Set Stabilization to No Motion.
    6. When done, switch to your nested sequence, disable the Color Matte eyeball, switch back to the master sequence, enjoy.

  • Warp stabilize AND slow speed

    I want to warp stabilize AND slow speed which are incompatible, so what is the recommended route on this please?
    E.G. I would anticipate we must export one and reimport to do the other, or what? In which order?  Is there a smarter way?
    Does export reimport degrade the imagery?  These kinds of things.
    Thanks
    Steve Z

    I suggested WS into a DI as first step  because it gives the editor options to do what they will with it later and to save on processing time.
    A nest means the processing is required for 2 major fx during the edit process.

  • Warp Stabilizer error: Unable to acquire rendered frame

    Hi,
    I am trying to apply Warp Stabilizer to a clip. Analyze process starts but then halts after 15-20 frames and a pop-up appears "Unable to acquire rendered frame".
    I have previously used Warp without any hitches.
    Any ideas?
    Thanks,
    Richard

    I too get this, sometimes not and the analyze just drops without a word, but most of the time I get the error. I tried on material such as: Red r3d, uncompressed fullHD/SD, mp4, canon 7D etc. pretty much all formats there is, so there isn't a problem with what type of files or what GOP structure it got. I cannot solve this even by creating a new project or reboot, I even reinstalled AE and the Matrox drivers, I tried unplugging the MXO2 mini but got the same result, so I'm pretty much done testing, I tried everything I can think of. I allocated RAM differently, shut of multiprocessing, enabled it, more RAM to few cores and then less RAM to more cores, increased cashe, disabled it.
    Sometimes when I let the footage play out with RAM preview, the analyze gets to the end in the background, but whenever I just let it work for itself it drops.
    So I tried everything and the error still persist. What should I do?

  • Warp Stabilizer will occasionally choke queueing operation

    That's my guess anyway. Yesterday I queued 100+ clips form the same timeline for export; none of them with warp stabilizer. The process ran like a clock. I could get each clip to the queue almost as fast as I could type.
    Today I tried the same process except a few of the clips had warp stabilizer on them. The rest of the process was the same and Pr acted like a pig. I had to Force Quit 6 times, every clip regardless of effect took much longer to get to the queue. Frustrating.

    When I stabilize a shot that I have in premiere there are two workflows.
    I copy the shot in Premiere in the timeline. I then open up After Effects and paste the shot. In the shot comp I extend the length of the composition to give me "handles" then stabilize, add to the render cue, render to the codec that I'm using in Premiere Pro (usually ProRez 422 HQ or ProRez 444) and replace the shot in Premiere. If you know how long your handles are, mine are mostly 60 frames, then it's very easy to re-sync the edit with room for transitions.
    If there are multiple shots or layered shots in Premiere I'll marquis select everything involved in the sequence and use the Replace with After Effects Composition option. This gives me an AE comp with all of the shots selected including room for transitions if they are in the Premiere Project. If the shot that needs stabilizing is long I'll Pre-compose it in AE, Add handles in the pre-comp, render the pre-comp in AE and replace usage. If it's just a short shot I'll just let dynamic link take care of the AE project.
    I hope this helps. Every project has a slightly different workflow, but in most cases, I'm rendering heavy effects shots in AE and replacing them in Premiere. That's the nature of the work that I do most of the time.

  • Warp Stabilizer Cripples My Computer

    Just want to know if it's normal for the system to lock up if I apply warp stabilizer. It uses about 20-26 GB RAM out of the 32 GB installed. The clips are pretty long , though - 20 minutes or so. Obviously, it handles shorter clips without locking up. But I can't do much better than 32 GB of RAM. It doesn't really crash the computer (not yet). Eventually it does it's thing, but it does freeze Premiere for periods of time.
    I am experimenting with different parameter settings to several clips. I assumed that once the clip is analyzed, I could preview different parameters without having to re-analyze.
    CS6, Windows 7, i7-2600 3.4 GHz CPU, GTX580 Amp! Video card.

    Trying to stabilise a clip as long as 20 minutes is inevitably going to take an enormous length of time, unless there is very little movement within the frames.  It is not likely to lead to an acceptable result as the movement that is present will probably mean the excessive zoom is applied to stabilise it.
    Stabilisation really only works with short clips, ideally with little movement apart from the jitter that is  to be removed.  Otherwise there is simply too much processing required.
    If you persist, you will discover the other problem with the warp stabiliser - it rapidly generates enormous project files leading to Premiere slowing to a crawl.  I hate to think what will happen here with stabilised 20 minute clips.
    I rarely attempt to stabilise a clip longer than 20 seconds - ideally less than 10 secends - and have long since abandoned the Warp stabiliser even though it gives good results on certain types of clip.  I stick to Mercalli 2.

Maybe you are looking for