Lumetri Color Auto not working on clips with Warp Stabiliser

This issue appears to have been fixed in Premiere 25. Please create a new post if you are still facing this issue in the current version of Premiere following the guidelines listed in How do I write a bug report?

Thank you all for reporting this issue to us.

Amy

Oh, I do understand. Many years of experience with both. 

And I do completely sympathize. I simply hate drudgery tasks everywhere, and sadly, editing has a ton of them. All of which irritate me. Like this does.

So long ago I realized it is simply way past annoying to apply Warp and not finish the darn thing ... so when I apply Warp, I run it ... and then for all Warped clips, do a full render & replace to get new media created with Warp DONE.

Then Life goes on as normal, with a ton less drudge stuff. And I'm less likely to be thinking of throwing things at my monitor.

R Neil the problem here isn't the speed. 

It is not working. You have to disable and renable warp or change order. It's time consuming.

There are other bugs related to warp in combination with Lumetri (in particular with the new color management in PR, but we are not talking about this now).

At times, we users have to adapt to reality.

Which is that Warp is the heaviest computational load of the entire program, simply massive in its needs.

And Lumetri by its nature, is also demanding of resources. Both compute and apply major changes to every pixel in all respects.

For a user to treat Warp like it's just a glow effect or something, is well ... not going to end well. And I don't think it's reasonable to expect anything else.

You expect Neat video noise remover to run quickly with Lumetri and other stuff involved? I wouldn't think so. Warp can actually be a heavier computational load than Neat.

I don't see that the makers of Neat can get around that ... nor do I expect Adobe's devs to magically change computing loads.

Asking for increased capabilities, yes. Asking for the moon on a silver platter, maybe ... not this week.Though next week, who knows, right?

I do know from so many conversations that many users do not understand why stabilization in software is any more difficult than stabilization in-camera. Which is mostly a real-time physical action ... not a computing thing so much. Very, very different beasts they are.

Same problem. Adobe should fix this. Changing effects order or disabling warp before applying auto correction is time consuming on project with 100-200 clips. 

We are not talking about the fact that Lumetri is slow in combination with warp or viceversa (which is true by the way). Auto color-correction doesn't work at all with warp stabilizer. You press the button and nothing happens. It's a bug and it must be fixed. 

You can just disable wrap stabilizer (from effects control window), then auto correct the clip and then enable wrap stabilizer again. That is what I do.

This is the kind of thing that will vary between machines, media, other effects, the day of the week, if Aerosmith or the Stones are on the road somewhere, something/everything ...

Neil

When I get the stacking order correct it works for me too. Dont need to render and replace.

Just as a practical comment, I've found Warp a heavy enough effect, that coupled with any other heavy hardware effect, playback and results can be iffy. As ... Lumetri, speed or other size changes, video noise reduction, much audio track work.

So when I use Warp, I normally do it, get it 'right', then do a full Render & Replace operation on the timeline. Get a typically ProRes422 clip with the Warp baked in.

Then I can do other effects and it just ... works.

Neil

Seen this too.

Change stacking order; Lumetri then WS.