Hi,
External Hardware Trigger -> External Hardware Synths via USB Midi interface(s) and CopperLan
My idea was to setup:
External Trigger 1 -> VMidi1~ Vmidi1 ->External 1
External Trigger 2 -> VMidi1~ Vmidi1 ->External 2
External Trigger n -> VMidi1~ Vmidi1 ->External n....
....so every hardware trigger is connected to every External synth and so when windows decides to change USB port assignments, it wont affect the signal flow.
When I route directly I have signal connectivity, when going via a VMidi1...MidiOx sees VMidi1 activity but it is not being passed out of VMidi1 to the external world.
Yes:
Trigger-Source-Ch16 -> USBMidi -> Win8-Port1 -> [CP-Direct-Connection] -> Win8-Port2 ->USBMidi ->Trigger-Target-Ch16
No:
Trigger-Source-Ch16 -> USBMidi -> Win8-Port1 -> [VMidi1] -> Win8-Port2 ->USBMidi ->Trigger-Target-Ch16
** I have used a midi transformation application called TransMidiFier and used CopperLan as it's Loopback device. Using the same Copperlan set up, it works perfectly i.e it takes VMidi and sends to external synths as set up in CP. Something screwy with CP loopback?
Thanks,
Chris