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.
Nick Seitz commented
I will add to this- I'm often working with 4k footage in a 1080p timeline. It seems like this would be a huge plus to ws in some instances- having more information outside of the frame and moving the surrounding footage relative to the frame rather than having to crop into the original footage.
paul wedel commented
Also please fix this new bug introduced in v13, which has nullified one of my favourite workflows from v12 and earlier:
I have a clip where I apply a mask to omit certain tracking points for Warp Stabilizer.
I nest the clip.
I apply the Warp Stabilizer effect.
PP freezes/crashes/spinning ball of doom.
This workflow worked fine in CC2018 and earlier, but not at all in v13, including the latest 13.1.5
Finally got to play with CC2019, happy to see the resolution mismatch at least got addressed. One more thing to thumb-up is that the existence of a band would bring up a warning for export.
1. Speed changes + warp are less of an issue for me so I'm less annoyed with having to nest those, but of course plenty here need it. The "philosophical" issue here is, do you process a speed change and then apply Warp (losing frame data), or Warp, then speed-change a stable clip?
From a time and dataset size perspective, I vote for speed-then-Warp (it's so slow already..). From an image quality perspective... I'm not sure.
2. Darren: YES I'm also seeing the frame-size bug - on Mac. It jumps to a small size upon playback, jumps back to correct scaling upon pause. One workaround is to modify the scaling (e.g. to 50.1%). Personally I don't like Warp to scale for me, so I use it in Stabilize+crop mode and then scale the clip myself in the transform controls.. which also happens to work around this bug.
Also, try setting playback quality to Full and see if it helps.
3. Last but not least... I've seen Warp-on-scaled-clips work in Premiere, and not work in Media Encoder 2019 (13.1 Build173)! Media Encoder brings up the same old "mismatched resolution, please nest" warning as if I'm using an older version... and I'm not! What gives? Anybody else seen this?
Darren Manden commented
@Jon Haile - Oh man, that sucks. We haven't spotted it on the Macs here, but it's definitely throwing a wrecking ball into the Windows system, so I was kind of wondering if it was just limited to Windows. I guess not.
If I find any other workaround, I'll post it here.
Jon Haile commented
@Darren Manden Yes! I'm having that exact issue on our Mac. Haven't been able to find a fix other than going back to the nesting routine
Darren Manden commented
Is anybody else running into the issue where, when you apply Warp Stabiliser to a clip that is a different resolution to the sequence, and then hit play, the clip shrinks down, revealing any clips on the timeline below the WS clip, but as soon as you stop playback, it returns to normal size?
This is on our Windows systems. Essentially we still need to nest, or else WS is broken.
So the recent update added compatibility with different resolutions, but the big one for me is still the speed incompatibility. Anytime I change the speed of a clip, I have to nest to use the stabilizer. PLEASE add variable speed compatibility as well, ASAP! This is more important for me than the resolution issue was.
It is really great that you fixed this issue.
However there are many more things to improve upon in warp stabilizer. I listed them in comments before:
There are 3 problems with Warp stabilizer.
1. You have to nest clip if you 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 1-2mb. If you use it offen, you will end up with over 100mb files that saves painfully slow. Maybe store analisys data in other file
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 that if you fixed this issue you are already working on other too.
Woah! This may finally be a release worth upgrading to, from 12.1.1.
So I guess we can close this one?
trent happel commented
FYI, Premiere Pro 13.1.3 now allows clips with different frame sizes in Timeline Sequences to work for Warp Stabilizer without the need to nest (as long as the Pixel Aspect Ratio matches).
Added support for scaled clips with matching aspect ratios for Warp Stabilizer
Andrew Geraci commented
8k footage to 4k or 4k to 1080p - this should be an automatic macro function so we don't have to create nests.
Felix Pitscheneder commented
It would be great to be able to apply the warp stabilizer similar to lumetri like a master effect
Anthony Monk commented
It would be nice if we could apply the effects of a warp analyzer to several clips, I'm working with several layers of the same clip with various effects and masking on top of each other anw would like to be apply to apply the same stabilisation to all of them.
Jonathan Finley commented
I straight up avoid using warp stabilizer in premiere because of this issue alone.
4K Footage in 1080p, it really is a very frustrating workflow.
Emilio Luis Roman commented
any update on this?
4K footage in a 1080 timeline.
Our clients always ask for cutdowns of 16:9 promos. Going to 4:5 or 9:16 vertical formats.
Agree with OP, it is a hassle to always have to nest clips.
Etienne Lacroix commented
4 k on a HD timeline
Ivan Ivanov commented
The majority of my projects have slow-mo b-roll. Needless to say that the warp stabilizer is most needed on b-roll which always has a speed adjustment. When I'm done with a project, my whole sequence is basically a bunch of nests. It becomes impossible to work with it.