Warp Stabilizer making PP file huge

[Scintilla_UK]

I have a lot of time-lapse footage that is very shaky due to the exposure of the camera and altitude of the camera. I have tried stabilising the footage in Premiere Pro using Warp Stabilizer (No Motion) - but this results in the file becoming massive and will not output using my Mac Studio (M1 Ultra).

Is there an alternative to Warp Stabilizer that does not negatively impact on the file size?

Thanks

[R Neil Haugen]

I would  recommend that once you've analyzed a clip and it "works ok", that you do a full render & replace on the timeline to create a new full file with the Warp baked in. 

Simplifies all further work in that project.

Neil

[Scintilla_UK]

Thanks for this, will give this a go - I can see your logic.

[Remote Index · Accepted solution]

Hello Scintilla_UK,

(Edit: I presume when you say that it makes the file massive that you are referring to the size of the Premiere Pro project file.)

This is a very negative side effect of the way Adobe have designed Warp Stabilizer in Premiere Pro.

I always recommend that users do not use Warp Stabilizer natively in Premiere Pro for this reason - particularly if you are working on long term projects.

One alternative is to use Dynamic Link and use the Warp Stabilizer in After After Effects (right click and "Replace with After Effects Composition"). This may seem slightly daunting, but it means simply applying one effect (warp stabilizer) to a composition in After Effects that is auto-created by the above right-click action.

This, comes with some caveats:

- After Effects needs to be installed

- You will be creating After Effects projects which are associated / necessary for the Premiere Pro project

Also, I recommend you first duplicate any clip in a timeline you wish to treat this way (Option-drag to another track) and keep this duplicate clip in the track (disabled) in case you need to refer back to original media at any point. Dynamic links and After Effects clips in Premiere Pro do not track this information (in spite of its obvious use).

Finally, on the plus side, the After Effects Warp stabilizer does offer slightly more control / nuance for stabilization (though it's often not great, it's an improvement over the Premiere Pro version).

R.

[R Neil Haugen]

I would totally agree that Ae's Warp is better than the one in Pr. Like many effects, really.

So for absolutely the best Q results, the Ae one would nearly always be the better choice.

But even then, for most purposes, I recommend for any Ae dynamic linked comps ... that as soon as you have the comp "finished", you export a full clip of it from Ae. Then use that clip to replace the comp on the Pr timeline.

Same reasons ... easier playback, fewer headaches down the road.

Neil

[Remote Index]

Neil,

While your suggestion does make for easier playback, it does not account for future access to the original media.

One such need would be if changes are required (ie. parameter changes to the effect, or adjustments to in and out points).

Another such need would be for any offline/online workflows where proxy media needs to be replaced with original media. (Remember, Premiere Pro in-app proxies are only one type of proxy workflow).

For these scenarios, the original clip duplicated in the timeline and a dynamic link to an after effects project are useful.

R.

[R Neil Haugen]

True. There are always things that can change, and probably will. Being able to flexibly roll with the changes is such a massive requirement, isn't it?

But that doesn't change my recommendations at all. If the needs change, you pop back into the Ae comp, make your changes. You can still use a DL for that.

Check the work on the comp in the Pr sequence, or simply in the Ae comp. Then, again ... when done, export the file to use in replace of the previous clip or the newly modified Ae comp.

Been there done that.

Neil

[MyerPj]

I agree the AE method is the best way to go. I like exporting out a 'finished' clip and using that in the place of the original. It keeps things clean and you'll get the best performance. 

There was an Enhancement Request at some point asking the the Warp info be saved outside the project. I believe Adobe replied, but it was vague, like 'we're taking a look at this'.