Automation system:
-
Glide automation. Nearly every Pro Tools engineer I’ve heard talking about their experience in Nuendo complained about it not being there.
-
Trim should fill loop. What is intuitive and productive is that when you set "Fill” to “Loop” whatever you do to the automation system actually fills the loop range. If I set “Fill”, “Loop” and have “Trim” / “Touch” selected and move a fader then what I want to do is apply the trim-offset to the loop range.
-
Auto join on a per-track basis: Please give us the option where touching one fader triggers auto-join on that track only. The reason is that a lot of times I am writing automation in latch and then need to go back and adjust one track only for one section and when touching the fader to do this all tracks auto-join which is not the behavior I want. I want the tracks to auto-join individually as they reach their last written automation points instead. Currently, if I do nothing but play back without touching faders each track auto-joins as expected and I see no reason to change this behavior for un-touched faders just because you touch a completely different fader. The way it currently is I have to re-touch each fader to get it to pick up where it left off, which is obviously annoying if there is movement that is different on different tracks (having to time the re-touch). Also give the option to force faders into “latch” when auto-joining.
-
Two-state-options in the automation panel. The current three-state options leads to accidentally choosing the wrong setting. Along with a previously posted automation bug (or design flaw) it is especially common with “loop”. By having only either on or off for each we avoid that, and we could then have another, additional "function” for “lock”. Let us then assign the on/off toggle to one key command and lock on/off to another.
-
Punch to loop inside loop only. Currently if “fill’ is set to “loop” the intuitive expectation is for anything that is done filling loop range. However, if you set Fill + Loop + Latch and write automation outside the range it fills loop and outside of the range. It doesn’t much matter to me if it is by accident or on purpose.
-
“Reveal Parameter On Write” key command binding. It would be great to be able to toggle this with a key command. I never use this because I end up with too many automation lanes visible, so being able to temporarily turn this on before touching a parameter and then turning it off would be great.
-
Copy-Paste level automation between faders and sends. It can be very convenient to copy the fader level automation to one or more sends, and vice versa.
-
Copy-Paste level automation between faders and events (gain). Same as above. Sometimes convenient.
-
Add playlists / track versions for at least volume automation on at least group tracks. Use case is mix revisions where levels are changed giving us the option to easily A/B previous version or easily restore.
-
“Events” on group and FX tracks. These events would not contain audio but instead function as placeholders of the automation of those tracks. With “automation follows events” enabled we can then move automation in the same way we move audio. It also allows us to label and color code the events according to what happens at that point. Imagine a reverb track with settings automated per location, e.g. a room, a warehouse, a hallway etc. By color coding and labeling them we can easily jump to where the hallway was, copy it, and then paste that back in a later location. Also have the ability to then extend or shrink that range easily by just using the event to do so. Arguably easier, faster and more intuitive than other ways of going about it right now. There is a video of a person doing this in Pro Tools and it’s actually odd that nobody has thought of applying this yet.
-
Automation safe of Plugins or any parameters (in a convenient way) (from other user) Even when automating many things “all the time”, some global Plugins or parameters of channels that are write enabled should be isolated from writing. Always. whether I turn global write on or toggle suspend automation.
-
Trim automation Fader not in the middle of fader range but at 0dB (from other user) have you ever tried to mix with some Faders set to trim at the same time with some faders set to “normal” automation mode?
-
smaller automation panel for me it seems too huge to have it open, The ProTools one is sufficient for most Information
VCAs:
-
Spill. I think we need it. This would allow us much better navigation in larger projects, and a trend seems to be for studios and stages to move away from larger consoles to fewer faders. With hundreds of tracks and a flexible spill functionality either just natively (VCA) or via Eucon navigation can improve.
-
Mute. It is odd that the “mute” doesn’t actually mute controlled tracks but “solo” solos them..
-
More control flexibility. In Alsihad for example VCAs are effectively controlling sets of tracks but a VCA does not exclusively control all members of a set. This means that once an individual track has been assigned to one set it can still be assigned to an additional set. For example: Dialog 1-8 can be assigned to set #1, which in turn is controlled by VCA #1, but Dialog 2, 5 and 6 can also be assigned to set #2 which in turn is controlled by VCA #2. A potential use-case for this is to have an ad-hoc VCA that is assigned temporarily to whatever the user wants. It does not override previous assignments but acts alongside them. It would let you for example select a subset of your SFX tracks and add them to the ad-hoc VCA for quick automation of all levels. While Nuendo allows “nesting” VCAs I think this other way of doing it is ultimately more flexible. (The “set” I’m referring to here is called “group” in PT).
Eucon:
- Add more Control Room functionality.
- Generally bring up to par with Pro Tools