Age | Commit message (Collapse) | Author |
|
|
|
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
|
|
is false (since it is orthogonal)
|
|
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
|
|
|
|
|
|
|
|
no Route is set
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
emit a signal
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Old code was counting how many child nodes where in the MixerUI, assuming they
were all routes, and using that to decide if this was a from_scratch setup.
The addition of VCAs to the track_model changes that, so now we have to actually
check there are no existing Routes before doing the from_scratch setup
|
|
|
|
|
|
|
|
|
|
|
|
|
|
drop connection to master Changed signal when unassigning
|
|
|
|
See comments in the code for a bit more detail
|
|
|
|
|
|
Note that this includes some changes that actually make mixer pane settings get restored,
which has been broken for some time. Of course, they are not restored perfectly, yet.
|
|
More info in the code comments.
|
|
|
|
|
|
|
|
|
|
|
|
|