![]() It’s curious that the “TOUCH” track and the “TRIM” track behave entirely differently after automation has been combined. As you can also see clearly on the first track, despite me ONLY lowering the fader, there is a gradual ramp upwards before that short drop. Instead the beginning of each track is now lower than the original 0dB. In any logical implementation this would write automation where I touched the fader, not anywhere else. The automation written by me on the first two tracks were two short bursts of attenuation. Not only do these tracks (in my opinion) incorrectly write automation when it does write automation, it also does it in the wrong place. The VCAs merely modify whatever the automation is on the tracks. We are able to change those tracks in PT independently of the VCA, including applying trim automation. This is in direct contrast to Pro Tools where the individual tracks are quasi-independent. That breaks trim automation because those faders then appear to be writing a trim value based on the “automation read” value, which in turn is given by the VCA. VCA Slave tracks with automation set to “global” never adjust faders to “+/-0dB” default when enabling TRIM in the automation panel. But either way, here are the items that seem to be just plain wrong to me: ![]() ![]() You should be able to see and understand what the issues are by just looking at the screen and follow the mouse clicks which are indicated.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |