Automation System Panel - Display and Function Triggers
08-21-2010 12:03 PM
Automation System Panel - Display and Function Triggers
Control a powerful automation system from a simple panel before you move on to configure your own controls for it
Comments and ideas and pointing out bad things in this design is requested and encouraged in the
January 5th 2014 - v44 update. Further refinement to make funciton and connection between capture & state buffer and state mode obvious, and that pass mode doesn't use those buffers.
Automation Button on TCP and floating panel v44
- Default behaviour produces the same results as the old automation system in v4.5 (July 29th 2012).
- Safety of your existing automation data
- Easy setup
- Easy to write exactly what you need to where you need it
- Easy to learn as you go
- Automation recording buffers - Pass and State
New automation is recorded to a buffer that runs on top of the existing automation.That buffer, or layer, takes presedence over the existing automation whereever it has data until it is either purged or commited.
What is recorded, written, read, captured and active is controlled from a simple control panel, built with simple, reusable images and text, with methods Reaper has already implemented.
Users can choose to use all the advanced funcitonality or just use a button on the Track Control Panel or Mixer Control Panel of a track.
Pass or state recording is controlled globally.
The Automation Commit button on the Track Control Panel.
The Automation Control panels for a quick overview and detailed control.
- Pass or State
The user can record the state of parameters over time, which is referred to as an automation pass, or the user can record just a single state for the parameters in the automation recording layer.
The profound difference between recording an automation pass and a state of parameters, is that an automation pass is bound to where it was recorded. A state of parameters is not. The recorded state can be held on to and applied (see Commit section) anywhere. The automation pass can only be commited to where it was recorded.
A state of parameters cannot or rather should not be recorded in touch mode, but only in Latch or Write mode. In Touch mode, the user would have to hold on to the controls of parameters he/she wishes to change, because by letting go, the parameter would return to what is already present on the automation lanes within the set “return time” in the preferences, after which readout of the existing automation lanes would resume.
That newly recorded layer can be applied to the actual envelope lanes at will or automatically when transport stops. Several options give the user a choice of where to commit a pass or a state of parameters.A state of parameters can be commited to within the boundaries of a time selection. Commiting a pass can be limited to a specific area with the time selection option.A state can be written back to the first punch in point which is where the user first wrote data for a parameter in to the automation recording layer.
- Write Enable
The user can prevent certain groups of parameters from having automation from the layer being commited to the envelopes lanes by using the “Write Enable” buttons. The “Write Enable” states are absolute and global. For example, if “All” or the the “Volume” buttons are not lit, nothing can be written to any volume envelope lane in the session.
- Recording and Commiting a Pass or a State
How to Commit
The user can commit, bypass or discard this recording with the Automation Button and the Automation Control Panel (see the PDF link in the introductory sectin of this request).
Switching between Pass and State mode
The automation recording layer can be switched to state mode (and back again). This switch between pass recording and state recording can be done in the context menu of the automation button, or the automation panel.
When switching from pass mode to state mode, the current state of the parameters in the automation layer are used and held on to, effectively freezing them in place. The automation recording layer is purged except for this value for every parameter recorded to the layer.
This can only be done in either in the automation mode Latch or Write. In Touch mode, the user would need to hold on to the controls of the parameters, or they'd return to the values on the existing envelopes lanes within the return time set in the preferences.
When switching from state mode to pass mode, the state is used as a starting value, in which all parameters are considered touched by the user.
Use case for state to pass switching
This way, using the automation mode Latch, a user could find starting values in state mode, locate transport to where he/she wants to start writing and perhaps ride those values, switch to pass mode and start playback.The options to commit a state, which is one value for any parameter recorded, are determined in the context menu of the automation button for a track, or globally on the automation panel. The pass mode has its own options to control where your recorded pass will be written to.
The automation recording layer would begin recording the parameters and the value previously set. The user can then dynamically change things, starting with a desired set of values.
Top to bottom, Automation Recording Buffer is empty , filled and bypassed.
Commit logs and snapshots
- Button states indicate Automation Pass buffer filled, empty or bypassed
The Automation Button will indicate whether an automation pass has been recorded on a track or not, by lighting up or being dark, similar to how the record-arm button indicates armed status.
Click to commit the automation pass or state (manual mode only)
ALT+click to empty the automation pass buffer. (only matters in manual mode)
SHIFT+click to bypass the automation pass buffer, just like you do for sends.(manual mode only)
CTRL+click to commit to all tracks (manual mode only)
- The Context menu revieals the Commit Options first, of which there are two for selected and all tracks. The mode is indicated with a symbol on the button.
The user has to click this button to commit an active pass to the track envelopes. If no automation pass has been recorded on the track, nothing will be commited, i.e. nothing happens.
- Commit on stop
The user doesn't have to do anything. Any recorded pass is commited as soon as the user stops transport. The user can loop around an area, playing with the parameters as he/she sees fit, and whatever was recorded.
Special Note: Latch mode will not start reading back the existing recorded pass when coming around for a loop, but keep writing with the value the user has set so far, unlike Reaper v4.14 Latch mode, which will start reading track data as soon as playback loops around.
- Manual (global)
Set manual commit mode for all tracks. Clean slate.
- Commit on stop (global) (default)
Set Commit on stop for all tracks. Clean slate.
- Commit source -> submenu
- Automation pass (default)
- Automation state (current values)
- Commit target -> submenu
- Automation pass area(default)
- Time Selection
- To Punch In (where the first parameter was touched)
- To Session Start
- To Session End
- Auto Parameter Grouping -> submenu
This is what Nuendo calls Touch-Assist. Maybe we should use that name for consistency.
Sometimes the user may wish to write to all the parameters of a plugin. Thus, in order to write automation data, they'd have to touch each parameter at least once. This is not effective in some instances, which is why this function HAS TO EXIST.
If "Auto Parameter Grouping"(or whatever its name will be) is ON, the user only has to touch one parameter of a plugin to put all of them in to a "touched" state.
All parameter will then be recorded in to the automation pass buffer. If in Latch mode, they will stay there until transport stops. If in Touch mode, they will stay there for the duration of the match-out time after the user lets go of the controls. Thus, to write to all parameters briefly, only touch mode is necessary, but for writing contiously Latch mode should be used, so the user doesn't have to hold on to any one of the parameters all the time.
- Off (default)
When off, only the parameters you touch will be recorded.
If one parameter of a plugin is touched, ALL parameters of that plugin are put in a touched state. This is also why Nuendo calls it Touch-Assist.
It lets users quickly write a bunch of parameters of a reverb for example. Highly efficient.
- Touch All Parameters and Touch All Parameters On All Tracks
This function can be used to do what the automation mode WRITE used to do. It is almost never used. This can be done during playback and in STOP mode.
The function puts all parameters of a track(or all tracks) in to the automation pass buffer. If the user wants to write a clean slate to a small area, all he/she needs to do is make a loop selection, activate this action, and hit play.
To do this in non-realtime, use of the automation panel is recommended.
Every commit is logged in the automation history, and can be named for later recall or reuse.
In addition, buffer contents can be saved away as snapshots for recall and commit. The user can capture specific states, such as the plugin states for selected tracks (button command "Ins"), for example.
The commit log, the automation history (with branching !!!!!!!!!!) and snapshots should be part of the project bay. More details are in the PDF linked to in the introductiory section.
Category Audio recording and playback
Priority 1 - Highest
Suggested Version 3.66
Implemented Version (none)
Users who would use this feature
Users who would not use this feature