Memory using Warp Stabilizer

This is bull. Here are my specs. 12 core mac pro, 2.93 Mid 2010. 32 gb ram. Radeon HD 5870 graphics card, and ruinning on prmiere pro cs5.5 and after effects. I am tryiung to use the new warp stabilaztion effect in after effects and after effects in general does not utulize any of my cores let alone the ram. It is stupid. If you look to the top right of the pictures at my mac menu bar, you would see bars for all my cores and only one is utulized. check out some pics while stabilizing my clip:
What the hell am I supposed to do to speed this s=process up.

The Warp Stabilizer effect is processed in the background so that you can continue working in After Effects while the analysis is taking place. It is deliberate that the Warp Stabilizer isn't consuming all of your resources, allowing you to continue to work in After Effects as normal while the analysis is done.

Similar Messages

  • Film in 4k to use on 1080p sequence. Can't use warp stabilizer.

    Hi all,
    So, I've been filming using 4k resolution with the intention of using it on a 1080p sequence. The reason I use 4k is so I have the extra pixels to play with when I use the Warp Stabilizer. BUT, it seems this is not possible to do, as Premiere Pro CC says I need to 'nest' the 4k clips before I can use warp stabilizer. The problem with that is that, 'nesting' a 4k clip to match the 1080p sequence video dimensions, means the 4k video gets cropped to 1080p, thus loosing the extra pixels I had and making it completely pointless filming in 4k in the first place.
    It's my understanding that a lot of people use a higher resolution than sometimes needed when filming, so they can crop / stabilize the footage without loosing the quality...but how are they doing this?
    Any help with this is greatly received
    Thanks,
    Paul

    After you put the 4k video on your timeline and you "crop" it (size it) the way you want it to be seen in the 1080p frame... then export the video using "match sequence settings"... this will give you a 1080p file... put this on your timeline and then you can use Warp Stabilizer!

  • 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

  • Getting an error when trying to use warp stabilizer

    I made a picture slideshow with some videos and I am trying to stabilize my videos. When I click on "Analyze" a red bar comes up saying: "Warp Stabilizer requires clip dimensions to match sequence". Is there an easy was to transfer everything over to a new sequence that matches the dimensions? Also I am using Premiere Pro CS6.

    Try nesting the clips and then adding the warp stabiliser to the nest.

  • Using Warp Stabilizer results in a black preview screen.

    I have been trying continuously for the past two days to get Warp Stabilizer to work. It actually did work once, so I know it can. But mostly all I get after it has gone through the procedure is a black preview screen. Or no result, not seeming change at all, even though it has gone through all the steps! This is happening when I have selected the "No Motion" result, the "Smooth Motion" result seems easier to achieve.
    I need something finished, and I am at my wits end. I have tried making the test bits shorter and shorter, because I saw on another forum a suggestion the the power of - or available space on - the pc might be the problem. But my laptop should be strong enough, it has been able to handle everything else I have thrown at it over the pas couple of years.

    Hello,
    I tried Warp Stabilizer but, now I ma working with ProDAD Mercally V2. The problem I had were : freezing of Premiere Pro and "paste" of the video which followed the mouse.

  • 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 and speed can't be used in same clip.  explain error message please.

    Learning - from how to capture to how to do basic edits. 
    Trying to use warp stabilizer on some hand-held footage and got the red "NO" message. 
    Can I still do this, or did I do my edits in the wrong order as in I should maybe have used warp stabilizer first or something. 

    I have used various stabilisers over the past ten years, and have always found that the best stabilisation results are achieved with the raw footage, unless this has very low contrast.  In that case it pays to apply a levels effect first.
    I always export my stabilised clips to an intermediate file using a "lossless" codec before importing that new file into my project to replace the original footage.  I use the free download UT codec for this.  I have tried Lagarith and the free Avid DvxHD, but have had problems of one sort or another with each.
    Speed changes never work well when the clip needs stabilising, in my experience.

  • Warp Stabilizer in CS6 does not work at all

    When using the CS6 Premiere Pro Warp stabilizer it starts to analyze but doesn't start to convert after it has finished analyzing.
    - Add the Warp Stabilizer
    - Blue bar over picture shows up "Analyzing in Background (Part1 of 2)
    - Prozess finishes but nothing happens (Source does not get corrected, orange bar never shows up)
    - Another blue bar shows "Click Analyze to begin"
    When pressing Analyze the process starts over again without any result.
    The used footage is some mxf from a Canon C300
    The used PC gots 8 cores, 32GB Memory
    Update:
    When using a different Clip, or if i shorten the problematic clip, it seems to work now
    Info to problematic clip:
    File Path: xxx.MXF
    Type: XDCAM-HD Movie
    File Size: 44.5 MB
    Image Size: 1920 x 1080
    Frame Rate: 25.00
    Source Audio Format: 48000 Hz - 16 bit - Mono
    Project Audio Format: 48000 Hz - 32 bit floating point - Mono
    Total Duration: 00:00:07:05
    Pixel Aspect Ratio: 1.0
    Compression Type: MPEG 4:2:2

    I could not help laughing at Jim's remark. I remember showing my 20 minute video of our trip to Italy to my brothers way back in 2002. In fact, it was my first Premiere project. I had the sense to cut it way down from 20 one hour tapes to 20 minutes. My oldest brother may have thought he was being a little insulting with his remark, but I was overjoyed. He said "It looks like a PBS travelogue." That was, of course, exactly what I was going for with the video and the voiceover.
    In any case, I was able to use Warp Stabilizer this weekend on some footage of a children's birthday party. I can't show the results because of the subject matter. Not that they were doing anything wrong other than savagely beating a poor Super Mario Brother's pinata, but I don't have a release for them all.
    I was a bit surprised at how long it took. I have a state of the art PC, and apparently the GPU doesn't help. I liked the results, but I sure would like to know what resources the effect utilizes. This is a screenshot of what it looked like about two minutes into the 11 minute process (the effect window estimated 8 minutes) for stabilizing a 60 second video (1800 frames). I think maybe I will start another thread to inquire about this. The CPU wasn't even breathing hard, the hard drives I am using for cache are in RAID0 - so should be reasonably fast.  Hmmm. I wonder?

  • Warp Stabilizer Constantly Crashing Premiere Pro CC 2014

    I have never had an issue applying warp stabilizer to clips, now it constantly crashes my system during the analyze phase. Does not seem to be an issue with any other effects. Have the most current version of premiere CC 2014. Running Windows 8.1 Plenty of memory, etc. Has never been an issue, now it happens every time! Help!!

    I am having similar issue - without the crashing. Any clips I use warp stabilizer on do not retain their render after I close the project.
    What version of Premiere Pro? Include the minor version number (e.g., Premiere Pro CS5.5 with the 5.5.2 update).   v8.0.1 (21) build  2014.0.1 release
    Have you installed the recent updates? (If not, you should. They fix a lot of problems.) Cloud says i'm up to date
    What operating system? This should include specific minor version numbers, like "Mac OSX v10.6.8"---not just "Mac".  Windows 8.1
    What kind(s) of source footage? When telling about your source footage, tell us about the codecs, not just the container types. For example, "H.264 in a .mov container", not just "QuickTime".    mp4 from a gopro
    If you are getting error message(s), what is the full text of the error message(s)? no error
    What were you doing when the problem occurred?
    Has this ever worked before? no
    What other software are you running? Chrome
    Do you have any third-party effects or codecs installed? No
    Tell us about your computer hardware. Be especially certain to tell us about third-party I/O hardware (e.g., AJA, Matrox, Blackmagic, MOTU).  Dell latitude e7440 8gb ram, ssd
    Are you using Mercury Playback Engine GPU Acceleration? i dont think so
    Does the problem only happen with your final output, with previews, or both?  clips do not stay rendered in timeline after saving/close a project and reopen

  • Warp Stabilizer Doesn't Render

    Hi, I've been having trouble lately using Warp Stabilizer in Premiere CC 7.1. I had used the effect many times successfully, then it suddenly stopped working. It analyzes the clips without problem, however it seems to get stuck on the "Stabilizing" phase. It just sits there. As I try to playback the clip in the timeline, it simply shows up as black video in the viewer. The space above the clip on the time line is yellow. Has anyone experienced anything similar? I've done a full uninstall and no luck. I don't have any other problems in Premiere Pro CC 7.1 right now.
    Steve

    I've had some problems with the effect completing, but usually only on clips what were especially long or demanding (like 4k with lots of movement). Additionally I have either encountered or read of others encountering these issues:
    With OpenCL Rendering on, stabilized effect rendering does not complete
    Large amount of memory is somtimes used when during Warp Stabilizer analysis phase (which is probably the root cause of the first problem I mentioned)
    Long progress pause (minutes) during auto-save while applying Warp Stabilizer
    Hang when saving project after extending warp-stabilized clip and re-analyzing
    Those don't all necessarily occur reliably, but they have happened for some users. I'm not necessarily saying they;re causing or even related to what you're seeing, but perhaps they offer some clues. In any case, it doesn't sound like an issue that would be addressed by uninstall/install, but it could be addressed by doing things like clearing your media cache, checking your available memory, etc...
    The workaround I would have suggested is to use AE if possible which it sounds like you did successfully already.

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

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

  • 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 crashes in After Effects CC (OS X)

    Every time I try to use Warp Stabilizer, I get the following crash.
    1. I select a track, open up the Warp Stabilizer VFX panel, and click "Analyze".
    2. The blue "Analyzing in Background" banner appears. At this point, After Effects locks up and becomes unresponsive.
    3. Looking in Console I see "com.adobe.Adobe Analysis Server.application[285]) Job appears to have crashed: Abort trap: 6". A crash report is saved. Here is a report: http://pastebin.com/RTnjNW28. Pertinent extract:
    Application Specific Information:
    abort() called
    terminating with uncaught exception of type dvacore::filesupport::dir_create_exception: $$$/dvacore/filesupport/DirCreate=The directory '@0' could not be created. Please check the parent directory protection or permission rights.
    4. Within After Effects itself, after several minutes, the error "Could not launch the Adobe Analysis Server. (515) (25 ::101)" appears. After Effects then becomes responsive again.
    This is on a fresh install of After Effects CC, installed via the Creative Cloud app. Version 12.2.0.52.
    I have tried this on 2 different Macs: a 2013 MacBook Pro and a 2011 Mac Mini. Both with latest OS X 10.9.1. I also tried on the preview release of OS X 10.9.2. I have tried with several different source videos, of different formats.
    I have no virus scanner, or other such apps installed. I have tried disabling all running background apps. I tried turning off FileVault. Rebooted several times. Same result every time.
    Is there any fix? Any help greatly appreciated.

    It seems that this issue is caused by some folders being created with the wrong permissions set. This morning, a new version of the Creative Cloud desktop application was released that fixes this issue.
    See this article for more information:
    http://blogs.adobe.com/kevinmonahan/2014/02/12/prevent-crash-on-export-with-premiere-pro-c c-adobe-media-encoder-cc/
    That article doesn't mention After Effects specifically, but I'm reasonably sure that the same fix will help here.
    Let us know either way.

Maybe you are looking for