Author |
Topic: configure midiox for multi-client midi (Read 996 times) |
|
alexstringer
New Member
MIDI-OX Rules!
Posts: 3
|
 |
configure midiox for multi-client midi
« on: Jan 19th, 2005, 3:32pm » |
 Quote  Modify
|
Hey everybody,
I was told today that Midiox could be a problem to my multiclient midi issues. I've just installed it but it speaks chinese to me. Here's my problem: I try to have 2 midi applications( Sonar and Midiquestxl) share the same midi driver so i can use this midi editor (MQXL) as a midi plug-in within Sonar 3. I'm new to this forum so excuse me if this topic was already covered, but i really need to sort this out...
I'm using a Layla 24 as a soundcard and a PC 300 Roland midi keyboard usb plugged. I'd need the Roland to be able to play notes whether when i'm using Sonar as when i'm using MQXL, or when they are both opened on the same time...Does it make sense to you?
|
|
 IP Logged |
|
|
|
Peter L Jones
Expert
Hit it
Gender: 
Posts: 978
|
|
Re: configure midiox for multi-client midi
« Reply #1 on: Jan 19th, 2005, 4:55pm » |
Quote Modify
|
You want:
MIDIQuest [midi data->Out] ---> [midi data->In] Sonar
And then you also want
Roland PC300 [midi data->Out] ---> [midi data->In] Sonar
Yes?
You have a couple of options.
You need to use one hardware MIDI In port for the Roland PC300. No option there. Open the hardware IN port in Sonar and make sure MIDIQuest isn't using it for anything.
You could send the MIDI data from MIDI Quest OUT of the PC on one hardware MIDI Out port and then back IN to the PC on another MIDI In port. Assuming you have a spare hardware MIDI In port...
Alternatively, you could use MIDI Yoke. You don't need MIDI OX at all.
What MIDI Yoke does is act as a (number of) set(s) of MIDI Out/cable/In connections in software.
So MIDIQuest would open a MIDI Yoke Output port to send data OUT and Sonar would open a MIDI Yoke Input port to get the data IN from MIDIQuest.
|
| « Last Edit: Jan 19th, 2005, 4:58pm by Peter L Jones » |
IP Logged |
"...Playing fast around the drums is one thing. But to play with people for others, to listen to, that's something else. That's a whole other world." -- Tony Williams
|
|
|
alexstringer
New Member
MIDI-OX Rules!
Posts: 3
|
|
Re: configure midiox for multi-client midi
« Reply #2 on: Jan 19th, 2005, 5:41pm » |
Quote Modify
|
It's not so easy because MQxl has to be independant enough to use both midi driver ( in and out) of a same device to make a loop with an external hardware midi instrument that i have it connected to( in my case , i'm starting out with an Oberheim xpander) , and exchange sysex so MQXL communicate fully with the Oberheim.
|
|
IP Logged |
|
|
|
Peter L Jones
Expert
Hit it
Gender:
Posts: 978
|
|
Re: configure midiox for multi-client midi
« Reply #3 on: Jan 20th, 2005, 5:26am » |
Quote Modify
|
So add:
MIDIQuest [midi data->Out] ---> [midi data->In] Oberheim
Oberheim [midi data->Out] ---> [midi data->In] MIDIQuest
to the above.
Doesn't affect anything else, though. It's on a separate hardware port from the PC300, as that's USB.
|
|
IP Logged |
"...Playing fast around the drums is one thing. But to play with people for others, to listen to, that's something else. That's a whole other world." -- Tony Williams
|
|
|
alexstringer
New Member
MIDI-OX Rules!
Posts: 3
|
|
Re: configure midiox for multi-client midi
« Reply #4 on: Jan 20th, 2005, 11:00pm » |
Quote Modify
|
Peter,
Within MQXL, it's usually set as follow:
Port in: [Layla Midi]
Port out[Layla Midi]
and when you click on the oberheim, its send and receive sysex with MQXL and i'm able to edit the synth from MQxl.
But at this point:
a/ i'm not able to play the synth from the PC300 keyboard, when i select it in Port in, and MQxl doesn't communicate with the Oberheim.
b/When i open Cubase, Layla Midi ports is not available since it's in use by MQXL and as a matter of fact, in Cubase (orSonar) even if i select PC300 in Port in of the sequencer, port out :Layla midi is denied ( since in use by MQXL).
So, within MQXL, i tried to select Midi Yoke NT 1 in Port in & out ( being sure this port wasn't in use by any of the sequencers), but the synth and MQXL don't communicate to each other, then i tried Midi yoke 2,3,4...16 same problem.
Did i misunderstand something?
|
|
IP Logged |
|
|
|
Peter L Jones
Expert
Hit it
Gender:
Posts: 978
|
|
Re: configure midiox for multi-client midi
« Reply #5 on: Jan 21st, 2005, 5:15am » |
Quote Modify
|
Heh, it's always easier to work these things through with a picture rather than words... 
You want to be able to have the data from MIDIQuest going to Sonar? Essentially splitting the single out to two ins?
You need MIDI Yoke and MIDI OX for this.
Install MIDI Yoke and MIDI OX.
In MIDIQuest, pick one of the MIDI Yoke Junctions as out.
In MIDI OX, open that MIDI Yoke junction as an input, the Layla as an output and link them:
MIDIQuest [midi data->Out] --/midiyoke/-> [In->midi data] MIDI OX
MIDI OX [midi data->Out] --/Layla/-> [In->midi data] Oberheim
You can now also open the MIDI Yoke In in other programs (up to 4 in total, IIRC), such as Sonar, and receive what MIDIQuest is sending. Just be careful not to be sending two copies of every message - one through MIDI OX and one through Sonar. Don't set Sonar to forward messages received from MIDI Yoke to the Layla.
You can also send from Sonar to the Oberheim by opening the same MIDI Yoke junction as an Output.
You should then be able to play the synth from the PC300 using Sonar to route the data from the USB MIDI In to the MIDI Yoke out it has open. This way you can record the MIDI data. (The alternative is to have the PC300 bypass Sonar entirely using MIDI OX but the configuration is similar.)
|
| « Last Edit: Jan 21st, 2005, 5:20am by Peter L Jones » |
IP Logged |
"...Playing fast around the drums is one thing. But to play with people for others, to listen to, that's something else. That's a whole other world." -- Tony Williams
|
|
|
|
User Forum ::
Powered by YaBB
Home 
Help 
Search 
Members 
Login 
Register
Reply
Notify of replies
Send Topic
Print