plugdata-team
Multiple Midi Devices Order Issue
version 0.91 on Osx 10.13, 12 and 13
In Vanilla it's easy to set the order of MIDI devices (Ports) by selecting the order they are in in the "Midi Settings".
There is no way to do this in Plug Data?
I have ported a Vanilla patch that uses two different hardware controllers (Korg NanoKontrol on Port 1 and 12Step on Port 2 (17)) Loading the same patch into Plugdata has reversed the port order (Korg on port 2(17) and 12astep on port 1) so that the CC ma[ppings for each port make no sense and are unusable.
I have tried pluging the hardware devices in different orders but plug data has decided it will decide what hardware is on what port no matter what I do.
Is there something in the system I can edit to change this by hand?
Ive got around it at the moment by changing the MIDI note range on the 12Step controller and changing my code to allow Omni operation from the ctlin object and just letting plug data decide the ports but it would be great if we were able to choose the ports, if possible.
On the latest nightly builds, you can assign each MIDI device to a port. This is more flexible than what Pd offers, as you can also choose to route multiple devices to the same port. Hope it helps!
This is more flexible than what Pd offers
That depends on your system. On Linux with ALSA Pd is still more flexible as there the OS can route any MIDI port to any other MIDI port. (I explicitly don't say "device" here because you can route software ports as well).
This is more flexible than what Pd offers
That depends on your system. On Linux with ALSA Pd is still more flexible as there the OS can route any MIDI port to any other MIDI port. (I explicitly don't say "device" here because you can route software ports as well).
I guess, what I mean is that given the choice between:
- Allowing multiple ports to refer to the same midi input or
- Allowing multiple midi inputs to go to the same port
The first one is not actually useful. It allows you to create ports that are exact duplicates of each other, but there is no reason you'd want that. The second one is useful, because you can "merge" multiple MIDI inputs on a single port.
"Allowing multiple ports to refer to the same midi input or"..."The first one is not actually useful"
That is an assumption. There are many reasons users would want such a thing. The original post describes this.
I needed both the Korg nanoKontrol and 12-Step ports to talk to the same midiinput. Totally different physical controls both serving a purpose in the patch with a single midi input. You can see this in operation on the Organelle video.
I needed both the Korg nanoKontrol and 12-Step ports to talk to the same midiinput. Totally different physical controls both serving a purpose in the patch with a single midi input. You can see this in operation on the Organelle video.
I think that's what I described right, if I'm not mistaken? You want to send 2 midi inputs to the same port in Pd, so what plugdata does allows for that:
Whereas with pd-vanilla, you cannot do this:
The point is, pure-data allows you to do this instead:
Now, both port 1 and 2 receive from the same single device. So port 1 and 2 become interchangable, you might as well just use port 1 everywhere or port 2 everywhere in your patch.