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

Similar Messages

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.

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.

OpenCL warp stabilizer renders in a small box in the top left corner

Hi everyone,
I have just built a new computer with the following specs:
Premiere 8.1.0 (81) build
i7 4790s haswell-refresh,
16gb Corsair RAM (4x4 DDR3 1600),
Gigabyte Z97MX Gaming 5
2x A-Data SP920 128gb SSD
Sapphire Radeon HD 7750
Windows 8.1 Pro CZ
Now I know this is a very weak configuration compared to other builds here, but I had hoped it would work fine for my amateur Full-HD workflow of clips mostly under 30mins.
The problem is; when I enable OpenCL acceleration, then all clips with warp stabilizer become about 1/4 of the preview window; it carries over to the final render. I have tried this both with the AMD card and without it (having OpenCL enabled with the Intel HD4600). No avail.
Now the funny part is that I used to have this same card running in my previous system; running on an obsolete Gigabyte UD3 with Core i5 750 in it and... IT WORKED! It was with the same Premiere version, running on the same OS. I've ditched that computer just a few days ago, but my new computer has this inexplainable problem.
The build is not the issue, as I had the computer tested and everything is stable with decent temperatures.
I am also having quite a lot of crashes while editing, but I think that's due to the infamous RedGiant suite which as I read on the forums is likely to blame. It's ok, i just need to save often. Would Neat Video be better? Does anybody know?
Another problem is the sluggishnes and lags when my clip reaches beyond 30 mins; I don't think that's ok, my videos produced with EOS M should not be anything demanding for this setup; when I monitor the ram usage, it never gets above 8gb (and yes, I have allowed CC to use up to 13gb of the total ram); also other resources are almost idle during editing.
The sluggishnes and lag is however even worse in SpeedGrade; over there when I move any slider, I need to wait for seconds! It somehow improves over time, but again, I just have an opinion now that this software suite is very very badly made. I am happy I am not using this to make money...
Please correct me if I'm wrong and any links that could help me resolve the problems are super-welcome.
regards,
Jan

Thanks for the report. We believe we have identified the issue and are working on a fix. For now the workaround is rendering in Software mode.
Best,
Peter Garaway
Adobe
Premiere Pro

Warp Stabilizer Script Request

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

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

Warp Stabilizer: How to Start and End Full Frame?

Often I only need to stabilize part of a scene so I just crop the segment to be stabilized. But I want the transition to and from the stabilized segment to be smooth. There is no "timer" so I cannot change the level of stabilization from 0% to 100% over a period of 1-2 seconds. So how do I achieve this?

In the past when I wanted to stabilize a portion of a clip, I'd stabilize the part of it that I needed stabilized and then crop the non-stabilized part in to match the percentage that's scaled and then use the motion settings to sort of move the clip around to match the start or end frame that's stabilized. It's not perfect, but it's fairly seemless. Yeah, it would be nice to gradually de-stabilize something but for now, this is what we do on the rare occasion that we need to do it. Warp Stabilizer in After Effects is a bit more fully featured so maybe there's a way to do it there, I don't know.
Good luck!

Warp Stabilizer getting jelly distortion artifacts

Hi all. I am getting a lot of jelly/jello distortion artifacts when using the warp stabilizer. I've tried a plethora of different settings. Filmed in 1080p/24fps on a Super 35mm Exmor CMOS sensor. It''s smoothing out the movement well which is good but i'm getting a lot of jello-like artifacts in a majority of the clips i'm using. I tried even doing it in nuke, and tried in PP using various 3rd party plugins. They're all giving me similar results. I thought maybe it was a rolling shutter issue, so i tried doing the rolling shutter repair both before & after the stabilization but that didn't work either. I posted a sequence on youtube here and you can see it in several spots.
Original footage: https://www.youtube.com/watch?v=QIgOrK71xqg
Stabilized footage: YouTube

clearly getting the shot right would be ideal. but when a bridesmaid makes a wrong turn at a pivotal moment, sometimes you need to make some post adjustments :-)
The thing is that the footage itself is sharp. It's once the stabilizer is applied that it gets jelly like. Even with the smooth amount set low to like 5%, it's still giving me the same distortion. Isn't that weird? it seems weird to me, but maybe it's normal. I would just think that trading off to just having a low smoothing amount should likewise minimize the jelly artifacts, but that doesn't seem to change it

Warp Stabilizer: Resolution or FPS?

So I have been messing with drone GoPro footage lately and have been trying to stabilize.
With all of GoPros shooting modes, I was wondering what is more important to get good use of warp stabilizer:
FPS or Resolution?
For instance, I can do 4k at 30fps, or 2.7k at 60fps.
Which is more important to fiving the stabilizer clean footage to work with?

Greater pixel depth will make it take longer, but so will a moot more frames per second, so you should just pick whichever you one you want for your finished video. One thing that the higher res setting will do is give you a lot more pixels for it to work wit if it needs to scale and crop a lot to make it stable.
The thing that really affects how well warp stabilizer works is how relatively still you held the camera and how much movement is in the shot. For example, a well stabilized handheld shot of a sunset will stabilize nearly perfectly. Similarly, a shot of say, skiing downhill with some bumpiness but relatively fluid movement of the amber, will also stabilize pretty well, especially if your footage was at high res. But if you're running around with your go pro on, bouncing up and down, and looking up and down and all around at all the passing scenery, warp stabilizer won't have much to work with and will have to crop it way down to just to find enough common frame info (if it can complete it successfully at all).
So the short of it is, warp stabilizer is a super-helpful tool, especially if you don't have the luxury of high end stabilizing equipment, but there's still no substitute for planning and properly stabilizing your source footage as you take it.

Pages zoom and move around when I attempt to write on them

New to iPad. Primary use for which I purchased it was to read and annote pdfs. I've purchased PF Expert, and am extremely pleased with it so far---not only the app, but the support provided by the developers.
My issue may just be due to my lack of experience with the iPad. It is that when I attempt to highlight a document in PDF Expert using a stylus, the page zooms in and out and moves around. This makes highlighting pretty inconvenient. I would like pages to remain fixed, the way a piece of paper would while I'm writing on it. I have wrist protection turned on in PDF Expert.
Is there something I'm missing regarding technique? Or is there something I can set somewhere that will prevent this form happening.
Thanks,
Eric Weir

anyone fix the problem yet?I cleared my cookies and that didnt work.

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.

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.

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.

Crashes after effects with warp stabilizer

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

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

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?

Applying Warp Stabilizer transitions?

I have some experience with warp stabilizer in After Effects.
After having watched the Warp Stabilizer tutorials for After Effects (thank you to community for links)
After Effects Help | Tracking and stabilizing motion
REMOVING TIMELAPSE CAMERA SHAKE: ADOBE PREMIERE TUTORIAL - YouTube
and having played with them in Premier Pro, I find it does a great job of stabilizing the time lapse footage. However, I still notice a slight jerk during the transition from one daily video to the next because each video/day is stabilized independently of the next. The video does not move much from one day to the next so this would only be a few pixels, but it is still noticeable. Is there a way to create a "stabilizing transition" from one day to the next so that in the last 2-3 seconds of the video, the warp stabilizer shifts the image to align the last frame of day one with the first frame of day two? Can I have to trick Premier Pro into doing this by placing the first picture of the second day into the folder of pictures from the first day or is this more painful than necessary? Is there a way to drag and drop a Warp Stabilizer effect across multiple videos in the timeline at once so that the cropping and rotating is done while considering all of the video files? I realize this could result in significantly more cropping than if each video was stabilized individually..
I would prefer to not have to place all of the images in one folder as I would have to rename them for the Import Sequence function to work properly and because there are about 5 months worth of daily folders.
Schwizer

There is no KBSC for adding an effect to a clip.
If you want to add the warp stabilizer (or any effect) to all clips in the timeline: select all the clips and double click on the effect.

Warp Stabilizer introduces roll due to movement around edges

Similar Messages

Maybe you are looking for