Warp Stabilizer extremely slow

[rhaul2]

premiero pro 22.1.2 its taking 47 min analizing 288 frames with warp stabilizer. I updated to the last version and its taking the same time, i created a sequence apart (nest) its taking the same time, i have no plugins installed in my premiere pro. The vid its inversed but its taking a ridiculous amount of time to analize, im working with warp stabilizer in inversed vids from long time and never took to much time until now. i changed my workstation and the adobe premiere version in the same time (i had an core i7 in the past) so i dont know if the problem its my new config or adobe its not yet optimized for this new processors or any other problem, can someone help me please.

win 10

Core i9 12900k

rtx 3090 24 gb

64 gb ram ddr5 (only premiere opened)

1 tb nvme WD black (a lot of empty space)

[Gui Costa]

what i find out, if there is a lumetri color effect i remove, after that i apply warp stabilizer and it render faster.

[Michael Grenadier]

Thanks Gui.  Makes sense to apply the color effect after you've applied the warpstabilizer effect.  You might try "render and replace" after applying the warp stabilizer and then apply the lumetri effect...

[Laezio5D1E]

In my case, if I apply lumetri color prior to warp, it won't even start anayzing unless I  switch the order on the effects panel. 

But great observation, will make sure that warp is the first edit I do on my clips.

[carlr82881030]

This is the answer!! Well done, sir.

[Antoine24629964mvg8]

wow, went from 22 minutes of analyzing to like 10 seconds just by turning lumetri off, and unnesting the clip.. 

Ridiculous ...

[miguelp80362861]

This was an immediate solution to the problem. I toggled color and then applied warp stabilizer. 

[jtjefferson]

After 21 years with Premiere Pro (yes im already old) i finally switched mid Project to davinci cause of the Problems with Warp stabilyzer, poor codec playback Support (xavc), Logitech Errors, self deleting Team Projects, Premiere deleting files from my hard Drives and hours of helping Support to recreate Bugs. I was even an early Beta tester when it wasnt Public. There are still Problems in this Forum to which i was writing to from 9 years ago, that are still Not solved.

I'm so done with this programm.

Stabilyzation is so damn fast in davinci, as is Playback with so many Codecs, which would never ever Play in real time and full res. Audio Timecode: No Problem

Batch merging audio and Video with Timecode: no problem

All should take a deep breath and Dive into davinci.

Im Happy that i'll never Return to this Forum again.

Goodbye

[Boka2112]

I find oddly that checking fast analysis and unchecking detailed analysis produces faster and better results.  I do agree Premiere cares little about fixing this plugin and it shows in its results.

[Eric Robbins]

I'm glad I read to the end of this thread to find the solution! I now understand that if you have Lumetri turned on "above" Warp Stabilizer, it exponentially increases analysis time. I had Lumetri on a clip that was embedded in a Multi-Cam sequence and it was taking 5everrr. Temporarily disabled, and now it's blazing fast again. This is also a good case for stabilization prior to color grading for my workflow. I'll take that into account next time. Grateful for the insight on this issue!

[Guest]

use warp stabilization on a subsequence; then color, layer, and other effects on top sequences

[Zsolt36388692pg28]

so no fix yet, huh? 🙂 still having this issue... new verison after new version after new version...

[Michael Grenadier]

Never easy to troubleshoot premiere problems from a distance so please tell us your system specs: OS version, Premiere version, amount of RAM, Hardware specs including graphics card and if you have any 3rd party plugins installed for Premiere... Also, sequence settings and clip properties can also help. Although you can throw almost any format into premiere, some formats can be problematic, particularly on an underpowered system. 

And as I said earlier in this thread, mpeg formats are gonna be difficult with warp stabilizer.  Suggest you transcode to an all iframe format like the appropriate flavor of Prores...  

[D35066974rtw2]

Go to Prefrences > Media Cache > Delete Media Cache Files. Then reboot premire and re-apply the warp stabilizer. 

[D35066974rtw2]

Found a solution. Go to Prefrences > Media Cache > Delete Media Cache Files. Then reboot premire and re-apply the warp stabilizer. 

[Alberto Bedin]

Removing Lumetri Color AND ALSO removing auto-log-footage color correction on the "modify -> color" properties of the file fixed the problem. Adobe must fix this bug. 

[R Neil Haugen]

Working smarter is also always an option.

Understanding processing considerations and order of processing things is crucial at times. Such as that Warp is the heaviest CPU demand load in the entire app, typically even more so than Neat video noise remover.

Using multiple heavy-processing effects on one clip ... is always at least potentially problematic. Trying to avoid that can save a ton of groping through other issues.

So ... for practical reasons ... it is wise to apply Warp, analyze, and when you get a 'good' result, immediately do a full render & replace to a good DI format/codec like ProRes422 or better.

Now further work on that clip on that sequence, will not involve the strain of Warp. And if you need to redo that clip, you can quickly "restore unrendered".

It's like working with Ae dynamic link comps. I know of situations where it's been a month since they last touched the comp in Ae, it's "cooked". But they still leave the comp on the sequence in Premiere. Which is asking for trouble with a capital T.

At the time you have completed the comp, and it plays in Premiere as needed, export a clip of the comp from Ae, and replace the comp with an actual clip. Safe working is easier on the nerves, at least for me.

[Michael Grenadier]

Great post as usual Neil, but...  I strongly recommend that you leave the AE comp in the premiere timeline, underneath the actual clip in case you need to make changes (hard to imagine?) at least that's the way I work...     

[R Neil Haugen]

We're all different, Michael! 

[Alberto Bedin]

I'm sorry Neigel, I totally disagree with you.

Warp stabilizer is REALLY FAST in Premiere and in all other NLE softwares. The bug is that in Premiere if you apply Lumetri color before warp stabilizer it brokes. It is just frozen. It takes 30-40 min to analyze a clip where it previously take 10 seconds. 

Saying "Understanding processing considerations and order of processing things is crucial at times" is pointless in this situation. On previous versions of Premiere I could apply warp and color in any order. The same in other NLE like Davinci Resolve. 

I haven't time to render and replace clips. Sometimes we just need to apply color to log footage before warp stabilizer (for example to get a preview on log footage).

This is a bug and Adobe should fix it. I'll report it.

[R Neil Haugen]

It's fascinating to me how different we all work, and how differently things work for different users. Such as ... I've never been able to get decent playback with Lumetri and Warp applied to a clip. I'm running a 24 core Ryzen, 128GB of RAM, and a 2080Ti.

And Lumetri applied ahead of Warp ... seems to really bog processing down. Not quite as bad as having both Neat de-noiser and Warp together, but close.

Putting Lumetri post Warp keeps Warp from bogging down on my rigs, but it's enough of a hassle that for practical reasons I just nearly always apply Warp and do a render/replace to get that OUT of my timeline. Saves hassles and problems period.

While it would be nice if such things weren't an issue in some Ideal World ... as a practical guy, I just do what works as is. And help request better builds, of course.

But then, I've only very rarely needed to go back and change a clip with Warp applied. Again, everyone's mileage always varies.

[MyerPj]

I typically do the warp on it's own, as Neil says, often times in AE, and do keep the link around per Michael's tip.

[R Neil Haugen]

Yea, some clips I've just not wanted to mess with Pr's Warp. Redo, redo, it's still not right, over to Ae, bang ... done. Export a replacement clip from Ae, drop it in to replace the original clip, and get on with Life.