I set a preset to inactive because I found a better way of controlling how MTP started clips in response to fader movements. Originally, I used feedback from Ableton Live to determine when a clip is started. I believe this feedback may still have been input by MTP and that it caused MIDI input buffer overruns which wreaked havoc when playing live.
What I’ve done now is to delete the preset that had the port which had Live as its input source. The buffer overrun seems to no longer happen.
Is it possible that MTP was still getting input from that port, but not using it for anything (since the preset was inactive) and therefore overloading the port and causing the overruns?
Another thing I notice is the jitter on some inputs from my APC mini faders seems to have disappeared too. And the jitter was intermittent. Sometimes the controllers were absolutely rock solid. Other times the some, but not all the faders would jump around with no movement on my part.
A incoming MIDI port will be open if its preset is active. The MIDI port will be closed when the preset using it is inactive (unless another preset, translator, or MIDI route using that same port is still active) .
You should be able to determine if a port is open at any given time by selecting at the project level and then scanning your eyes down the right to see which ports are open.
Of course, if an alias points to a given port that is open, the alias will show open as well.
It is possible that some slight jars of the table that the controller rests upon would cause false fader movements, but again, only if the port is open.
In a nutshell, any incoming MIDI on non-open ports is ignored.
If you remember from a few years ago, we had observed crashing of the APC MINI due to fader feedback.
Finally, if there is a MIDI route using that MIDI port, the respective MIDI ports will be open as long as that MIDI route is enabled.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz