Hello @moss !
I am trying to use the akai apc mk2 footswitch1 (there is only one) like the push footswitch2 with the admin configuration (FootswitchCommand especially the FOOTSWITCH_2_CLIP_BASED_LOOPER
https://github.com/laurentdebricon/Driv ... 9ef7793a87
in this commit attempt, you can see i am not filtering anymore the sustain, and i adds note on
and note off
, otherwise if null bitwig forward default midi stuff(like sustain, so you can't control it) (right ?)
You talked about this in 2017 and tried to be a good student.
moss wrote: ↑
Mon Jun 26, 2017 10:12 pm
cjgolden wrote:Any way to make the Footswitch 2 function of
"Creates a new clip on the selected track and slot, starts play and enables overdub,"
avalible on the APC 40 mkii, which only has one footswitch input?
I tried going into APC.js and flipping the midi values sent for footswitch 1 and 2.
So it works sometimes, but the script crashes often when I press the footswitch.
I really think that this function is important for my workflow.
Is there a better way to do this?
The problem is that the Sustain data is directly routed to Bitwig. You have to decide if you want to do this on script start and cannot change this afterwards. If you want to make this work you have to remove the midi filter from the creation of the midi input. Look in the MidiImput class.
There is no more sustain (great), configuration in admin is there, but still, nothing happens. What am I missing ?
Be aware that a warning is written (even before my attempt, the message is there) :
"CC should be handled in Framework"
when using my sustain pedal