Automation in Clip Mixer changing overall level

[HumbleDaisy]

Audio automation problem: Dragging a volume fader in the Clip Mixer, in Latch mode, will change the volume before the fade to the final state. There is no possibility to really undo this (undo undoes only the keyframes) except through the Remove Attributes menu. This happens in both Editing and Audio workspaces. Touch mode: same behavior - so doesn't return to previous state after the automation as it should.

[Kevin-Monahan]

Hi @HumbleDaisy,

Can the team have more info? See, How do I write a bug report?

Thanks,
Kevin

[HumbleDaisy]

Hi Kevin,
There are two systems and the bug happens on both:
1. iMac 2019, 6-Core Intel Core i5 (3,7GHz), 64GB RAM with MacOs 12.6.8 (Monterey) and a Sandisk G-drive 18TB (Thunderbolt-3)
2. MacBookPro M2 Max, MacOS Ventura 13.4 working from the internal disk (4TB)
Both run Premiere 24.6.1 (last version).
Formats: MXF video (XAVC-Intra 100 1080p25 and XDCAMHD 4:2:2 1080i50), plus BWF audio (8-10 channel wav). But 
Both multicam and non-multicam sequences
To replicate the problem just:
1. enable automation in the Audio Clip Mixer;
2. play the sequence and drag a fader. 

[HumbleDaisy]

Was that enough info, Kevin?

[HumbleDaisy]

Same problem in 24.6.3 and 25.0.

I have to go back to 24.3.

[Rach McIntire]

Hi @HumbleDaisy ,
Thanks for providing that extra info and the video clip.  I believe I see what you're talking about, but just to be sure, when you say "return to the previous state" can you clarify that?  What is the expected result?  Are you expecting the fader to go back to the start level?  

Thanks,
Rach

[HumbleDaisy]

Hi Rach,

I mean "previous state" as it used in your user guide (look under "Audio" > "Monitor Clip Volume and Pan Using Audio Clip Mixer" and scroll down to the section "Audio Clip Mixer automation modes". The "expected result" for Touch mode has also been described there and that is exactly to what I mean).
This aside, I think the clip shows clearly what is going wrong - I don't see much room for misinterpretation.

[Rach McIntire]

Hi @HumbleDaisy ,
I understand you're frustration, but the more information we have the better to help resolve the issue.  The reason I ask is because I can't tell from the video which mode you are in, Latch/ Touch.  

Latch would not return to the previous state until you until you’ve stopped your playback and then restarted again which is hard to tell from this clip.  Touch moves back over time, but unfortunately the video is too short for me to tell if it would move once released from the mouse click.  

Can you also tell me if you are using any third party plug ins?  I know you said it happens on mutiple systems, but are they different projects or the same project tried on both?

I hope this clears up my questions so we can try and figure out what is going on.  I'm  sorry you're having this problem. 

Thanks so much,
Rach

[HumbleDaisy]

Hi Rach,

Don't worry, I was not frustrated; just wondering.

Answering your questions as good as I can:

The clip showed Latch mode. 
Let me stress that the point is what happens to the volume line before the first keyframe. This part shouldn't be affected, but it is - in both Latch and Touch mode.

One system has some vst plugins installed, but they are not used in the projects. The other system has no plugins - it's new, I bought it one week ago and the only software installed is Adobe.

I could replicate the problem in different projects, using the media I described earlier but also (only) Adobe's sample media.

Hope this helps!

[Rach McIntire]

Updating Status

[Rach McIntire]

Hi @HumbleDaisy  ,
We do see this as a reproducable bug and I have filed a bug report.  
Can you try this work around and hopefully that can help until the issue is resolved.  Add a rogue keyframe on the clip and then delete it.  That should fix it.
Thanks,
Rach

[mstegner]

This bug is fixed and you should see the fix in the next beta build.

[Rach McIntire]

That's great news. Thanks!