Effect bug premiere pro

[VendelaFr]

Hi, I've been editing this video for a while and I ran into an issue while switching to GPU acceleration.

(GPU acceleration OFF)

(GPU acceleration ON)

So far I haven't been able to find any other solution than redoing all the effects.

[Ann Bens]

All I can think off is switch order of effects.

[Andy 1968]

You are saying it cropped the video? 

[Baffy19]

How could GPU acceleration affect the Crop of your frame?

[R Neil Haugen]

I think I'm with Ann on this one ... switch the order or apply the crop, nest, then apply movement.

Neil

[Baffy19]

Neil, the user attached screenshots marked: 1) the GPU accelerator is turned off and 2) the GPU is turned on. What's that got to do with it??? The question is, how does enabling GPU acceleration affect frame cropping?

[R Neil Haugen]

Because the math and processing order can actually change between CPU and GPU encoding. Weird as it may seem to us, it does matter.

Hence ... the use of nesting the first part of the work done on a clip to clearly set the next steps correctly.

And is also useful when doing multiple heavy effects on a clip, say Warp and Lumetri. Do Warp, nest, do Lumetri. Or maybe even do Warp, a complete render & replace, then do Lumetri.

Neil

[Baffy19]

I understand if a user asked me what I did wrong with the applied effects, that he had a cropped frame on the right. BUT, THE ORDER OF EFFECTS IN HIS PROJECT DID NOT CHANGE, PAY ATTENTION, NEIL. Here he clearly and clearly asks and marks why he has such a reaction to turning on/off the GPU accelerator. That's the question. If he hadn't underlined and marked it, then the answer would have been obvious and correct in Ann. But, here he asks about something else. Look at the pictures and compare. What is the difference?

[R Neil Haugen]

There are behaviors that none of us can define the reason for, that simply (to us users) ... exist. Sometimes I can get an engineer to explain and get it sorted. Sometimes ... it's just, what is, is.

Processing order in video post is always something to pay attention to, no matter whether it's Premiere, Ae, Resolve, Baselight, Avid, whatever. All of those apps have what seems to the user bizarre changes that occur based on whether X is before or after Y. So we just have to somehow learn and apply those.

No, I've got no answer if what you want is the why. But if you just want to get the work out the door, the practical answer is what is possible. And yea, I get frustrated with that from time to time also.

Neil

[Andy 1968]

There should be no difference between using the CPU and GPU but unfortunately there is. The Mercury Playback Engine needs to be scrapped ASAP and replaced by the Saturn Six system. 

[Peru Bob]

BUT, THE ORDER OF EFFECTS IN HIS PROJECT DID NOT CHANGE,

As Neil stated, the fact is that CPU and GPU encoding are different and may yield different results with the same order of effects.

Changing the order of effects might fix the misbehavior in the clip with GPU encoding turned on.

[VendelaFr]

So a little bit of an update! I manage to figure out what made this happen. There reason the effect moves is because of anchor points. Nesting the clip you're trying to edit before applying effects will fix the problem.
At least that worked for me! Also this problem only happend when using the transform effect with motion blur.