| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
This is better tested with direct use of the solo_control and
Config->get_solo_controls_are_listen_controls()
|
|
|
|
|
|
it usefl
|
|
|
|
|
|
|
|
get the logic right for boolean controls
|
|
|
|
VCA solo+mute (BUT ARE NOT DONE YET)
|
|
session
|
|
condition
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
design ... review coming ]
|
|
|
|
|
|
|
|
|
|
and used. The controls now own their own state, rather than proxy for state in their owners.
Massive changes all over the code to accomodate this. Many things are not finished. Consider this a backup safety commit
|
|
control is enabled/disabled. Add AutomationControl::master_changed() as a virtual method to handle ... master value changes
|
|
GroupControlDisposition)
This allows the signal to convey more information, which may be required by some handlers of a control's Changed signal
|
|
about solo/mute changes
|
|
Route now calls back into Session when solo/mute/listen state changes. All other interested
parties must use the Route::{solo,mute,...}_control()->Changed() to be notified of changes.
The Session requires more information than the Changed signal can provide, in order to
propagate solo/mute changes across the entire Session correctly.
Note that this uses an experimental use of CRTP to isolate a public API within Session
|
|
logic and consistent master/slave behaviour
|
|
AutomationControl
|
|
The first step of generalizing master/slave to other controls
|
|
|
|
|
|
|
|
|
|
|
|
|
|
emit a signal
|
|
|
|
|
|
|
|
|
|
|
|
|
