Multiple devices interfere with each other if no dest id provided #405
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
On linux, if you have several devices that accept same MIDI messages, you need to connect them to different output/input in jackd, else a midi message will affect both devices. For example, if i try to change the led color of a button on APC40, some unrelated button on the Launchpad-S also change color (because each device interpret the MIDI note message differently).
With Modality on linux, connections are made for you all on the first output port of supercollider. It seems not trivial to change Modality to start bookkeeping which device use which port, but adding the device id to MIDIOut solve the problem neatly (because providing the device id on linux bypass jackd connections)