It's too complicated to explain right now, it's just annoying. My templates are incredibly planned and structured but this area so to say is where I like to have things "loose" and then often end up writing automation later to obtain the required precision. Or for instance, I've set up everything so that the channels controlled by VCAs are feeding into a group channel that is free and so I can push gain into that group which maybe has a compressor on it - my VCA is raising volume on the tracks which hit a compressor harder. Usually I'm starting all this work just positioning fader levels freely without automation though, and then wanting to adjust overall with the VCA, and then automate.MattiasNYC wrote: ↑Fri Nov 01, 2019 5:48 pmIt depends on what type of work you do and how you work.
If you're in post for example and are mixing just a plain old TV show to -24LFKS then it could very well be that you set dialog event level to close to -24LKFS and then ride faders to adjust for the dynamics of it. That can be done in various ways but I tend to use touch-trim when I do it even in Pro Tools which doesn't have this issue. I do it because it's easier to just quickly go back and, well, 'trim' something. So in this case I'm not bothered at all by the initial node. It makes zero difference.
If I'm riding music levels I'll probably go into latch for the first pass and so again it simply doesn't matter that there's a node there because I'll inevitably pull levels down before the first music hits anyway.
Or to state it all a different way: There's virtually no use-case for a lot of TV/broadcast/internet work where I don't end up writing automation from the beginning somewhere, and as soon as that's done there's an automation node there. So if it's there before initial writing or not makes zero difference.
I suppose if you're mixing music you might want it all clean and just move faders around without writing automation. I typically end up writing it anyway even if it's static because I want to be sure it recalls properly and avoid human error (i.e. I accidentally move a fader).
So for me templates worked in this regard.
What are the use-cases for you where you can't work with a template with an initial value of "unity gain" nodes at the top of the project?
but I guess I have to think about how to avoid all this now.