Why does warp stabliser stop while doing other operations?

[unknownsailor]

Hi,

One of the things that slows down my workflow is when I have a whole series of clips that require warp stabilisation (in this instance underwater slo-mo clips but that's irrelevant). Before composing I need to run warp stabiliser on up to 50 clips, each nested, and the restriction I'm finding is that I set warp stabiliser to work on one clip, which could take up to five minutes, but stops working when I move onto the next clip to edit. This is having a major impact on my time as I have to wait for the first clip to stablise before I can do anything else.

Interestingly this only happens on certain operations, mainly when opening windows on the next clip. It seems I can do basic operations like moving clips around, but if I try changing the speed of another clip, it stops the warp stabiliser on the previous clip.

I'm running 24.1.0 on a Windows 10 PC with AMD Ryzen 7 2700X and 32GB RAM. I don't see this being a processing issue but if anyone has a work-around I'd be very grateful because warp stabiliser has always done this.

TIA

[unknownsailor]

Bueller?

[R Neil Haugen]

Warp is the biggest resource-user of any effect I know of ... the analyzer time will take most of the available CPU capabilities to process. It's more intensive in demands than even Neat Video noise remover.

So applying that to a TON of clips, well ... it's going to such up most of your computer's capabilities while the CPU takes a few cores to churn away. Not a lot else can get done unfortunately.

That's just ... what is going to happen.

Doing really basic stuff, yea, the computer can sort of function. But changing time on a clip ain't 'basic', that also adds a fair load on things. Lumetri is another one. Multi-track stacked video all playing back, again too much load.

[unknownsailor]

I could understand it if the computer slowed down, but in this instance all I am trying to do is apply Warp Stabiliser on one clip and then add, say, a text layer to another clip (changing speed in my OP was a bad example. Pick any other operation like adding a text layer). I find it odd that Pr cannot multi-task these two operations, one of which is resource-light. After all, I CAN add warp stabiliser to many clips, all at the same time. Each operation slows down as the resources are shared across multiple operations, but my computer can handle it. What it can't handle is warp stabiliser on one clip and a simple operation on another clip that requires bringing up a window or adding a layer. Warp Stabiliser even gets disabled when I switch sequence.

[R Neil Haugen]

The devs could give an explanation why. As a user I can only comment really on what works. I know their color management and processing pretty well, but other users like Warren or Richard M Knight are much better at this sort of processing details.