Age | Commit message (Collapse) | Author |
|
significance of ParameterDescriptor
|
|
This allows it to be used everywhere, as intended
|
|
make sure data gets out
|
|
|
|
|
|
these now control punch in, punch out, external sync and follow edits, respectively
|
|
accesss GUI actions
|
|
|
|
|
|
some sessions name that send "Monitor" and some "Monitor 1"
The correct solution is a test of whether the send is connected to the monitor section.
|
|
controllable values from vpot events
This is still not really right - it doesn't do the right thing, i think, for trim controls
|
|
|
|
|
|
|
|
|
|
|
|
controls correctly (or more correctly
|
|
|
|
|
|
|
|
AutomationControl for track monitoring choice
|
|
ParameterDescriptor
|
|
|
|
More controls/pots to come
|
|
banking
|
|
|
|
|
|
|
|
|
|
|
|
|
|
With some LED action that would even better with blinking
|
|
rewind/ffwd)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
selected route
|
|
automation state for selected routes
|
|
as the selection
|
|
all ::clear_*() methods
This allows the clear methods to be used before calling ::add(), to avoid the
emission of a signal saying "there are no <foo> selected right now".
There should be no side-effects from this commit.
Note that correct use of this new API is complex, and requires avoiding the use
of wrapper methods like clear_objects().
|
|
message
|
|
|
|
|
|
|
|
Routes in the future
|
|
|