| Age | Commit message (Collapse) | Author |
|---|
|
This also removes Route::group_gain_control() and associated machinery.
Not yet tested with Mackie or other surfaces. More work to done to
start using the group capabilities, and also potentially to add
or derive more controls as RouteAutomationControls
|
|
sure to initialize descriptor member to null
|
|
|
|
This new design will work even when threads that need to receive
messages from RT threads are created *after* the RT threads. The
existing design would fail because the RT thread(s) would never
be known the later created threads, and so signals emitted by the
RT thread and causing call_slot() in the receiver would end up
being enqueued using a lock-protected list. The new design ensures
that communication always uses a lock-free FIFO instead
|
|
|
|
|
|
after timeout.
|
|
(shift-rew)
|
|
|
|
|
|
Change from Evoral::Parameter to AutomationType caused this glitch
|
|
|
|
state mgmt
|
|
|
|
|
|
|
|
to provide panning and EQ control
|
|
|
|
|
|
repeated user action from adding multiple markers when stopped (mackie version)
|
|
|
|
|
|
|
|
manual/off; off button is never sent an LED state message to avoid fader disabling
|
|
|
|
|
|
figure out why it kills the fader
|
|
cut-n-paste
|
|
|
|
|
|
Somehow fails to move master fader to correct position when monitor section is added
|
|
transport moves faster than 800%.
|
|
|
|
|
|
|
|
and that will be rediscovered on next startup
|
|
|
|
for muted-by-others; blink transport for speed != 1.0 && != 0
|
|
|
|
boost::shared_ptr<Port> (2) detect connection changes
|
|
Given that we use "port" after the test, the test makes no sense
|
|
|
|
|
|
|
|
button when used as a modifier
|
|
|
|
|
|
|
|
|
|
2 remaining problems:
* IO selectors are not updated if you change the connection outside the dialog.
* occasional crash on the next startup, after a connection is made from the menu.
|
