Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
clamp/scale by masters only applies to non-boolean controls
|
|
|
|
This prevents overshoot e.g. when writing automation (and related oddities)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
master(s) value now just scales the control's own value; a trivial
bit of math at assign/deassign ensures that values do not change
during add/remove master operations
|
|
|
|
|
|
|
|
|
|
|
|
.. and leave some notes for the day when UI treemodel won't be canonical
to set order-keys.
|
|
|
|
- behaviour should match that of 4.x (move the first tempo
to frame 0).
|
|
|
|
|
|
- this fixes incorrect timing of new regions recorded
before the music origin.
|
|
|
|
|
|
|
|
|
|
- should fix 7234
|
|
|
|
|
|
|
|
saving state to disk
|
|
|
|
do not mark the current session dirty
|
|
context should potentially tell its ControlGroup
This fixes record-enable controls in a group failing generate
a call to the required stuff for tracks (moving meter position,
preparing diskstream) #7213
|
|
- the initial tempo must always be locked to meter,
so i think it is safe to explicitly set it anyway.
|
|
|
|
change, not just configuration changes.
This prevents a scenario where the route has had its solo control's state set from
XML, but then we configure the route's output, and invoke output_change_handler().
Without the new conditional, this would check which downstream routes are soloed,
find none, and then unset the soloed-by-downstream state of the solo control.
|
|
propagation
|
|
|
|
which may be slaved to a master
|
|
up back in the same state
|
|
|
|
|