Premiere Pro: Basic3D + Transform issue

[AndrewTheGreat]

Hi, Adobe. An issue that seems to exist for ages and that hasn't been fixed so far, perhaps, because no one can explain how it even happens. There's certainly a co-relation between these two standard effects mentioned in the title which makes them glitchy. No big projects, only a new empty project with the media cache flushed, no third party plugins, only these two.

1) I create a new sequence with the following settings:

2) I import the footage. Any will do. I downloaded mine from the Storyblocks. It has the following specs:

3) I drop it onto the timeline (no change of the sequence settings) and apply the two effects to the clip - Basic 3D and Transform.

Now (see the first video) - if the Transform effect is above the Basic 3d in the effect controls panel and the Basic 3d values are unchanged, the Transform effect works. Once you change the Tilt or any other Basic 3D value, the Transform's position and anchor point stop working. If you change the tilt gradually and it hits the 0 value, the video jumps up in the program monitor (see the 2nd video). If you place the transform effect BELOW the Basic 3D, the image immediately jumps into the position corresponding the applied position\anchor point value and everything works.

You can easily reproduce this issue. 

Premiere Pro 24.5, I7-14700K,RTX4080,64Ram, fast SSDs with a plenty of space, all the drivers and the OS are up to date. Nvidia Studio driver installed.

[Ann Bens]

Might not be an issue, but rather the way you need to stack these particular effects, the way they interact with each other.

If I stack 3D above Transform I do not see any glitching.

On a side note the clip is 30 fps while the sequence is 29.97. Might be something to look into.

[Kevin-Monahan]

Hi @AndrewTheGreat,

Please let us know if Ann's advice helped you or not.

Thanks,
Kevin

[AndrewTheGreat]

Hi, @Kevin-Monahan 

I checked Ann's assumption, and made a sequence out of the footage by dragging the footage onto the new sequence icon, and it didn't help - if the transform is above the basic 3d, the position and anchor point stop responding and there's the same jumping at the 0 value. I can admit it's because of this particular effects order, but Adobe needs to do something about it, maybe add some explanation in the Premiere Pro manual or something else because I see a lot of Premiere Pro users at a loss not understanding why this happens, why the transorm values stop responding at a certain moment, even here in the community. Or the transform effect should just be fixed somehow, because we get alotta glitches with it in other situations. For instance there's a Premiere Pro plugin called AtomX which bases its work on premiere's own effects, and it often has transitions that just don't work or glitch. I emailed the developer and they said it happens because of the instability of some Premiere pro effects, the Transform and Basic 3D were mentioned as the main culprits - their combination.

I myself use those two effects in every video I make and I always get some problems with them. 

[AndrewTheGreat]

@Ann Bens 

forgot to draw your attention to that - look closely how this glitch happens only if you change the Basic 3D value when the transform is above. So the stack order is doubtly the cause

[Ann Bens]

There are several effects one needs to put in a particular stacking order.

For instance, if you want to do a horizontal flip (HF) on a clip with Warp Stabilizer (WS) one needs to put the HF below the WS effect. Same goes for Corner Pin.

[AndrewTheGreat]

I know all that, the reason I started this topic is the glitching described. The effect doesn't work as it should

[Kevin-Monahan]

Hi Andrew,

Thanks for the comments. It's really a great idea to alter the stacking order of certain effects to achieve a compound effect, but you also might need to use nesting to achieve certain effects, as well. As a user, author, and teacher of Avid, AE, and FCP in the past, that is often the case. Can you check that out? I am hoping we can help you with this issue shortly.

Thanks,
Kevin