6 Sep
2017
6 Sep
'17
8:27 a.m.
Figured it out. The so called "exclusive" mode is because of the application opening the port in "raw mode" So far I only used sequencer mode in my code and this did not bump into this situation.
On Mon, Sep 4, 2017 at 6:34 PM, happy musicmaker <happy.musicmaker@gmail.com
wrote:
I ready somewhere that some applications, like Bitwig, allocate(?) MIDI ports in "exclusive" mode so that other application cannot connect to the MIDI ports. I used Bitwig and confirmed that after starting Bitwig in qjackctrl you cannot connect any of the MIDI write/read ports. ( qjackctrl MIDI option is set to "none") I could not find any documentation on such "exclusive" feature though ?