Participant

Question

Warp Stabilizer extremely slow

Forum|Forum|4 years ago
January 3, 2022
17 replies
20278 views

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)

Performance

A

Alberto Bedin

Known Participant

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

Legend

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.

Everyone's mileage always varies ...

M

Michael Grenadier

Legend

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...

D

D35066974rtw2

Participant

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

Z

Zsolt36388692pg28

Participant

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

M

Michael Grenadier

Legend

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...

A

Anonymous

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

Eric Robbins

Participating Frequently

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!

B

Boka2112

Inspiring

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.

J

jtjefferson

Known Participant

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

G

Gui Costa

Participating Frequently

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

M

Michael Grenadier

Legend

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...

L

Laezio5D1E

Inspiring

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!!

M

Michael Grenadier

Legend

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.

L

Laezio5D1E

Inspiring

XAVC-S

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

Jacob.5

Inspiring

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

Inspiring

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.

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded