What's holding Warp Stabilizer back?

I'm using AE Warp Stabilizer to stabilize some handheld shots (AVCHD, 50fps, 1920*1080), which btw produces excellent results.
I am just wondering, whats holding it back?
A 30 sec clip takes 6+ minutes to analyze. The media file is around 100MB, it uses less than 16GB RAM (32GB installed) and around 8-10% of the CPU?
It could finish in 30 secs. if using full cpu power?

The analysis is meant to occur in the background, allowing you to work on other things, so that wouldn't surprise me.

Similar Messages

Warp stabilizer does'not work

Adobe Premiere Pro 2014 v8.2 30day trial.
When put the "warp stabilizer" to file it doesn't work. Analyze go to 100% and dissapear but on preview screen word "Stabilizing" remain(like stuck). When i try to playback file the screen is black.
I try to reinstall Premiere Pro. Doesn't help. Then i reinstal windows and upgrade from 8 to 8.1, and it's the same problem. Maybe someone can help me.
The system is based on Core i5 + 12Gb ram + 120Gb SSD
Sorry for bad english

Hi... i have same problem.I tried it all and with new saquence but nothing.
It analyze video and everything is OK till the moment when it needs to start with stabilization, then CS6 freezes. Does anyone have any idea what is stopping Warp stabilizer from working correctly in CS6 when at the same time it's working perfectly OK in After Effects ?

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.

What is Warp Stabilization File Extension

When I archived my project to an external hard drive the warp stablization was no longer applied to the clips, so it appears I will be to restablize all clips. Where are the data for warp stabilization files stored, what is their extension, and can they be archived with a project?

We use this effect all the time and pass the project file to various computers who each have their own separate copy of the media and there are no issues or need to re-analyze the clips. It was my understanding that it's built into the project file like Jim said because when we apply the effect our project size jumps from under 1mb to sometimes 70mb or more...granted we use a couple hundred of these effects per project which brings into play all new issues (http://forums.adobe.com/thread/1278013). But yeah, I've never had to restabilize clips when opening the project on a different computer with a different copy of the media, etc.

Warp stabilizer is crashing my project upon open. What do I do?!

Hi guys,
I'm guessing the best thing that I need to do is remove the plugin temporarily from my adobe location, but I can't seem to find it. Anyone have any suggestions on how to remove it or even how to deal with this problem? This is on CS5.5, but from what I've read of WS so far on these forums is that it's causing problems all over the place... (from now on, I will do warp stabilizer and export that clip separately from the project for the final product...)
Thanks!

Wow. Nevermind. I answered my own problem. I was searching for something with the word "Warp" through my files and never tried "Stabilizer"... For those of you wondering, although Premiere realized that WS was absent, it successfully opened my project.

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.

Warp Stabilizer through After Effects Dynamic Link Locks up in CS6

Hey Gang,
I've been using Warp Stabilizer through dynamic link in CS5.5 without issues. However, when I go through dynamic link into AE, then apply Warp Stabilizer, AE locks up?
I can apply any other effects through this path in AE without issue, but when I try to apply WS, I get the "Analyze", but AE stops cold there.
I've tried:
-Opening new project in PP with basic 5 second clip. Then going through dynamic link into AE, and applying warp stabilizer first thing. AE locks up there with the simplest flow.
-I have the latest downloads of the entire production CS6 suite.
-If I apply warp stabilizer directly in Premiere CS6 (which I did not know previously I could do), it works fine! (Just noticed Warp Stabilizer is present in PP CS6, but not in CS5.5).
-If I try to import the Premiere project from AE, AE locks up doing that?
It appears there are multiple issues here:
1. I can't apply Warp Stabilizer in After Effects, and doing so crashes AE.
2. I can't import a Premiere project into After Effects, and doing so crashes AE too?
I'm assuming I'm going to need to download AE again?
Thank you for any help and suggestions you may have!
Derek...
Message was edited by: Derek Emmett

Hello Mylenium,
thank you for your input. Naturally I would expect if my work flow in CS5.5 works great, I would not have to make any changes in CS6 to accomplish the same task. With that said, I made it as simple as possible for CS6 AE to handle the Warp Stabilizer effect, and it crashed? If I went directly back to CS5.5, no problems at all in AE (same source footage, but of course different projects). When I first tried CS6 AE it appeared to work fine, even when doing Warp effects. So when I ran into the issue I saw above, I started thinking it was possible the update I did to AE may have caused some other issue. By the way, the projects I open in both CS5.5 vs. CS6 were independent, meaning, I did not convert a CS5.5 job to CS6, etc... (See notes below).
My setup is standard:
i7 960
16G mem
Nvidia Quadro 4k
Footage is Canon 5D Mkii 1080p
All drivers up to date.
-I think going back and forth between CS5.5 and CS6 may have caused some issues? When I rebooted my system, CS6 AE seems to work fine when applying Warp Stabilizer effects again.
-What I did find more interesting and effective, was that CS6 Premiere has Warp Stabilizer right in its own effects now! Works great in the premiere flow and plays back far better then going through the Dynamic Link with After Effects! When playing Dynamic link effects back in Premiere, I'm sure everyone sees performance issues in the playback. However, in at least with applying Warp Stabilizer directly in Premiere, the playback performance is much better.
Thank you
Derek...

Premiere Pro CC's Warp Stabilizer BUGS...see for yourself. (7.0.1 & 7.1)

I'd love to hear from Adobe Staff on this one. Hopefully they can focus on fixes over features for the next update, especially for one it's most touted effects.
Warp Stabilizer works great at stabilizing clips in Premiere Pro CC...but I'm beginning to learn that it's quite buggy. The two bugs below simply cripple the user experience when you use the effect a lot like we do. Here's a link to a sample project with just 2 clips (around 1 minute in length each) on two separate timelines with each clip stabilized using the Warp Stabilizer effect. It's only a sample/test project meant to show the issue which can be MUCH larger in a longer/bigger project. Relink to any longer media and you'll quickly see what happens when you have multiple warp stabilizers applied to a Premiere Pro CC project and how problematic it can be.
https://dl.dropboxusercontent.com/u/105331144/Warp_Stabilizer_SAMPLE_Project.prproj
See for yourself.
Two VERY Annoying BUGS and One Unfortunate Feature:
BUG #1: (It affects 7.0.1 and the new 7.1 Release/Update)
1) With GPU Acceleration Enabled and both sequences open, once the timeline render bar has turned yellow, hit save.
2) Now toggle to the 2nd sequence and you'll notice a delay/freeze as the render bar switches back to red and then yellow again.
3) Now toggle back to the other sequence and you have the same thing occur. Then, you can toggle back and forth with no delay...until...the project saves (or auto-saves) again...and then the delay/freeze will happen all over again.
4) Side Note: Even when you right-click on the sequence in the Project window, there's a delay. Right-click on a sequence with no Warp Stabilizers and the drop down list pops up immediately.
What's the Big Deal?: When you have tons more warp stabilizer effects applied to multiple sequences, not only does it take a while to save, but when it does, you are forced to wait while Premiere Pro freezes momentarily. This affects AUTO-SAVE too!!! The more warp stabilizers, the longer the wait. Our sequences have delayed up to 30-40 seconds depending on how much we've used warp stabilizer in each sequence. Imagine if you have Auto-Save set to every 30 minutes or less, well that means that every 30 minutes or less you'll be forced to stop while premiere freezes up for 30-40 seconds or so (depending on how much this effect is used). Other effects do NOT have this issue.
BUG #2: (It affects only the new October Release/Update of Premiere 7.1...this issue is NEW and does NOT occur in 7.0.1!!!)
1) Take the above project into Premiere Pro CC 7.1 (again, this does NOT occur in the previous 7.0.1 release) and hit FILE>EXPORT>Media.
2) You'll notice a delay while the EXPORT SETTINGS popup opens.
3) Toggle to different "FORMATS" in the export settings window and there's more delays every time the format is switched.
What's the Big Deal?: Again, this is a small sample project. When you have a much bigger project with lots more Warp Stabilizers applied to many more clips this "delay" can extend up to several minutes!!! Yes, on a recent project over an hour with MANY warp stabilizers applied to lots of clips, it took 7 minutes for the Export Settings window to pop up after hitting EXPORT>Media. And there was about a one minute delay now when switching formats. This occurs whether GPU Accleration is enabled or not. It ONLY occurs on Premiere Pro CC 7.1
UNFORTUNATE FEATURE #1:
We obviously use Warp Stabilizer A LOT. It's a great effect. The above bugs cripple the user experience. This last issue isn't a bug, but rather a default setting on Premiere Pro's warp stabilizer that should be changed. Within the settings of Warp Stabilizer there's a section called "Method". The default setting is "Subspace Warp". That sounds pretty cool. But in practice, and we have had lots of practice (eg. THOUSANDS of clips stabilized in just the last few months alone (no exaggeration)), we've found that switching the default method to "Position, Scale, Rotation" is a MUCH more effective way to stabilize a clip. Most of the time it cuts down on that "wobble" that you might see in complex moving clips...but more importantly, 9 out of 10 times it crops the video either the same or less than when you use the default method. By "crops less" I mean that the "Auto-Scale %" is less. Of those 9 times, I'd guess 7 or 8 of them would crop in on the video less while the other 1 or 2 times there would be no change to the Auto-Scale %. Less scaling = better.
What's the Big Deal?: Well, as cool as Subspace Warp sounds, our numbers don't lie. Again, we use this effect on HUNDREDS of clips every week. When you have to go into hundreds and hundreds of clips every week and keep switching the setting so the effect will work better, it gets old real fast. We end up wasting so much time doing this but it's worth it because the results are undeniable. Why not create a CUSTOM PRESET???! Well, that'd be nice if it worked...but it doesn't. The problem with a custom preset like that is that when you drop it on a clip, it doesn't activate/analyze the clip automatically so you have to manually go into the settings and hit analyze which negates any time saved. It's be great if the default "method" was simply changed to Position, Scale, and Rotation. Or at the very least, it'd be great if one could create a custom preset that would automatically activate/analyze the clip it's dropped on (just like the original effect does).
(BONUS FEATURE: It'd also be nice to have the ability to set a "max scaling %" too so you never crop in more than a preselected amount...but first things first...fixes over features.)
NOTE: I'm on a 2011 suped up iMac running OSX 10.8.5

[r]Evolution wrote:
Would it help to Render these Warp Stabaliized clips instead of leaving them in the sequence w/ the Effect applied?
Any way to "Batch" Warp Stabalize your media before editing so the effect is not needed during the edit?
Sounds like you guys could benefit from having your shooters use a "Stabalizer".
Thanks for the rendering tip rEvolution. Rendering the clips does help with BUG#1, however, I'm not sure if it would truly save us any time because of the constant need to render and rerender tons of very short clips with this effect as we make adjustments to the edit. Warp Stabilizer is GPU Accelerated so playback is really smooth which is great but why does saving a project have any effect on this and cause it to freeze up? And then it works great...until the next time the project is saved. Using any other effect, there is no issue (that I've found) when a project is saved or auto-saved.
Rendering unfortunately has no effect on BUG#2 in Premiere 7.1 (again, this bug/issue did not occur in Premiere 7.0.1)
Regarding "batch" stabilizing...I'm not entirely sure what you mean. We do stabilize dozens of clips at a time before editing because it's imperative for us to know which clips (the sections we've pulled) will stabilize effectively. And then once the longer edit is complete we end up pulling all the best shots from that long sequence and copy/paste it to another sequence to make a 2nd shorter edit.
To say we've gone back and forth about the use of stabilizers would be an understatement. The fact is that we've spent almost 4 years creating a unique way to shoot based almost entirely around the effectiveness of warp stabilizer. It's taken years of trial and error but our style of shooting effectively allows us to mimick and thus replace the need for stabilizers, sliders and cranes. The extra freedom allows us to get MUCH more varied coverage of live events. It's different, I know, but it's fun and rewarding having a unique style. Granted the extra work is passed on to the editing side, but it's worth it IMO especially if these issues were addressed/fixed.
Regarding the "unfortunate feature" I mentioned, I would be satisfied knowing the default method works great for others if one were simply able to apply a custom preset of the clip with the adjusted method and it activated automatically and began analyzing the clip without the need to manually go into settings and hit analyze. That would be nice.
Thanks again for your input.

FR: Big yet incredibly simple improvement to Warp Stabilizer

I love the Warp Stabilizer effect in PP. It's great! But depending on the footage and the effect's settings, sometimes it can actually make things worse. This means that any time this effect is used, users must review of the results after the effect finishes analyzing the clip.
Here's the problem:
Analysis takes a long time, often far too long for a user to stop editing and wait to review the results. In my case, I keep editing, but often I forget where my stabilized clip for review is located. In a multicam sequence, where every video clip occupies the same track, there's little to no visual cues to remind me where the Stabilized clips are. Setting an in and/or out point as temporary markers can work if you have up to two Stabilized clips. But what if you just stabilized 5 clips, and you want to keep editing while they're being analyzed? How do you visually recognize which clips they are? All current solutions add work for the editor, such as moving stabilized clips up a track and then back down after approval of the effect's results, etc. If you have transitions between a Stabilized and an adjacent clip, or clips on a track above it, the situation gets worse.
Here's the (incredibly simple) solution:
Give us a visual color cue any time a clip has the Warp Stabilizer effect added to it! This could be done through a new user selectable color category in the Preferences window's 'Label Defaults' panel.
It's interesting to note that while 8 different colors can be set in the Label Colors tab, only 7 are currently used by PP in the Label Defaults tab, so setting a unique color to this new eighth item should be even easier to program.
Adobe, this would make a great little addition to your next PP update!
What do others think?

Jim Simon wrote:
Your request calls for easy visual recognition of that one effect, mine calls for easy visual recognition of any effect, which I feel would be far more useful to far more editors.
Be as it may, even though I highly doubt that editors need an easier way to determine which clips have any effect applied in general, WS clips would still have to have a different color, otherwise editors wouldn't be able to differentiate WS effects from any other old effect that simply does not require the editor pause or return later to see the results. I've explained this pretty clearly but it seems you're determined to not get it.
Jim Simon wrote:
Or, if you don't want to wait for the effect to finish, add it after editing, as most editors do with most effects anyway. Then you'll have the time to wait to see the results.
Adding effects is part of editing, or isn't it? In case you don't know, editors work differently. If I want to add effects as I do my cuts, what's wrong with that? The software should be intelligent and flexible enough to accommodate a user's workflow. And if it isn't, then it should be improved. If you're an advocate against this kind of progress and think users should adapt to and accept a programs limitations, rather than speak up, which version of Premiere are you using? 4.1?
Jim Simon wrote:
Mark them, as you can do now.
The whole point of this thread and FR is for Premiere to remove steps from our workflow! Still don't get it, do you?
It seems that every time I expose a limitation in Premiere or an area for improvement, you suggest that I should change my workflow rather than have the software improve in a way that could benefit countless other editors. At this point, I really have to ask... what's in it for you Jim? What's your point?
"Then you'll have time to wait to see the results" Is that what you do, wait 10 minutes for a long clip to finish analyzing so you can see the WS results? You're just sounding more and more ridiculous IMHO. It would be nice if overall you made more intelligent contributions to my threads.
Frankly, I'm getting tired of this nonsense Jim. If you have something intelligent to say, please, by all means. If you don't, please stop diluting the message of my threads with your nonsense arguments/comments. If you want all clips with effects applied to them to be labeled with the same color, and thus make WS clips visually indistinguishable (which is the current problem I'm asking Adobe to fix), go ahead and start your own thread.

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?

5 things which should be improved in the Warp Stabilizer

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

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

Warp Stabilizer in Premiere Pro CS6

I was glad to see Warp Stablizer in PP so that it would not require AE. However, I found it to destabilize (no pun intended) Adobe Media Encoder such that the video would fail to render and I couldn't retry without restarting the computer. After about four or so reboots, I tried removing the Warp Stablizer effect from one of my nested sequences and suddenly the render succeeded.
FWIW, I don't know if it's related, but the sequence setting was 720p but the nested sequence that had the warp stabilization applied to only one clip therein was 1080p.
I do have GPU hardware acceleration enabled (not that Warp Stabilizer uses it that I know of).
Is this a known issue, and does anyone have any suggestions for a workaround other than going back to using AE a la CS5.5?
Also, on a side note does anyone know what process I need to kill after a failed render like this so that I don't have to keep rebooting? The dynamiclinkmanager process got rid of a hung Media Encoder on exit but didn't resolve the hung Media Encoder on restarting to render.
Jon

Have you tried rendering just that shot out to a file without the rest of the sequence? If you can do that then you can reimport that shot in to Premiere and use it 'ready-stabilized'.
We've exported several sequences that have lots of Warp Stabilizer clips and not seen the problem (yet!).

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 progress status

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

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

What's holding Warp Stabilizer back?

Similar Messages

Maybe you are looking for