I kept trying to mess around with the MidiInput.js, but alas, I kept failing. Is it something specific I have to do here to remove the midi filter?moss wrote: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.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?
MidiInput.prototype.createNoteInputBase = function (name, filters)
{
var noteInput = this.port.createNoteInput (name, filters);
noteInput.setShouldConsumeEvents (false);
return noteInput;
};
