Author |
Topic: Sending a Signal BACK to Original Source? (Read 2681 times) |
|
Gitago
New Member
MIDI-OX Rules!
Posts: 2
|
 |
Sending a Signal BACK to Original Source?
« on: Jul 9th, 2021, 6:02pm » |
 Quote  Modify
|
Hello all.. I've got an "interesting" problem that I cannot seem to find a solution for...
I am using MIDI Ox to Redirect my physical device, to virtual devices... the programs the virtual devices are in allow me to send a signal OUT to my physical device in order to control the LEDs depending on whats happening..
Unfortunately this only works for one program....
I was wondering if there is something I can do in 'reverse' much like is happening with MIDI OX + Virtual Devices and it splitting off the signals for me...
here is a little 'diagram' of my issue visually..
 https://i.imgur.com/X9VxxlZ.png" alt="" border="0">
|
| « Last Edit: Jul 9th, 2021, 6:02pm by Gitago » |
 IP Logged |
|
|
|
Breath
Administrator
Gender: 
Posts: 1030
|
|
Re: Sending a Signal BACK to Original Source?
« Reply #1 on: Jul 9th, 2021, 11:13pm » |
Quote Modify
|
Hi
Microsoft's class compliant driver (not including the new Midi system in Win10) is single client (can only connect to one program at at time).
Hardware that comes with a driver (CD or download) is usually multi-cient (can connect to multiple programs ).
Your Nano, unfortunately, just plugs in without installing a driver and so uses the single client MS driver.
MidiYoke and loopMidi are both multi-client. So to make you Nano multi-client ...
1) run only MidiOx - it has to be left running for this to work.
2) connect the Nano input (left side of the Port Router window) to a loopMidi , let say "loopMidi1", Midi out (right side)
Now you should be able to connect any number of programs to loopMidi1 as an input which is really Midi coming in from your Nano.
Midi Ins from multiple Midi inputs will correctly merge to a single Midi stream that can be connected to multiple programs.
Midi coming from a program... MidiOx is running
1) Use another loopMidi, say "loopMidi2" and connect (left side) it to a hardware Midi Out (Nano on the right side)
2) Connect your programs Midi output to loopMidi2 as if it is the Nano.
Midi Outs from multiple programs will correctly merge to a single Midi stream if needed.
NOTE sometimes when changing these connections in the Midi Port Routing window, Midiox doesn't route system exclusive.
On the bottom right of the main MidiOx window there is 'SYS' button.
Click it Off then On again after you change the connections on the Port Routing window and that fixes it.
Let me know if this solves your problem.
All the best
Royce
|
|
IP Logged |
|
|
|
Gitago
New Member
MIDI-OX Rules!
Posts: 2
|
|
Re: Sending a Signal BACK to Original Source?
« Reply #2 on: Jul 9th, 2021, 11:35pm » |
Quote Modify
|
on Jul 9th, 2021, 11:13pm, Breath wrote:Hi
Microsoft's class compliant driver (not including the new Midi system in Win10) is single client (can only connect to one program at at time).
Hardware that comes with a driver (CD or download) is usually multi-cient (can connect to multiple programs ).
Your Nano, unfortunately, just plugs in without installing a driver and so uses the single client MS driver.
MidiYoke and loopMidi are both multi-client. So to make you Nano multi-client ...
1) run only MidiOx - it has to be left running for this to work.
2) connect the Nano input (left side of the Port Router window) to a loopMidi , let say "loopMidi1", Midi out (right side)
Now you should be able to connect any number of programs to loopMidi1 as an input which is really Midi coming in from your Nano.
Midi Ins from multiple Midi inputs will correctly merge to a single Midi stream that can be connected to multiple programs.
Midi coming from a program... MidiOx is running
1) Use another loopMidi, say "loopMidi2" and connect (left side) it to a hardware Midi Out (Nano on the right side)
2) Connect your programs Midi output to loopMidi2 as if it is the Nano.
Midi Outs from multiple programs will correctly merge to a single Midi stream if needed.
NOTE sometimes when changing these connections in the Midi Port Routing window, Midiox doesn't route system exclusive.
On the bottom right of the main MidiOx window there is 'SYS' button.
Click it Off then On again after you change the connections on the Port Routing window and that fixes it.
Let me know if this solves your problem.
All the best
Royce
|
|
heya Breath, appreciate the response!
I think I follow along, I've attached a picture, hoping this is what you were meaning..
I did actually only have Nano Kontrol + Midi-OX event port on the 'input' side of things.. so i went ahead and added the other devices as well, but unfortunately this did not seem to help the situation.. here is an image of where im at with that..
Im trying to connect
Nano -> TP_MIDI
Nano -> VM_MIDI
Then I want TP_MIDI and VM_MIDI able to send a signal back to Nano in order to trigger the lights as needed.
https://i.imgur.com/hc36BRS.png" alt="" border="0">
|
| « Last Edit: Jul 9th, 2021, 11:35pm by Gitago » |
IP Logged |
|
|
|
Breath
Administrator
Gender:
Posts: 1030
|
|
Re: Sending a Signal BACK to Original Source?
« Reply #3 on: Jul 10th, 2021, 10:43pm » |
Quote Modify
|
Before you start, I have discovered on the Korg website that there is a driver for the Nano to download.
I am thinking that it might be multi-client and that would solve your problems.
https://www.korg.com/us/support/download/product/1/285/
If not ......
Here is a pic on my machine with the ports renamed to match.
Note: to have the pic appear in the Forum you need to use http: not https:
eg http://bwalk.com.au/pub/Port_Merge.png
1) The data comes in from the Nano (red) -> loopMidi1 -> (light red) duplicated data to VM_Midi and TP_Midi.
2) The data comes in from VM_Midi AND TP_Midi -> loopMidi2 - merged (light blue) -> Nano (blue)
You have to have loopMidi or MidiYoke (then it would be MidiYoke1 and MidiYoke2). installed.
All the best
Royce
|
| « Last Edit: Jul 12th, 2021, 12:28am by Breath » |
IP Logged |
|
|
|
|
User Forum ::
Powered by YaBB
Home 
Help 
Search 
Members 
Login 
Register
Reply
Notify of replies
Send Topic
Print