As per title. CMD-clicking a trim automation node in PT 12.6.0 does not give 0.1 dB fine tuning of the automation, instead it snaps the node to the grid, even in slip mode. CMD-clicking regular volume automation still works as expected. (The current workaround is using the "extreme" track height temporarily)
would be nice to be able to assign the main fader on the Protools dock to automate send levels or any type of automation
Right now trim automation is only possible for volume automation. It would be great to have trim automation for any parameter, including panning and plug-in parameters. There's absolutely no reason why this wouldn't be possible. Right now it's totaly ridiculous that you have to grab that mouse to fine tune any non-volume automation parameter even if you're sitting behind a quadrillion dollar Avid console. This is an absolute ...more »
For volume automation, the scrollwheel of the mouse can be used to write/change the value, if the output window of a track is opened and the volume value is highlighted. Right now, the increments are very small, like 0.1 dB per detent. There could be a preference of how many dB one detent of the scrollwheel changes (like 0.1 or 0.5 or 1.0 or 2.0 or ...). Like with nudging clip gain. Changing the vol automation value with ...more »
During stop, after automation has been written or when editing automation, it is possible with Write-to-Current and a selection made, to assign the value at the start of the selection to be written over the whole selection. I often find myself wishing to write the value at the end of the selection to be written to the whole selection. The shortcut could be (Win) : Ctrl + Start + / (numpad). (Yes, during an automation ...more »
Pro Tools would benefit from having recallable mix "scenes" (or Automation parameter scenes) available within a single session. Users should be able to generate and store an arbitrary number of recallable scenes. When a scene is recalled, the faders, pans, send, plug-in settings/bypass, etc all change to their saved vales. This feature can allow for a number of significant workflow improvements. It would allow: -Alternate ...more »
If you want to change the auto mode of a channel twice in a row, you have to double tap instead of single tap the corresponding sel button twice instead of once 95% of the time. In combination with the lack of proper visual feedback on the s3 this is very annoying.
When touching a fader during playback, the according auto mode button in the right side softkey section of that channel starts to blink. It would be great if this would also work when playback is stopped. It would also be great if this would work for the trim button as well. Of course this is no subsitute for a proper automation mode indicator on the lcds, but it would already be helpful.
The automation mode selected from the "fixed" automation mode buttons (to the right of the fader) should change the Auto Mode of the ATTENTIONED track without having to press the "Select" button. This is MUCH more intuitive & saves an extra button click. Additionally, for auto modes, this should be a simple "click", and not a "click & hold". There's very little chance that an errant click is going to "accidentally" change ...more »
Start+Ctrl-clicking (Win) a plug-in parameter sets the track view to that automation lane. A new command like e.g. Shift+Start+Ctrl-clicking on another parameter of this plug-in would automatically open an additional automation lane. This avoids clicking on the little triangle and searching in a long list of parameters in the drop down menu. Useful to quickly display only those automation lanes for further editing, that ...more »
Similar to noncontinuous edit selections and their editing (like applying clip gain to multiple object-selected noncontinuous clips), there could be the possibilitiy to perform automation on multiple noncontinuous selections. Object-selected noncontinuous clips will generate a noncontinuous timeline selection and performed actions like automation will only be written to the selected clips and not to non-selected clips. ...more »
This idea has to have been brought up in the past, but I couldn't locate it with the search engine. What I'm talking about is a plugin that is basically an effects rack of plugins. If you have seen Nomad Factory Magma or Blue Cat Audio Patchwork, then you are already familiar with the concept I'm talking about. The difference between those 2 plugins being that you would be able use any of the plugins you have regardless ...more »
this happends in PT 12.4.0 -write automation to a clip by 'Write To All Enabled' -change the cliplength with the trim tool -breakpoints get lost or -add a fade-in or fade-out to the clip -move the fade-in around -> the breakpoint possition is set in the middle of the fade- -> this behaviour is wrong, and when correcting the automation by select the clip, write to all enable, all automation get's lost because there is ...more »
It'd be great to have playlists for automation. I'm a composer who frequently mixes music to Voiceover. I'll often do final automation tweaks on the master music bus. I then have to find a way to bypass or change those automation tweaks if the client wants the music without VO for another purpose. If there were automation playlists, I could recall different automation needs within the same session without having to ...more »
For example, take two audio tracks (i.e.dialog source tracks) and bus them to the same recording audio track (stem). Insert identical plugins on both source tracks. The plugins should be something, which plugin processing delay DEPENDS ON AUTOMATABLE PLUGIN PARAMETERS. I noticed this phenomena with Fabfilter Pro DS that has three switchable parameters (split band, look ahead, oversampling), which influence the plugin ...more »