Warp Stabilizer needs to be able to automatically adjust to different resolution footage inside of the same timeline. I waste an obscene amount of time manually nesting footage, going into that comp, resizing the nested sequence to match the clip, and then applying warp stabilizer, and then going back to my original timeline, and then scaling the nested sequence to this sequence size. Its a massive hassle and waste of time. Build a feature that allows it to do all of that automatically in the effect panel.
We actually fixed this issue back in the 13.1.3 release (July 2019). Warp Stabilizer no longer requires the footage to match the sequence resolution. This allows for common workflows like shooting in 4K and mastering in 1080 so you have room to reframe the shot or punch in for a closeup and medium shot from the same camera angle. Warp stabilizer will work in these situations no longer requiring nesting. It is still a requirement that the pixel aspect ratio must match but this is less of an issue these days, where more often than not you are dealing with square pixels. If you haven’t updated since the spring of 2019, I recommend you update to the latest version. As always, thanks for your comments.
Also, please add an option to change default "Smoothness" percentage. I find 50% - too much for the most cases.
And it will be nice to have queued, one after one stabilization when you apply "warp" to multiple clips simultaneously, because now it calculates it all at once and uses too much RAM and CPU
[Deleted User] commented
I usually work with 4,6K or UHD prores footage inside a 1080p timeline.
I do a fair amount of tweaking the warp stabilizer settings.
Most of the time I either use the "no motion" option or a very low amount of smoothness.
The "synthesize-edges" option has literally never resulted in anything useful in my personal experience.
If warp stabilizer doesn't work I usually switch to mocha pro.
One thing I'd like to add: In after effects you can actually display and delete warp stabilizer tracking points. This can very often save a otherwise impossible stabilisation. So if you do decide to overhaul the entire effect, this would be a very helpful feature to add inside permiere.
hope this helps;)
Most of the files we work with are a mix of ProRes and AVCHD anywhere from 1080 to 5k. We always edit in a native 1080 timeline, and use "Scale to Frame Size" to match everything. Most of the time, Warp Stabilizer does a fairly decent job with the default settings, but most of the changes we do are to the type of stabilization, mostly switching to perspective, as well as smoothness amount. I know that I can fix it by nesting the clip, so there must be a fix internally that just automatically does that as a step, even if it pulled up a dialogue that asked if you want it to handle it in the native resolution or scaled, and then automatically nested as needed.
There are 3 problems with Warp stabilizer.
1. You have to nest clip if you want to applay effect on clip with diffrent resolution than timeline or want to use time-remap, time revers on it.
2. It is painfully slow.
3. Every time you use it project file size increase by 2mb. If you use it offen, you will end up with over 100mb files that saves painfully slow.
Mercali plugin don't give you as good result as warp but it doesn't have any of the problem as I listed above.
I hope you fix it because right now I use warp only if I really have to.
Daniel Hoover commented
I agree with the comments here, we often use Warp Stabilizer to stabilize footage shot in different resolutions than the timeline.
We also have to nest when the clip has been time-reversed or time-remapped. Between these two items, we often get a lot of nested clips in the sequence, making things messy and more difficult to work with.
Also, once the clip is nested, you lose the ability to adjust the heads/tails of the footage (aka the nest) in the top level sequence, making cross dissolves/transitions impossible between nested sequences unless each clip in each nest is adjusted to pull out the handles on each side. But then this ruins the footage shown in the edit, so the nest has to be "slipped" back into place, and then place the transition....
It's time-consuming and not user-friendly and would be immediately solved if Warp Stabilizer was resolution and time-remapping/reversed independent.
Micah Haun commented
I often use 4K/UHD footage in a 1080 sequence. All I need is for warp stabilizer to just work with the footage and not care about the timeline frame size.
That's how it already works in After Effects.
Ryan Plummer commented
We work with mostly RED footage at 5K, 5120x2700. Occasionally we need to pull in older assets or footage from older cameras that are not close to the resolution, and our output is 1080p. We normally work in a 1080p timeline. Sometimes we get to the end of the edit and forget that the 5K shots we have used, scaled, and positioned are not able to use WS. We then have to nest, rescale, and reposition...each. clip.
Niko Pueringer commented
I use warp stabiliizer on every project we release on Corridor. We shoot on RED in 8k, but master in UHD, so if our timeline is UHD, then every time I want to apply Warp Stabilizer I have to nest the clip beforehand.
If every single time you apply the effect you have to nest beforehand, it leads to a very messy project.
I also use nearly all the settings in the filter over the course of a project. It's one of the most useful and functional features of Premiere. Best stabilization solution in my opinion, and I would love to see it get even better.
Definitely agreed. Warp Stabilizer should handle resolution mismatches transparently.
The *proper* workflow is to use the tool with supersampled clips (clips whose resolution is higher than the timeline's), so having no support for it (for over 3 years) is madness.
Brian Davison commented
Would also be nice if it wouldn't 'stall out' if the clip you are stablizing is covered by another clip at it's head.