Fix the TRACK MATTE effect with a "Motion Settings Affect Matte" Checkbox!

[PierreLouisBeranek]

The Track Matte effect in Premiere Pro almost never works the way we editors need it to, and it's high time this essential effect gets fixed!

When creating a Track Matte, changing the Motion parameters of the clip the effect is applied to also changes the resulting matte. For example, if I zoom my clip to 120%, the clip zooms 120% but so does the matte. This makes it impossible to move a clip within a matte's 'window' without nesting.

The current way to get around this is to nest the clip, apply the Track Matte effect to the nest rather than the clip itself, and then edit the clip's Motion settings/keyframes within the nest. Unfortunately this is a HORRIBLE workflow, since it forces editors to edit their clip's motion settings and keyframes out of context of the master sequence. It also involves the extra steps of nesting.

After Effects handles masking the way it should work: making any changes to a clip doesn't affect the resulting matted effect. This is the way it should also work in Premiere Pro!!!!!!!!!!

A simple way to fix this problem, that would serve the needs of everyone, would be to simply add a "Motion Settings Affect Matte" checkbox to the Track Matte effect, and leave it unchecked by default. This way, the 0.0001% of users who want track mattes to work the way they currently work in Premiere could continue with the current workflow, just by clicking the checkbox, and the 99.9999% of users who want PP's matting to work the way it does in AE could finally have AE's far superior matting workflow inside Premiere!

The AE team gets it. Why can't the PP team understand how track matting should work???

Adobe, Track Matte is one of those effects that pro editors use all of the time! We would really, truly, greatly appreciate it if you could finally make time in your busy schedule to fix this essential tool before resuming attention to other features that are used by far fewer people.

Thank you!!!!!

[Pierre Louis B.]

If you look down the comments thread Robert, you'll see a couple of other workarounds I came up with that might help. The comment starts with the text "WORKAROUND TIPS!"

Adobe reps might barely ever participate on uservoice and for the most part simply ignore our requests, but that doesn't stop us users from helping each other with our workarounds in the comments section! 😉

[Robert Voogt]

Yes, I tried that first, but it didn't work for me. The mask stayed relative to the layer it was applied on.

[Pierre Louis B.]

I pointed out that work around in my original post Robert, but it's a horrible option since any Motion adjustments made to the nested clip are made out of context of all other visual elements in the main timeline. The bottom line is that Adobe should make their software FUNCTIONAL.

[AlfredRehbach]

This issue is enfuriating 😄

[michelle_7929]

I can't believe it hasn't been fixed yet. I assume it hasn't since you are posting. Despite all these post being dated Jan 2023, I posted back in 2020 and this discussion was at least a couple of years old back then. 

[Pierre Louis B.]

It seems the Pr team doesn't have time to address the real issues, such as this one, because they're too busy screwing around with complete non-issues and things that absolutely no one is asking for, such as rounded corners in Timeline clips (currently in Beta).  Sure, the team does improve Pr over time, but their priorities are almost always so out of whack, it's sad.  The Pr managers who set the schedule of problems to fix and new features to add should be ashamed of themselves, since every time they introduce something no one was asking for, while ignoring very real problems such as this one, they reveal themselves to be the ego-centrical, self-centered, self-serving, out of touch with reality people they are.

[R Neil Haugen]

I do advise just a wee bit of humility in such posts ... being as every freaking one of us does everything differently while editing. Seriously. I'm not a huge fan of some things either, for the record. 

Remeber: they have several million daily users, right? And we've seen about the fewest posts for troubles from a major new release since they started the CC thing back what, 2013 or so?

And on other forums I'm on, there's been numerous posts about how X is a ton faster on their machine than the 24.x series, or they like this and that but wouldn't mind this other thing going back. But certainly no great angst across that massive user base.

As an example, I'm not a 'fan' of the expanded Properties panel. But a lot of my editing acquaintances and online people love it. Takes all kinds, you know?

And some of the other old grouchies that were mad about the UI color changes tried the Vibrant option just to show how bad it was. And the posted that, actually, they really liked it.

The massive upgrade to color management and handling in this app would be worth the upgrade by itself.