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)

[captisvisuals]

We are having the same issues! And if you try ro export a video with even 15-20 clips with warp stabilizer...it can take HOURS. I downgraded back to version 22.0 and it cleared right up...only 8 minutes to render. Fix this Adobe please.

[Michael Grenadier]

Please tell us the properties of your sources.?

Not sure what you mean by "inversed."   But probably not a bad idea as a troubleshooting step to render out (export) the clip with the inversed applied and then bring that file in and then apply the warp stabilizer 

And any chance any of your sources are from a smartphone or screen recording?  If so, the problem may be caused by clips with a variable frame rate which can cause unpredictable and intermittent issues.  

[Shawsh5E2C]

has this been fixed, yet? I'm still having this issue as of mid July 2022, running v22.3.1

It would usually take seconds to a minute to anaylze now it's saying "approx 92 min" for a 350ish frames / few seconds slow-mo clip... We're on deadline as creators.... 😞

[Oshang]

Yeah I'm also still getting this issue in July 2022, it seems to work fine on the first clip after a fresh restart of premiere, with all subsequent clips tkaing forever. Interestingly if I watch the CPU usage when applying warp to the first clip jumps up to 70% or more, and for all the other ones afterwards the CPU is barely doing anything sitting below 10%, GPU not used at all. It's as if premiere just decides to throttle the analyzing for no reason.

[zachs30896143]

I'm having the same issue with Warp Stabilizer and Morph Cut, it just sits and sits and takes years to process the effects it seems. It worked fine in the previous version of Premiere Pro (22.4)

Here are my specs:

MacBook Pro (16-inch, 2021)

Chip: Apple M1 Max

Memory: 64 GB

Startup: Macintosh HD

macOS: Monterey (version 12.3)

Premiere Pro (version 22.5)

[Michael Grenadier]

probably a good idea to revert to the previous version...  shouldn't have any problem opening a project that you worked on in the new version with an earlier version of premierepro 22.

Also, you might try running the intel version and see if that improves this behavior..

[RdFalcon]

I am currently running 22.5.0 (build 62) on August 24th, 2022 and the Warp Stabilzer is now taking about 10 times longer than before.  I HATE the idea of downgrading my version, you have got to have a better solution by now.  This problem seems to come up every 6 months or so.  Is downgrading still the only answer you can provide?

[Oshang]

Yep agreed, i'm currently using after effects as a bandaid solution as reverting is not a feasible option for my current projects.

---Premiere is like a toxic relationship, it keeps abusing and gaslighting me, but every time I try to leave it seems to start working amazingly again and draws me back in 

[Gui Costa]

Same problem here, very slow to analyze Warp Stabilizer Effect. Did you find any solution?@zachs30896143 

My Specs:
MacBook Pro (16-inch, 2021)

Chip: Apple M1 Max

Memory: 32 GB

Startup: Macintosh HD

macOS: Ventura 13.0.1

Premiere 23.0.1

[Baffy19]

I have a modest question about the system requirements of your super machine. Tell me, having such an assembly, is there a noticeable increase in productivity and work with motion graphics?

How useful it is. I have a Core I9 9900K, 8 GB GPU 2070 SUPER, 32 GB RAM, M.2-3500

[monterrey648]

Same behavior. Left the new MBP working for 12 hours and it's on frame of 12 of 1187. Obviously nobody did regression testing of this feature at Adobe. Not going to bother posting my stats; it's not my system. Going to try to downgrade.  

[hagenm16374940]

Same behavior. 

win 10

Core i9 12900k

rtx 3080 10 gb

64 gb ram

1 tb nvme 

Sequenz with frame 13000 takes over 12 hours.

Any solution?

[jtjefferson]

Is it any better on the 2023 Version?

[jtjefferson]

it got a little better....

2023 145 minutes

2022 latest update i had 370 minutes on one clip.....

2022 1st version  65 minutes

2021 1st version 65 minutes

wonder how it is on 2020, but its not available anymore.

[Jared Post]

Warp Stabilizer has been fine for me until today. All of a sudden it's moving at a snail's pace taking 20 minutes to stabilize a 10 second 1920x1080 MP4 clip. It's also extremely slow on any type of footage I've tried at multiple resolutions. Reverted back to previous versions of Premiere and still got the same result. Literally nothing has changed on my system to explain this. 

M1 Mac Mini 2020
16GB RAM

1TB SSD

MacOS Ventura 13.0.1

[kasperw31847568]

I got the same issue (and the same mini) - it's driving me crazy. 

[Michael Grenadier]

I'm making a guess that the speed with which warpstabilizer works is dependant on the amount of detail in the frame and the amount of movement.  So is it possible the problematic shot has more detail and/or movement?

[Jacob.5]

I've had the same problem for the last several months on the 3-4 most recent versions of premiere. Took 30+ minutes to analyze a 19 second clip, and caused premiere to crash. On my old 2013 macbook with the same footage something like this used to take 3-5 minutes at most. So far no solution in sight...

Current specs:
MacOS Monterey 12.6
M1 Max

32 gb memory

[Jacob.5]

It seems to be the worst with nested clips in particular, regular un-nested clips seem to be working normally, aside from the occasional crash.

[Laezio5D1E]

August 2023, MacOsVentura 13.5

Macbook pro M2 Max 16inch 

Premiere pro 23.6.0 (build 65)

96gb Ram

4tb ssd

taking 5 minutes for around 15 seconds of video (4k 10bit SLOG3)

bummer!!

[Michael Grenadier]

what codec is the camera original.  If it's an mpeg variant like mxf or. h264, that may be part of the problem.  Try converting to the appropriate prores flavor in which each frame is complete.   

[Laezio5D1E]

XAVC-S 

Whys is it an issue for premiere? and what should I convert it to in order to have a faster warp processing?

[Michael Grenadier]

if you want all the grimy details: https://en.wikipedia.org/wiki/XAVC

but xavc is an mpeg format...  Not every frame is discreet.  I-Frames contain all the data, but only occur at a regular interval.  In many cases, that's 15 frames, so the first frame and the 15th frame have all the information and the frames inbetween only have the differences in the frames.  Not sure I understand all the nuances, but mpeg formats are usually much smaller files, but require much greater processing power to play.  In order for premiere to run the warpstabilizer effect, it's got to "decompress all the frames" which takes time...  By transcoding to a format like prores, in which every frame is complete, BEFORE you start editing, you're only spending that time once.  Perhaps someone else with more knowledge of the ins and outs can explain further if you still have questions...   

[Richard23394131sqn1]

Not all XAVC is Long GOP. There are flavors of XAVC that are All-I.  I still think it can slow things down though.