Warp Stabilizer Questions

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

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

Similar Messages

Precomposing & Cropping & Warp Stabilizer? *Beginners Question*

Hi guys,
I'm new to AE and have been trying to follow instructions from this link (http://www.sinusdigitalus.de/2011/05/06/my-first-test-with-the-new-adobe-cs55-warp-stabili zer/)
I've taken out the important bit here -
"i´ve imported my sequence and applied the warp stabilizer on it. the first instance of the stablilizer was to stablize only the movement of the position, scale and rotation with a crop but with no rescale to keep the image quallity. i´ve precomposed the shot and resized the comp with the new dimentions of the shot after the crop. on this i applied a new warp stabilizer and this time i´ve stabilized the perspective also with crop but no rescale. again precomposing and rescaling the comp to the new dimensions. then i applied a third warp stabilizer on this new comp and did it again. this time with the subspace stabilization."
- As he mentions at the begining, it's not an indepth tutorial so where I'm tripping up is the precomposing and cropping.
I'm trying to stabilise a jpeg sequence using this guy's method (he passes it through Warp Stabilzer 3 times).
When I hit the Precomopse button it gives me 2 options and a box to tick whether or not to open new composition, which ones do I pick? And when that's done, how do I crop it so it's applied to the whole jpeg sequence before I use Warp Stabilzer agiain?
Thank for your help.

Not tried it but could you make a 2.7k sequence and warp stabilise that, using stabilise only or stabilise and crop. Then add this sequence to the 1920x1080 sizing to suit.

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.

Best way to warp stabilize between premiere cs6 and AE cs6

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

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

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

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

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

A command to analyze all clips onto which a warp stabilizer has been added?

Ahoi gente!
We are working on a 90 minute piece -and getting through the project manager took time and nerves. Clips are still missing in the collected project created by the project manager...
Anyway - the real question is: Is there a way to filter the clips in the timeline to only show the ones with a warp stabilizer on it? Or a command to analyze them all?
Otherwise I have to look through all of the clips and click analyze again....
Recommendations? Thanks a LOT!

Hm, I did learn some lessons in all this - but not using an NLE to manage the files...?
I thought next time we should give unique names to files instead of building up a structure of folders on the external hds, work with proxies, dividing the project in more sub projects more often to increase performance etc.
But how would you get rid of not used files instead of using the project manager? Manually?

Starting the new multiple point Warp stabilizer

I do aerial photography with a large rc helicopter. Camera movement is hard to get rid of. I am looking forward to the upgraded Warp stabilizer "VFX" to help with that. I have been using the Warp in AE and motion tracking. I just don't know how to launch the multi point program in AE cloud.

I'm not sure I understand your problem. This page should help. It has links to tutorials that may answer your question if the page itself does not.

Warp stabilizer ? how do get it not to distort the footage

hi, almost any time i try to stabilize footage with the warp stabilizer, i end up with this trippy looking footage with objects bending and distorting.
is there any way to stabilize footage in premiere without this happening ? thanks

THANKS GUYS !
yep, JSS1138 i know i should have shot it with a tripod of course, but there are times when this option is not available to us, hence the existence of this plugin. right?
the tutorial was helpful, thanks but it did not clearly address the question of the warping footage. after a play around with the settings, though i find that using "position" instead of "subspace warp" seems to get me the result i want.
for those of you who know.... what is the trade off in increasing the smoothness? does it make the end result more blurry? thanks

Aerial videography, warp stabilize for pan only? Set exact scale?

I have a GoPro 3 Black, flying on a DJI Phantom Quadcopter with a 2-axis "gimbal", which does a great job of stabilizing pitch and roll, but not yaw.
I have two questions:
1) Can I set warp stabilizer to stabilize pan ONLY? Of course I do pan on purpose as well, so I'd like the panning stabilization to just smooth out the "wiggles", and not the purposeful pans. What is the best way to do that?
2) I am shooting in 16x9, 2.7k, at 30 fps, which is, ah, 2704x1440 pixels. I want the final product to be 16x9, 1080p, so I have a lot of pixels I can throw out in the process of stabilization, and still wind up with 1080p. Is there a setting in warp stabilizer to tell it to "use as much of the pixels over and above 1920x1080 for stabilization as you want, but not more"? (For this question, I am talking "normal" stabilization, pitch, roll, and yaw.)
Thanks...
Bill

I have a GoPro 3 Black, flying on a DJI Phantom Quadcopter with a 2-axis "gimbal", which does a great job of stabilizing pitch and roll, but not yaw.
I have two questions:
1) Can I set warp stabilizer to stabilize pan ONLY? Of course I do pan on purpose as well, so I'd like the panning stabilization to just smooth out the "wiggles", and not the purposeful pans. What is the best way to do that?
2) I am shooting in 16x9, 2.7k, at 30 fps, which is, ah, 2704x1440 pixels. I want the final product to be 16x9, 1080p, so I have a lot of pixels I can throw out in the process of stabilization, and still wind up with 1080p. Is there a setting in warp stabilizer to tell it to "use as much of the pixels over and above 1920x1080 for stabilization as you want, but not more"? (For this question, I am talking "normal" stabilization, pitch, roll, and yaw.)
Thanks...
Bill

Warp Stabilizer Analyze Data - where does it really save?

Hello,
I had cut 4 episode documentary series on a macPro with CS6. I had used the Sub Space Warp stabilizer feature on many of the clips. All clips had been stabilized and I saved the project on our server with the projects files, preview files and Auto save files.
I then got a computer upgrade to a new macPro with more RAM - graphic - and processing power. Yay! I have CS6 and CC installed on this.
I received the final design elements to insert into the series ( the L3 and titles and credits ) and went to go and export the project off the server from this new computer.
It seems that all of the clips that I have used the Sub Space Warp Stabilizer need to be re-analyzed again, as the exports had the orange banner across the clips stating that it is being analyzed.
My question is, does Premier have to reanalyze the clips again because I have a new computer and the Sub Space warp data doesn't save with the project files but instead locally on the machine that edited the project?
If so, can I get all the project data and cache to save with the project files?
When I started this project, as with any project, I direct all the save elements and caches to a specific drive location, so various computers can work with the edit, and for efficiency. I don't think that the Sub Space Warp analyze data gets off the local computer drive... Am I wrong?
Any comments are appreciated.
Thank for your help.

I see that now as well. Yes thank you for your reply there Snarky.
I wonder why my exports had the orange analyze banner across the clips with the Warp Stabilizer on it.
You figure with that data stored in the project file, it would just load up with the project,
and when the software says "All media Loaded" - that I wouldn't have to go back to each clip and get it to re-analyze for stabilization.
So time consuming.
I hope that is is an isolated incident.
This doesn't not seem to be the case, as I am not alone.
pass warp stabilizer between computers?
Reanalyzing Warp Stabilized Clips
Thank you Snarky McSnarkster

Warp stabilizer - change of directories

I'm having trouble with warp stabilizer and hope someone can help. I need to mention I'm brand new to using NLEs and am following along with tutorials for about 2 weeks to learn, so I am a very basic user.
I created my sequence by selecting multiple clip in my bin and dragging them onto the "New Item" icon at the bottom of the bin, allowing Premiere Pro to auto choose all the settings based on the footage by canceling when it popped up the window with all the many many choices about your footage format. The footage is just something I found online for the tutorial. I used "Warp Stabilizer" on a clip that was jumpy and it worked fine. I did not save, or I thought it autosaved but did not. I then installed a program called "Post Haste" which creates an organized series of folders for your projects. I did this because I am trying to learn good practices and being organized seems to be very important.
I then went to "Finder (I'm on a Mac) and moved all my files for this project into the folders that "Post Haste" created. When I restarted PPcs6 it asked me where all the files were and I went and found them all and it appeared initially that everything was working fine(or at least it looked the same), until I tried to do the Warp Stabilizer again on exactly the same clip I had before (as I mentioned I did not save). This time I got the message "Warp Stabilizer requires clip dimensions to match sequence" I should also say that my fps seems to be 24 which I'm not sure they were before. I should note that I'm in the US so I'd rather be working in NTSC and not PAL. So naturally I'm a bit frustrated and more over baffled as to what happened. I am assuming that moving the files to new folders somehow broke the settings. I did find an article on Premiere Pro Project Manager which initially makes me believe that I should have somehow set up settings before moving my files but the article was very brief and I did not really get that much from it.
So I guess my questions are: What happened? How do I fix it? Did I break/change my settings by moving my files? Did the clips change from my sequence settings to their individual clip settings? I 'm not sure what format the footage I am using was shot with/in, but since it is civil war reenactment footage I'd say it was NOT shot for PAL. So how did it move to 24fps? (isn't this PAL and should I not want 30fps?)
Is there a way for me to fix the entire timeline settings to all match the sequence or should I start again?
Any help including best practices going forward would be greatly appreciated.

If your timeline consists of different dimensions and the clip you want to stabilize does not match the sequence, just nest the clip and the add the Warp Stabilizer.

Warp Stabilizer 4K to HD - does PPcs6 interpolate first then downsize when using "stabilize, crop, autoscale?

I am using CS6. I have warp stabilized my 4K footage and want to output to HD at the best quality I can. I have two choices: I can either have warp stabilizer "stabilize, crop auto scale" then I simply render to HD or I can set "stabilize, crop" and then get rid of the black border (crop) using AME in export settings. So my question is: If I use option 1 does PP interpolate the footage and then "downsize" to HD thus reducing quality? Or Does PP make all the calculations "in one go" so the footage isn't actually interpolated then reduced? I hope I have explained this clearly - though I fear not :-) Thank you for any comments. Paul

I've been experimenting exactly the same. My conclusion is that stabilize, crop, auto scale does indeed crop the video first, then rescale back to the original frame resolution. So there is some loss of quality. I've been working on 4K video and warp stabilizing first (no crop, no auto scale), then cropping as a nested sequence to HD (with key-framing to follow the action). Depending on the amount of crop, what the video content is, and because you're starting with 4K footage to begin with, it's debatable as to whether the final HD rendered output is visually any different whatever method you choose. I guess you'll only find out by trial and error.
Steve

Warp stabilizer fail

After effects fails to load Warp-stabilizer when I start up the progamme. How can I fix it, or where can I locate the plugin/preset for this feature? I have CS6.
Thanks anyone!

Thanks for pointing that out so kindly, I am new here and and haven't seen any other topics, so don't know how things go around here.
When I start up, I get a pop up that says it cannot load warp stabilizer.There is not much else to add to the question.I thought it would be easy enough to ask where I can find the presets or plugins for Warp-stabilizer, or maybe what the exact name and location is of the effect, so that I an look it up and add it to my presets folder...
There is no extensive further explanation to do.

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.

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.

Warp Stabilizer Questions

Similar Messages

Maybe you are looking for