Hi folks. I've been building some USB-Midi interface/ controllers using LC's and 3.2's. and although everything works as intended, Ive found that I can only make one single connection to a Teensy-Midi Port on the system's host PC.
Using a Win7 host. IDE1.8.5 TD 1.48.
Scenario. A T3_2 with the appropriate Din Midi interface hardware, coded as a USB-Midi interface shows up on the host as Teensy MIDI. I can plug a Roland synth into it and point the Synth editor to Teensy Midi and it works.
If I then start Midox and attempt to connect a keyboard to the same Teensy Midi port, Midiox reports an "Out of memory" error. Seemingly this is Midiox's generic error message response to Windows reporting an error with the respective Midi port but fails to notify the error type.
This is typically what happens when Midiox tries to connect to a Midi port that some other application has already connected to so in short, my Windows host sees a TeensyMidi port as single client.
Sure, a workaround is to use some more LoopMidi pipes.
Have I missed or messed something or is Teensy Midi not multi-client?
Thanks in advance. Teensy Rocks!
Using a Win7 host. IDE1.8.5 TD 1.48.
Scenario. A T3_2 with the appropriate Din Midi interface hardware, coded as a USB-Midi interface shows up on the host as Teensy MIDI. I can plug a Roland synth into it and point the Synth editor to Teensy Midi and it works.
If I then start Midox and attempt to connect a keyboard to the same Teensy Midi port, Midiox reports an "Out of memory" error. Seemingly this is Midiox's generic error message response to Windows reporting an error with the respective Midi port but fails to notify the error type.
This is typically what happens when Midiox tries to connect to a Midi port that some other application has already connected to so in short, my Windows host sees a TeensyMidi port as single client.
Sure, a workaround is to use some more LoopMidi pipes.
Have I missed or messed something or is Teensy Midi not multi-client?
Thanks in advance. Teensy Rocks!