Always use a sidechain input to control triggers
This allows MIDI trigger tacks to distinguish between music-data and control-data.
This commit is contained in:
parent
bf9ef3abd3
commit
e0f6ef4369
@ -109,13 +109,7 @@ Track::init ()
|
|||||||
boost::shared_ptr<TriggerBox> tb (new TriggerBox (_session, data_type ()));
|
boost::shared_ptr<TriggerBox> tb (new TriggerBox (_session, data_type ()));
|
||||||
tb->set_owner (this);
|
tb->set_owner (this);
|
||||||
add_processor (tb, _polarity);
|
add_processor (tb, _polarity);
|
||||||
if (data_type () == DataType::AUDIO) {
|
tb->add_midi_sidechain ();
|
||||||
/* if placing this in a route where the default
|
|
||||||
* data type is AUDIO, the triggerbox will need
|
|
||||||
* a sidehcain MIDI input to be able to be MIDI controlled
|
|
||||||
*/
|
|
||||||
tb->add_midi_sidechain ();
|
|
||||||
}
|
|
||||||
}
|
}
|
||||||
|
|
||||||
set_align_choice_from_io ();
|
set_align_choice_from_io ();
|
||||||
|
Loading…
Reference in New Issue
Block a user