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.

Similar Messages

  • Best way to warp stabilize between premiere cs6 and AE cs6

    I have a sequence with many clips, some with different speed (warp stabilizer doesn't work with speed in premiere CS6) whats the best way to stabilize these videos that are in different speeds?
    Another question, in CS 5.5 I used the warp stabilizer in 1080P clips on a 720p composition (with fit to composition) this way I warp stabilizer could zoom/crop the video without loosing quality. Now premiere CS6 has warp stabilizer but I can use a 720P sequence with a 1080p video, warp stabilizer won't accept it.So whats the best way to do this in premiere CS6? (to get 1080p video stabilized in 720p sequence) or I can just stabilize in 1080p and export the final video to 720p and I will have the same quality?
    Thanks

    You can make a new sequence from that 1080p file, stabilize it, nest it, then copy and paste it into your 720p project. This way you won't need to export it beforehand.
    I notice this topic is old, but it may help someone.
    Best,
    Bogdan

  • Premiere Pro CC Warp Stabilizer with activated Mercury Playback Engine - GPU doesn't use the Nvidia GTX Titan GPU - CUDA

    Windows 7 Pro, fresh installation, include all updates
    Premiere Pro CC - actual version
    Gainward GTX Titan Z - actual firmware and driver
    SSD Hard Drive
    Intel i7/ 960/ 3.2GHz/ 32GB RAM
    Mercury Playback Engine - GPU is activated.
    Card is known by standard in cuda_supported_cards.txt
    Selected Clip: 1920x1080i, 25fps, AVCHD/mp4
    Seleceted effect: Warp stabilizer with Subspace-Warp (Standard-parameters)
    Step 1: Analyse the clip
    The Intel i7 is working with 90%, not the GPU
    The status monitor of the Nividia-card shows 0% used performance
    Playing the analysed clip (informations from the Cuda Render System):
    Total render time: 26ms
    Display FPS: 0.82
    Scheduler FPS: 2.28
    Target FPS: 25.00
    Rendered FPS: 3.50
    Total: 239
    Dropped: 234
    => Playing the analysed clip is dropped extremly.
    Step 2: Rendering the clip
    The Intel i7 is working with 90%, not the GPU
    The status monitor of the Nividia-card shows 0% used performance
    The Warp Stabilizer is shown as a GPU-Cuda supported effect.
    The GPU doesn't help the Intel i7....?!
    Please help me!

    Thank you for your fast response!
    Warp-Stabilisation shall be a GPU accelerated effect.

  • Warp stabilization render problem

    Hi,
    I would like to ask if it's possible to render (export) in the same quality after warp stabilization like the original file? (shot with 5D 1920X1080 25fps)
    Itried with best settings, lossless
    with current setting, lossless
    same settings as composition, lossless
    but all seem to be uch worse quality than original file. If I open it for editing in FCProX or Premiere still worse than the orginal next to it.
    Thanks:)

  • Before render, option to warn user of pending warp stabilization of pre-analysed clips

    Hi, I work with hours and hours of footage, and sometimes it is almost impossible to go through every clip and check if warp stabilizer needs more frames to analyse, as well as other affects that have a blue, red or green line across the clip which renders with the project in use.
    I was wondering if there is a script/option that can warn a user before rendering a project that warp stabilizer needs frames to analyse as the ''Media offline'' warning that comes up when media is missing or misplaced?
    Looking forward to any help as this can save me hours of time, I am sure users out there are eager to find a solution to this too.
    Thanks, Ckerux

    I second this motion! would love to know if there's a way, or put in a request to add a feature for something to flag us that there are clips that need to be analyzed/re-analyzed.

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

  • 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 error when using dynamic link

    Hey guys,
    So I'm very new to video editing, and not surprisingly, I'm running into problems.  I'm trying to use dynamic link to allow me to Warp Stabilize and color correct video clips in a Premiere Pro project.  When I try to apply the Warp Stabilizer (through dynamic link) in After Effects, I get this error message:
    After Effects error: Stabilization analysis doesn't work with Collapse Transformations (514)
    (25 :: 101)
    I read the only other thread on this which linked to the following page:
    http://help.adobe.com/en_US/AfterEffects/9.0/WS064964FC-424C-4e5a-A5C3-2160B3DFBCA4a.html
    Unfortunately, that didn't help me much.  Maybe the answer is in there somewhere, but if so, its way over my head.  Can anyone give me a simple explanation of why this doesn't work?  I feel like it should be a simple solution so I don't have to go through the process of importing into AE, render, export, import to Premeire Pro, and replace the clip there, blah blah.  This is what dynamic link is for, right??  Thanks for any advice you guys have!

    Not sure I properly understand you...
    As for me, the solution is in AE warning message - just disable Collapse Transformations switch in your AE precomp...

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

  • Warp stabilizer analyze alert burned into output

    Hello. Having a problem that I have not been able to find an answer to online. I have a clip in a timeline that has warp stabilize on it and when I export using media encoder the output file shows the analyzing bar rendered across the screen. This only happens with media encoder sequences sent from premiere. Doesn't happen if I just export from premiere. Trashed media encoder prefs but that didn't help. The clip is h264. No other effects in the clip. Any help would be greatly appreciated. Thanks! Chris

    Hi RameezKhan!
    Thanks for the input!
    Unfortunately i can't change the renderer, software only for this mac...
    I deleted the media cache and render files right before this happened so i didn't think that would be it...but I did notice that when I re-opend premiere that one clip would always need rendering again...
    I deleted media and render files again and it's been fixed...
    I though media encoder didn't use the render files...maybe it uses the cache and that was the fix.
    Either way it's working.
    Thanks again!
    Chris

  • Warp Stabilizer Causing Jumping?

    I am new to Premier Pro but I have messed with it some here and there. I have a video that is taken using a hand held camera and is at times a bit shaky. I attempted to add Warp Stabilizer (using default settings) but when I render the video it has a jumping or flicking motion. If I remove the warp stabilizer it doesn't do this.
    Is this a side effect of the stabilization and how do I solve this issue?

    Is this a side effect of the stabilization and how do I solve this issue?
    It would be called 'Warp De-Stabiliser' if this was meant to happen!
    You may need to do some more trial and error testing with your particular footage. Settings.
    BTW there is a practical limit to how effective these stabilisers can be.

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

  • 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 do I keep Warp Stabilizer and aeselflink from filling my swap space?

    Hello,
    I'm running the lastest version of AE on OS X, when I try and run warp stabilizer on a composition, aeselflink grows the virtual memory it uses (> 50GB) until it fills my swap space and causes my machine to hang, because the hard drive is full.
    Running AE's Edit->Purge options has no effect on the amount of virtual memory used.  I have to quit AE to get aeselflink to quit and free the memory used.  How can I limit the virtual memory used by aeselflink to something reasonable? 

    I'm not aware of a way to control this in any more detail, but this stuff obeys the settings you make in the Render Multiple Frames Simultanuously prefs if used. Otherwise it will use factory defaults which should never use more than 4GB. Anyway, the behavior you see is highly irregular no matter what. Sounds like a memory leak, so maybe you can provide more info, including which AE version, what footages etc.
    Mylenium

Maybe you are looking for