Can warp stabilizer ignore a portion of my film?

I work at a film archive where we use a digital scanner to capture images from 35 and 16 millimeter film frame by frame. The result is a file with what we refer to as "overscan" where the perforations and some of the information from the preceding and following frames are visible.
This works very well and turns out beautiful results, but the film will often have a slight bounce to it. I've found that warp stabilizer works very nicely to reduce or even completely do away with this bounce on clips that have an immobile camera. I do not wish to stabilize camera shake (that wouldn't exactly be preserving the work), but I do wish to stabilize this bounce.
Is there a way for shakier footage, for example, a collection of home videos we've been attempting to stabilize, to be masked off in some way so that the Warp Stabilizer focuses only on the bounce of the film itself and not the shake from the original operator of the camera? I imagine there must be some way (without point-tracking, preferably) to focus the stabilizer on the perforations or some part of the film itself rather than the footage it contains.
I've looked at the videos where keylighting is used to "outsmart" the Warp Stabilizer's assumptions about foreground, but unfortunately that doesn't exactly work for my particular problem.
Any help is very much appreciated.

No, unfortunately not. At this point there is no way to differentiate between different types of shake e.g. by ways of additional trackers or mask paths like you can do in some plug-ins. It's an all or nothing thing.
Mylenium

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!

Warp Stabilizer and Speed can't be used on same clip

...just my luck that on my first ever Premiere project (CS6) I'm building a timeline and need to use both the Rate Stretch Tool and the Warp Stabilizer on multiple clips. The message, "Warp Stabilizer and Speed can't be used on same clip" took me by surprise.
However, after research here on the Forum, I found a Workaround that I'm deploying:
"Apply the effects, nest and finally apply warp stabilize" Ann Bens
Here's what I did:
In my only sequence -- Sequence 01 -- I highlighted a clip that I had already applied Rate Stretch to.
chose Clip/Nest
This created a Nested Sequence 02 with the clip in it.
In Sequence 01, the clip now says, "Nested Sequence 02"
I applied the Warp Stabilizer to the Nested Sequence 02 clip and it worked. Both Rate Stretch and Warp Stabilizer have been applied to the same clip!
So I've done this like ten times to ten clips and now have 10 Nested Sequence folders.
Questions:
Are my step-by-steps correct?
Do I let these multiple Nested Sequences just keep piling up? (when I right click on a Nested Sequence and choose Clear, I get a warning message that I'm going to delete clip references)
Now that the workaround has worked, is there a way to close -- unlink -- from these Nested Sequence folders? If so how?
I am so Over My Head for a first project. I thought you could always compound Video Effects!
NotOnSugarMountain

Best is to make a copy of the timeline or clips that you are going to multiple nest etc.
If you screw up you can easily replace nested clips etc with a copy from the copy you made.
There is an undo function but most of the time its not enough.

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.

Can I export Warp Stabilizer Data?

I have two identical video clips, they match frame for frame, however one of them is under exposed and is a lot darker. Therefore it is a lot harder for warp stablizer to work.
Can I somehow export the data from the warp stabilizer on the clip that it works on to apply it to the under exposed clip?
I would use Mocha to stabilize the shot, but I am having difficulties with it, since it requires frames to match throughout and my shot is rotating.
Any help is greatly apprecaited TIA

If you have identical footage then you either had a motion control camera, and even then it's highly unlikely to be exactly frame for frame unless the rig was very big, heavy and expensive and your actors were robots because anything moving in the scene would throw off the warp stabilizing, or the camera was locked down and there was nothing moving in the scene. There must be some differences in the shots or there would be no need to work on the one that is under exposed.
There is nothing keeping from you from making exposure or color grading adjustments on the original clip then pre-composing or rendering a clean copy, and warp stabilizing that clip. I don't think anything else is going to work.

Problems with Warp Stabilizer -Testversion After Effects, who can help ?

Hey can someone tell me why the Warp Stabilizer is not working at the testversion. Is is only activ on the registrated version ? Wanna figure out whats better at this stabilizer compares to the final cut Motion 3 d stabilizer befor i buy a expensive software that doesn´t make it better, thanks a lot for any answer..simon germany

thanks..will wait and try....thanks for the link
Am 17.04.2011 um 05:57 schrieb Todd_Kopriva:
The trial version will be available in May. See http://blogs.adobe.com/toddkopriva/2011/04/improved-trial-version-for-after-effects-cs5-5. html.
>

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.

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.

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

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

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

Warp Stabilizer introduces roll due to movement around edges

I'm finalizing a year's worth of daily photograpy into a time lapse movie. Of course the daily shots never quite line up, and I need to stabilize the image sequence. I'm using the Warp Stabilizer in Adobe CS 5.5 (10.5.0.253) version on a Mac MacBook Pro Core i7 with a 1Tb SSD HD and 8Gb of RAM.
Because this is year-round outdoor photography, various conditions like snow, rain, humidity, etc. cause tree branches in outer 1/3rd of the photos to droop or rise up. The stabilizer ends up using these objects to stabilize, instead of the more stable elements (ground, rocks) in the center of the picture. It causes AE to "roll" the photos back and forth. You can see the images I'm using for this on my Flickr account here: http://www.flickr.com/photos/30664653@N03/sets/72157633131214843/ and here: http://www.flickr.com/photos/30664653@N03/sets/72157634112948001/ (I also have a 3rd still unpublished site)
Is there a way to define the area, or tracking points, used in Warp Stabilizer, or perhaps tell it to ignore the outer 20% of the picture? Or do I need to go the more manual "Tracker" route to accomplish this?
I also tried using Photoshop to align the pictures, but with an image set of 390 photos (some days more than one photo was taken), photoshop just chokes.
Once I get my last photograph the morning of Dec. 31st, I'm hoping to have all my time lapses finished, uploaded, and published by 5pm New Year's eve.
Any suggestions would be greatly welcome.

AE CC will allow you to isolate areas in the WarpStabilizer. CS5 will not. I do not think that is the right tool for the job.
I took a look at your photos and there's not much there to lock on to. Humor me and read the following story.
I did a similar timelapse project in Glacier park a bunch of years ago. We packed 15 miles in to the wilderness on horseback with a surveyors transit, 4 sacks of concrete and some hardware to set up a mounting base for a movie camera late in August. At the location I did some survey work, checked the sun path tables, made a bunch of calculations, shot some stills and set up a permanent mounting system by pouring concrete and setting mounting studs in the ground so we could return and mount a Mitchell 35MM camera on a set of Baby legs with a motorized geared head and a Tobin motor controller. From my calculations I planned that the camera would shoot 1 frame every 80 seconds from sunrise to sunset tracking the sun across the sky.
Early the next spring, the first time we could get in through the snow we packed in with the camera gear, located our mounting pad, and then spent 2 days doing time lapse. We returned every two weeks until the snow became so deep we could not get back in. We ended up with a boat load of time-lapse footage panning from east to west from sun rise to sun set. The sequences were combined in post so the camera action matched exactly and the seasons changed as we panned across the scene. Starting with a sunrise on a snow covered valley, seeing the wild flowers bloom by the time the sun was 1/4 the way across the sky, then the full glory of summer at the half way point, to leaves turning gold and snow falling at sunset and deep snow at dusk. The shot worked because of planning and accuracy. There was no such thing as camera tracking when I did the shot (1978 - 1979), it was all matched up on an optical bench a frame at a time.
This story brings me to my point, you've picked a very difficult scene with only a few immediate foreground objects to track. The best way to line those objects up would be to use Photoshop's Edit/Auto Align. Portrait photographers use this tool to line up group shots so they can easily replace faces. I gave it a try with a screen cap of 6 of your photos. It works fairly well, but there are slight differences in camera position and angle that make perfect alignment difficult. I'm sure that this will work much better than WarpStabilizer and you can tweak the frames that don't quite match up by hand. Load your Photoshop file as a composition and sequence the layers.
Next time you plan a project like this make sure that there are several areas in the image with constant immobile geometry. We used the ridge line of the distant mountains to pull off the shot I talked about. I wish I had a link to it, but the client has held on to the footage like it was the Hope Diamond.
http://help.adobe.com/en_US/photoshop/cs/using/WSAA03F5FB-2F22-49a1-A824-5BEB70A58951.html

Warp Stabilizer Questions

Hello,
I have been using Warp Stabilizer in the CS6 release of Premiere Pro. I've noticed 2 things:
1) I have a sequence with a clip using Warp Stabilizer effect that has been rendered. If I add a clip directly after it and add a cross dissolve transition, it requires the entire first clip to be re-rendered. On complex stabilizations, this can take hours to days. Is there any way to have it only require a re-render of the impacted portion of the clip instead of the entire thing?
2) If I set my work area to a complex clip (synthesize edges, detailed analysis) with Warp Stabilizer and render the entire work area, it appears the efficiency goes down. I'm not sure how this is possible, but the estimates of completion time (and watching the elapsed time vs percentage compete) seems to indicate that it may exist. If I segment the work area to smaller regions in the clip and work my way through it, the total clock time to complete seems to be much faster. In one example, it seems to go from 80+ hours down to about 12 hours. In both cases it takes 100% of the CPU (8 cores) and a large portion of the ram (8-9+ GB). I believe the performance options are set correctly.
Any suggestions?
Regards,
Jonathan

Hi Jonathan,
I hope you get a good answer from the gurus at ADOBE on this one. I use ProDADS Mercalli V2+ Stablizer in Cs5.5.2 with 4 cores Xeon processor, i suggest you trial it as I have had no issues with the exception of cutting the clip after stablization, do it befor hand. I was thinking of upgrading to 6.1 ?
Good luck

Warp Stabilizer VFX, did you know

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

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

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

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

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

When is Adobe going to fix Warp Stabilizer?

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

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

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

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

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

Can warp stabilizer ignore a portion of my film?

Similar Messages

Maybe you are looking for