Age | Commit message (Collapse) | Author |
|
|
|
|
|
The previously-commented code is precisely what gets invoked
when solo state changes, and had nothing to do with actually
changing solo state in any way.
|
|
|
|
|
|
Changing solo-state needs to be done in rt-context to atomically
propagate solo/mute.
set_control() queues a rt-event, later Session::rt_set_control() calls
Session::update_route_solo_state() to propagate solo/mute.
|
|
|
|
|
|
Subject To Change. Mileage May Vary. Offer Not Good In All Territories.
|
|
banks on a PI change
|
|
|
|
|
|
|
|
|
|
button ID
|
|
|
|
|
|
|
|
This reverts commit 0d7f88afbdb4477990706faa49a75e4dfb419b75.
|
|
make remapping work"
This reverts commit 16804e20c8d13b0b217410a208b9416845f48213.
|
|
remapping work
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
is received
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
That commit accidentally removed unrelated code in generic-midi surface
which just happened to have the same name (get/set_midi_feedback) as the
unused preference.
Regardless, there was more cruft there. GMCP midicontrollables now use
the control surfaces' feedback option.
|
|
|