Marc Wielage wrote:I have also seen this kind of thing happened with corrupted Pan/Volume information in Pro Tools. If it gets a weird number that's not supposed to be there, it results in havoc (sometimes even crashes or corrupted sessions). I don't have a fix except to manually enter the correct value again and see if it "sticks."
Yeah. I've been editing exclusively in Fairlight for audio to simplify things for myself and it seems that alt-dragging clips sometimes suddenly enables automation on a track. This doesn't cause the 141F glitch and I haven't been able to reproduce it so far (fingers crossed it doesn't happen for final export). As a workaround, I will check pans of all channels before each export. Tedious but I am not on the latest version of Resolve and updating during a project would probably break a litany of VFX I've done.
I wish I could disable automation quickly on a track by track basis but seems the only way to do that is to go to automation settings, select what I want to disable, then use the range tool and go to the top bar on Mac to delete it.
The delete key unfortunately deletes the clip even when I'm in an automation viewing mode, unlike Pro Tools, so there doesn't seem to be a quick way when the software messes up. For reference, the alt-dragged clip contains no automation at all and it creating new track automation data doesn't make sense to me considering usually it just sticks an automation point at the same fader position, practically locking my fader unless I use or disable automation for the entire track...
Not to mention I'm also doing 5.1 surround so confusion was a guarantee in the first place. This is the sort of stuff I wish my university would teach me but apparently doing the same curriculum of a high school film class is enough for them...