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.
Please hurry up and fix the speed and resolution compatibility! If nothing else gets fixed about this filter, please fix this. I'm really getting tired of having to nest so many clips all the time just to stabilize them. Please hurry up and fix this!
Pierre Louis Beranek commented
YES!!! +100 for this one. And smoothness KEYFRAMES PLEASE +1
Please update this Adobe. I'm sure you can figure out a way for the software to "virtually" Nest the clip and perform the stabilization without making us do it.
Ben Myrick commented
Patrick, here's my answer to your questions specifically:
Often times I'm working with 4k footage that was shot at 48p or higher frame rates, which provides a great deal of flexibility in post when the final output is generally still 1080 @ 23.98. So, stabilizing any of these high-res, high-speed files requires nesting. This is so common for me now, that one of the first bins I make when starting a new project is "Nested Sequences" because I know I'm going to have to nest a bunch of clips for this. But that's all I'm doing, just nesting so I can use the filter.
I don't tweak Premiere's Warp Stabilizer much other than auditioning 'Subspace Warp' vs 'Position/Scale/Rotation'. If I need to tweak it further, I usually send the clip to After Effects where I can delete erroneous tracking points. But, doing so adds a lot of extra steps. I know there's another voting thread on this forum to replace the Premiere Warp Stabilizer with AE's Warp Stabilizer, which would be ideal because of the tracking point manipulation.
I hope my experience here is insightful for future development.
Something else I'd like to see is the ability to keyframe the "Smoothness" setting, so that if I want one part of the shot to be stabilized, but another part of the shot to be left alone, then I can keyframe the smoothness to go from 50% down to 0% during the shot.
I sometimes have to do this if one part of the shot desperately needs to be stabilized, but another part of the shot either doesn't stabilize well or doesn't need it.
Currently, the only way to do anything even close to that is to splice the clip into two, and then put the stabilizer on the one I want... then do a really tricky and time-consuming thing were I have to zoom into the other clip and carefully match it into the right position so it doesn't jump at the splice point. Obviously, not a great way to do it, but there's no other way to apply the stabilization to one part of a shot without affecting another part. KEYFRAMES, PLEASE!
David-Ali Ungan commented
My wishlist for a new Warp Stabilizer revision:
1) No need for nesting anymore
2) Speed changes on same clips possible
3) global mute/analyse button for the blue banner warnings
Darren Manden commented
Yup, pretty much. I don't think using it in the way we've described is particularly unique either.
Oh well, hopefully when the constant crashes are fixed, and the other ridiculous bugs (hello audio effect reset) are taken care of, WS can be addressed.
That's an issue I can't qrap my head around how Adobe forces you to nest the clip before applying warp stabilization.
Given that many of us have 4k footage in a 1080 timeline, one would assume that this is the perfect basis for applying warp stabilizer because it can take the additional non-visible image to auto-crop without any loss of quality when zooming in.
Instead it PP forces you to take the lossy route.
Darren Manden commented
Currently 99% of our projects are output at 1080p, but we're shooting at anything up to 4.6k.
The footage itself will vary from project to project. Sometimes it's all handheld, and we're stabilising to make things a bit smoother. Other times, we might be on tracks, or steadicam, and are just wanting to get that extra bit of stabilisation.
The tweaking within the plugin will vary significantly depending on the shot. Sometimes the default settings are great, but more often than not we're doing anything from minor to major adjustments.
But the big point is that having to nest the "non-sequence res" shots before stabilising is a pain, and frustrating when you're making adjustments to the edit.
This happens to me if I have a clip that I want to appear in slow motion (filmed natively in 60fps) when my timeline is 24fps, I have to nest it to be able to apply warp stabilise.
I know some will suggest confirming, but sometimes half the clip you want to play at normal speed then slow down half way through so either way you are hit with this scenario.
Kevin Christopher commented
We shoot a lot of Phantom 4K and RED 8K specialty shots so they are shot purposely wide for this reason. We get everything right for editorial then do the stabilization work. The settings have to be tweaked to death. I currently use 4 stabilization methods and plugins to do my work. Animated Smoothness, and transform and scale would also do wonders.
Andreas Toth commented
I've never understood why the effect cannot just do that, i.e., perform a hidden pre-compose/sub-sequence.
Yeah this is quite annoying. It occurs for me because I've scaled a shot and then I want to stabilize it. I often mess with how much stabilizing is used to make it look more natural.
Im guessing the plugin could perform some sort of hidden precompose.
Also: If new frames need analyzing, don't analyze again from scratch!
Currently if a clip is 10,000 frames long, and I extend its out point by 1 frame... WS will require analyzing all the frames again!
UHD footage in a 1080p timeline.
Many times I change the Method and Borders/Framing (when I'm punching in myself in Motion/Scale). The rest is useful but less often.
Would love to see to use masks - either to give the plugin a region of interest, or exclusion zones. It appears that it would help tricky situations more than any "Detailed Analysis". (But not if that would delay implementation by a year :)
My experience has been that Warp Stabilizer either does a great job, or does almost nothing.
And yes, definitely address projects bloating up from WS metadata.
Same here. 4K footage on 1080 timeline is a normal workflow today.
At the very least, auto nesting and auto nest naming of the nest to be NEST-ClipName.
Yes, it's a drastic change. How about adding. feature to 'Nesting', namely that of electing to use the footage settings or Timeline settings. that would solve the issue, right.?!
Daniel Hoover commented
Yes, it'd be great to select and delete tracking points to improve the track, as you can in After Effects. That'd be an amazing addition.
it’s funny how in fcp7, a now obsolete editing program, you were able to “smoothcam” any clip of any resolution on any timeline at any time at any speed with better results. warp stabilizer is much more inefficient not only at stabilizing but the junk of sometimes having to double or triple nest a clip to get the same result i used to be able to drag and drop.
I frequently drop UDH footage in a 1080 timeline.
Nesting can be a pain when you have a large amount of clips.
Also WS tends to bloat the project.
Takes a long time to open or save the project.