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.

Similar Messages

Script Warp Stabilize

Hi there,
Currently, our workflow within our business is taking large numbers of JPEG stills (50,000 and growing), and stitching into a lossless video, to then be stabilised and deflickred in order to send to clients as a regular view of the progress on their site.
As the number of images/cameras grow, this workflow is starting to mean our two editing stations are almost always stabilizing footage, rather than editing (not ideal...)
As we have a Hyper-V server (16 core, 64gb RAM) that can help with rendering, i'm looking to offload it onto this if possible -
I've managed to script a batch render of stitching the images together into an Apple ProRes file (using FFMPEG), all that remains really is to stabilize
I know I can do this by batch using aerender with command lines of my choice to take in the project files however applying the warp stabilizer will require a script?
I've looked through some examples, and my basic java knowledge is getting me nowhere!
As mentioned, I can already organise as part of my existing scripting a video for example to be saved as "INPUT.mov" ready for AE
This then needs to put into a composition (same resolution and frame rate, but 1080p25 incase I need to specify) warp stabilised, and then output to OUTPUT.mov, and then I can write scripts to take this video and move it/rename to its relevant location.
I know this is possible but its where to start! I've searched the web and forums but come up with nothing for warp scripting, i've only found people using the results of an already completed warp stabilizer in their scripts.
Any help would be much appreciated, it's becoming obvious this workflow isn't scalable and if I could get this working I could ensure all stitched videos are rendered overnight ready for our editors and clients in the morning
Thanks,
Jay

Here's some example code that might help. If you're applying the Warp Stabiliser as a preset you'll first need to add a copy to a layer manually, change any settings as required and save it as an Animation Preset.
var activeItem = app.project.activeItem;
if (activeItem != null && activeItem instanceof CompItem) {          // only proceeds if one comp is active
if (activeItem.selectedLayers.length == 1) {          // only proceeds if one layer is selected
    var theLayer = activeItem.selectedLayers[0];
    var theEffect = theLayer.property("Effects").addProperty("Warp Stabilizer");          // the regular way to add an effect
    theEffect.remove();
    // thePreset = new File("place preset path in here to hard code it in instead of asking user for it");
    var thePreset = File.openDialog("Choose your preset");          // ask user for preset location
    if (thePreset != null) {          // if user didn't cancel the file dialog
      $.writeln("preset path = " + File.decode(thePreset.absoluteURI));          // use this as reference if you want to hard code in the preset path
      theLayer.applyPreset(thePreset);          // apply the preset
      theLayer.effect(1).property("Detailed Analysis").setValue(0);                    // prompt analysis to start

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

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

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

The Next Version of Premiere Pro CC - Warp Stabilizer

With the recent post of what's coming in the next version of PPro CC, I was sad to see no mention of Warp Stabilizer. As amazing of an effect as it is, it needs a bit of help. I know there are improvements and fixes that probably weren't mentioned in the post so I'm still holding out hope. We use Warp Stabilizer more than anyone I know. Several hundred times per week. Yes, per week, no exaggeration. Over the last few years, we've built an entire style of shooting around the strengths of this awesome effect that emulates the use of a slider, steadicam and crane all without having to have them. So we've become really familiar with its PROS and CONS.
Here is a short list of SEVEN things that should be addressed with regards to warp stabilizer within Premiere Pro CC to maximize its effectiveness (and yes we did submit multiple Feature Requests for these so far to no avail):
FIrst and foremost and by far MOST IMPORTANT to us - Allow users to create a CUSTOM PRESET with any altered settings that will engage (or begin Analyzing/Stabilizing) automatically when added to a clip!! This is huge. If you double click on Warp Stabilizer with a clip selected, it is applied to that clip and begins the process of stabilizing that clip. However, the vast majority of the time we need to alter the settings of the effect. If we create a custom preset, that's all fine and good, but when we add that to a clip, it does NOT begin stabilizing. Instead you have to manually go into the Effect Controls for each clip and select ANALYZE. Huge waste of time when adding this effect to hundreds of clips. PLEASE FIX!
BUG when saving projects!!! - If this is not a bug, it needs to be fixed because it's awful. - If you have more than one sequence with multiple warp stabilizations added and GPU ACCELERATION IS ENABLED, then after you SAVE a project (or if it auto-saves) when you toggle between the two sequences you are hit with a delay or freeze while the render bar goes from Yellow to Red...and finally back to yellow again. No work can be done during this delay/freeze. The more stabilized clips, the longer the delay. For us, on our larger projects this delay is sometimes 30 seconds to almost a full minute! Once it turns back to yellow, you can toggle between sequences without the delay...but as soon as it saves again...and you toggle between sequences, the delay hits again. If this is a bug, or somehow a result of Premiere Pro's way of CACHING projects after it's saved, then I sincerely hope it's fixed asap. It's awful!
The third is more of a feature request than a fix - Add the ability to set the maximum scale to work WITH the smoothness control so that if you never want your clips to scale more than say 105%, you can set that and have Warp Stabilizer stabilize the clip and adjust the "smoothness" percentage from the default "50%" down to whatever it needs to be in order for that clip to be fully stabilized and scaled to no more than 105%. Correct me if I'm wrong, but this is not possible currently. Right now we have to manually adjust each clip if it is initially scaled too much by dropping down the Smoothness %.
Another great feature would be the ability to manually keyframe the scaling so that if you have a longer clip that starts fairly steady, then needs to be smoothed out a bit more in the middle, before it ends relatively steady again, you can slowly and seamlessly ramp up the stabilization/scaling so that the whole clip doesn't have to be scaled to make up for the misgivings of one portion of the clip.
Minor bug - sometimes when you have extended the length of a clip, the clip needs to be re-analyzed again. However, the "analyze" button is often greyed out. You need to click away from the clip and then click on the clip again to make that button appear again. Nothing big, but still, a small bug.
After Effects Warp Stablizer VFX feature carried over - It would be nice to carry over to Premiere the ability to isolate what in frame is supposed to be stable (sometimes someone nodding their head can trick the effect into thinking that it's the camera shaking). Great to have it in AE, but would be nice to carry over to Premiere Pro CC.
Finally, I've always believed that no matter how cool "Subspace Warp" sounds, it is not as effective as "Position, Scale & Rotation". This SHOULD be the deafult "method" within the Warp's settings. I'd say 95% of the thousands and thousands of clips we've stabilized we ended up switching the "Method" within the settings to "Position, Scale & Rotation" because it either scaled the shot less or created less "wobble" in the resulting stabilized clip. I know everyone shoots differently, and sometimes Subspace Warp is the way to go, but we have stabilized all sorts of shots with great success by simply switching this setting. Granted...if #1 on this list was taken care of we could then easily have this set as our default setting.
Hopefully this list either reaches someone within Adobe that can do something about them or at the very least inspires others to write feature requests and bug fixes as we have. Even resolving #1, #2 and #3 would be HUGE and would save our editors probably 10 hours per week. It's an awesome effect, far better than "smoothcam" on FCP7, it just needs a little love.

CoSA_DaveS wrote:
All good points, thanks for posting.
For #1, you can make this work in AE at least. This tip is from my colleague DanW:
If you make a preset by only selecting the values you change (and not a preset for the whole effect) then it will auto-analyze on apply.
Simplest way: apply WS, make edits, hit UU to reveal changed params, select all "i-beams" in the Timeline, drag them to the Effects & Presets panel.
For #4, you can get manual control over the scaling by setting Framing to Stabilize Only, and then keyframe Additional Scale to taste. At one point we were going to try to automate this, but found automatic scaling to be very subjective as to the best way to handle it.
For #6, Warp Stabilizer will not track areas with zero alpha channel. So you can pre-mask the input to reveal just the parts you want to stabilize. Do this inside a nested sequence, with Warp Stabilizer applied downstream (in the outer sequence). The just-announced masking & tracking capabilities of the next CC version should be handy for this.
-DaveS, Adobe Dynamic Media, Advanced Product Development
Hi DaveS!
Great to hear that you guys are taking a look at this list. Hope it helps make it better. #1, #2, and #3 are by far the biggest time killers for us so hopefully they'll be able to be fixed/resolved within Premiere soon.
Regarding your note about #1: Allowing this functionality within Premiere specifically would be very helpful. Would it be possible to eventually allow Premiere to auto-analyze when a saved custom preset is applied to a clip? I tried it in AE as you suggested, and couldn't figure it out. But realistically we use Warp Stabilizer on so many clips that round tripping literally hundreds of short clips to AE would be just as time consuming as going into the settings in premiere for each one and adjusting the parameters. We usually adjust the method and then adjust the smoothness scale so that it doesn't "Auto-Scale" more than 104%. That's where our #3 suggestion would help. I didn't quite understand how to make a preset of specific changed values. I tried, but couldn't follow DanW's suggestion. Granted, I'm not that great with AE. I really just use it for the Warp VFX's ability to isolate what in frame is stabilized (hope that comes to Premiere one day) and that's about it. And I really only have to do that a couple times per project. Anyway, I'm sure I'm doing DanW's suggestions wrong but regardless, I'm not sure it would save us much time when we have several hundred individual little clips that would all need to be sent to AE. Any hope for adding this auto-analyze functionality (hopefully allowing a custom preset on the whole effect and all it's adjusted parameters) in Premiere CC?
Regarding your note about #4: That is a valid work around for now. I appreciate that thought. Thanks!
Regarding your note about #6: I think I half understand what you described. I'd have to try it. Although, as I said before, the AE way of doing it is ideal and I just hoped that ability to show the tracking points and delete them over time would come to Premiere CC one day. When the next CC comes out I'd love to try this masking method although I think I'll have to claify exactly what you want me to do just to be safe. Is there no hope to port this added functionality that's in AE's Warp VFX over to Premiere's Warp Stabilizer? Again, not the end of the world for us. I'd rather #1, #2 and #3 be addressed inside Premiere Pro CC for now.
Fixing the first 3 on this list would be HUGE time saver for us.
Thanks again DaveS to you and the rest of the Adobe team for looking into this list. Very much appreciated.

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.

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

How to "analyze" multiple clips with "Warp stabilizer"-effect preset

Is there a simple way to "analyze" multiple clips that have the Warp Stabilizer effect attached?
I have a sequence with 100 clips, which all have a customized Warp Stabilizer effect preset attached. I can attach the effect to all the clips very easily, but afterwards I have to manually press "Analyze" on each clip, which is quite irritating... Is there a shortcut?
I don’t use nesting because I have to tweak the effect-settings on some of the clips…

https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
Yes, sadly custom presets with warp stabilizers don't work correctly. You have to go hit analyze manually for every clip. For you that may be quicker than changing your two settings for each clip. It is a bummer though. We actually use this effect several hundred times per week and prefer the "Position, Scale, Rotation" method in the settings but we can't use the custom preset because it doesn't properly re-analyze automatically like the default effect does. I'm not sure whether it'd be a bug report or a feature request (in my opinion it's a bug) but definitely report it to the link above.

Trying to get value from Warp Stabilizer

Hello everyone!
I want to write a script which can get value "Auto-scale" from all stabilized footages and, depending from the number, will change the colour of footage (layer).
"Auto-scale" isn`t keyframable effect, so I got stuck on how to get it`s value.
Thank you in advance!

If you're after the percentage number, this should help. It assumes your stabilized layer is layer 1 of the active comp:
var myComp = app.project.activeItem;
var myLayer = myComp.layer(1);
var myEffect = myLayer.property("Effects").property("Warp Stabilizer");
var myName = myEffect.property("ADBE SubspaceStabilizer-0017").name;
var numIdx = myName.indexOf("(");
if (numIdx > -1){
    var myPct = parseFloat(myName.substr(numIdx+1));
    alert (myPct);
}else{
    alert("No percentage found.");
Dan

Warp Stabilizer Usage Limitations

Thank you Adobe team for the intergration of Warp Stabilizer. It has fundamentally changed the potential of much of the footage I typically work with.
But the limitations, such as the clip must match the dimensions of the sequence, can't be time stretched or time remapped, are a formidable handicap.
It's easily solved by nesting the clip and applying the warp stabilizer to that new sequence instead. I'm curious if this is so easy for us, why the software can't handle it natively? Can we expect any changes to this in the future?

Some issues were addressed and performance should be better, but no major changes for the CC release due out next week. (informally known as 7.0)
I think (but I'm not sure) that AE's warp stabilizer has some capabilities that ppro's does not. So you might try it there once that's all available to you. Ben's request is good (please submit a FR if you have not yet) but everything takes time and that time has to be prioritized.

Premiere Pro CS6 Warp Stabilizer not using GPU/CUDA why?

Hi,
I installed CS6 and tried the Warp Stabilizer, I undestand that only part 2 of the process (stabilize part) is GPU accelerated, but I can't get any acceleration from GPU, my GPU is idle at 1% usage (GTX580) and all the processing is going to CPU. The renderer/playback is marked CUDA so its not that.
Is there anything I'm missing?
Thanks

OK, this surprised me a bit. I have a state-of-the-art new PC with plenty of RAM, a fast processor and lots of cuda cores. See the specs here: http://www.stevengotz.com/
It took over 10 minutes to stabilize one minute of video - 1800 frames. It wasn't all that shaky to begin with, but it was handheld and therefore looks better after using Warp. There was one section that was so bad, I sliced the clip up and chose not to stabilize that part after the fact. So I thought that it might have added a little to the problem. But no. I tried just 180 frames of reasonably stable hand held video from the same clip and it took almost a minute.
Now, once the process was finished, I had no problem playing it back in realtime without rendering. But what is taking so long? I understand that there is a lot of work to do, but why isn't it using the power I have provided?
This is a screen shot of my resources about two minutes into the process.
I would love to know what I need to do to speed up this process. I get that it is working in the background. Is it possible to make it work in the foreground? I would not mind if it maxed out the RAM or the CPU or both if it would help.
edit: I just submitted a Feature Request to let Warp run in the foreground using every available resource.
Steven
Message was edited by: Steven L. Gotz to include additional information.

CS6. Need to have time remapping and warp stabilizer work together.

This should be obvious for most people. These two effects must be made to work together.
If you're shooting with a glider you're usually moving very carefully (read: slower than normal) so the footage in post would need to be sped up plus stabilized a bit.
Currently warp stabilizer and time remapping cannot be applied at the same time. But I *need* it to be applied at the same time. I need a workaround.
Should I:
1. shorten the clips, export them, re-import them into the project, and then apply stabilizer?
2. apply the stabilizer, export them, re-import them into the project, and then shorten them?
How do I export individual clips as just seperate clips while Premiere? Do I have to drag them into an empty timeline one by one, apply the stabilizer/remapping, and export, remove the clip, put in the second clip, etc all one by one?
I've used Mercalli in the past and I time remap the footage and then apply Mercalli to the accelerated clip. Mercalli doesn't mind a bit.

ComputerNovice25 wrote:
Adobe might have written the code in a way that doesn't include the ability to deal with that extra variable. I'm assuming that when it's nested it then makes the timeline it's in just read it as a normal clip again instead of a clip with a non-supported variable included.
Although I'm totally just guessing, but if what I'm saying is correct it would mean a fix wouldn't be very much work at all. Which means in the future they could simply provide a quick and easy patch to fix this. I'd highly suggest to make a feature request.
https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
Does Adobe read these feature requests? I often have a hard time justifying spending time to type out something when I feel like it's just being thrown into a black hole. I'm sure the team gets thousands of feature requests. It's like the lottery. Statistically you will never win. Sure, you'll never win if you don't play, but it's still a waste of time to play. I know, I'm pessimistic. Just don't have much faith in conglomerates - although Lightroom 3 is by far the most perfect program I have ever used and I would kiss the LR3 team if I could.
With Lightroom, Photoshop is hardly needed anymore unless absolutely necessary or for truly intensive chop-like edits. Premiere DESPERATELY needs a Lightroom equivalent.
I have half a mind to guess (nicely) that you video guys have absolutely no idea what you're missing out on, workflow-wise. It's life-changing. Literally.
I'm doing a video right now and I can't stop thinking about how if I had a Lightroom workflow, this video consisting of 40 clips, 40 titles, 40 transitions, audio tracks could be on the way to final export in 5 minutes. 5 MINUTES. And be 100% as good as if I had to spend an hour doing this in traditional Premiere.

Warp Stabilizer VFX, did you know

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

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

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

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

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

When is Adobe going to fix Warp Stabilizer?

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

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

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

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

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

Warp Stabilizer Script Request

Similar Messages

Maybe you are looking for