Author |
Topic: Help with Cubase Midi-ox and alpha Juno 1 (Read 2783 times) |
|
hiro
New Member
MIDI-OX Rules!
Posts: 2
|
 |
Help with Cubase Midi-ox and alpha Juno 1
« on: Oct 12th, 2004, 2:32pm » |
 Quote  Modify
|
Hi folks, can anyone help with this little problem,
I've managed to get midi-ox running with cubase vst 5, xgedit and my sw1000xg card. It was set as required by the xgedit and sw100xg documention and this works great for real time recording of xgedits to the card parameters.....but when it's all running I lose my Alpha Juno hard synth...stop midi-ox and the juno's back in the mix.
I have noticed when I start midi-ox after cubase i get 2 midiox error messages about sw1000 IN and sw1000 OUT being used by another application (cubase, I assume)....so does that mean when midi-ox starts first it grabs hold of the sw1000xg in and out, preventing cubase communicating it's midi to the juno?
what do i need to do to midiox to allow cubase to talk to my juno? It's really infuriating because it's almost so close after banging my head against a wall for a week.
Your help would be greatly appreciated.
App settings:
XGEDIT, Midi in = none, Midi out 1 = NT Yoke 1, Midi Out 2 = NT Yoke 2
Cubase, Midi in = NT Yoke 1, Midi out = SW1000 OUT
Midi-Ox settings:
MIDI INs > Yoke 1, Yoke 2, SW1000 IN
MIDI Outs > SW1000 Out, SW1000 #1Synth
Mappings: (notation as follows)
INPUT PORT <> OUTPUT PORT
Yoke 1 <> SW1000#1Synth
SW1000MIDI IN <> SW1000 MIDI OUT
MIDI-OX Event Port <> BOTH of above ports
I have tried to keep it simple by ommiting things like Midi Yoke 2 and the other Sw!000~2&3 Synths
|
|
 IP Logged |
|
|
|
Jamie OConnell
Administrator
 
Gender: 
Posts: 2027
|
|
Re: Help with Cubase Midi-ox and alpha Juno 1
« Reply #1 on: Oct 12th, 2004, 4:20pm » |
Quote Modify
|
Quote:| I have noticed when I start midi-ox after cubase i get 2 midiox error messages about sw1000 IN and sw1000 OUT being used by another application (cubase, I assume)....so does that mean when midi-ox starts first it grabs hold of the sw1000xg in and out, preventing cubase communicating it's midi to the juno? |
|
Yes. But you can 'virtualize' this connection with another MIDI-OX instance and 1 more MIDI Yoke port. Single client drivers can only handle a single connection to an application. It sounds like only the SW1000 Out is in this category from your description. To work around this, replace every instance of SW1000 OUT in your diagram with MIDI Yoke NT 3 Out. Now launch another MIDI-OX instance and attach MIDI Yoke NT 3 IN as input and SW1000 OUT as Output. You now have a single connection to SW1000 Out, and Cubase and MIDI-OX (1) are routing thru MIDI-OX (2) via MIDI Yoke 3.
|
|
IP Logged |
--Jamie
Music is its own reward.
|
|
|
hiro
New Member
MIDI-OX Rules!
Posts: 2
|
|
Re: Help with Cubase Midi-ox and alpha Juno 1
« Reply #2 on: Oct 12th, 2004, 5:30pm » |
Quote Modify
|
cheers, that sounds positive,
after posting my request I tried just removing all references to sw1000 out from midi-ox (if it does not know it's there it can't grab it, right?) - this does the trick, but i'm sure it's done it with some restrictions that i've yet to discover.
In your example would I have to tell cubase to run midi out on yoke 3 as well?
|
|
IP Logged |
|
|
|
Jamie OConnell
Administrator
Gender:
Posts: 2027
|
|
Re: Help with Cubase Midi-ox and alpha Juno 1
« Reply #3 on: Oct 13th, 2004, 1:50pm » |
Quote Modify
|
Quote:| In your example would I have to tell cubase to run midi out on yoke 3 as well? |
|
Yes. MIDI Yoke 3 would merge outputs from Cubase and from MIDI-OX (1) and pass them along to MIDI-OX (2) and the SW1000 MIDI Output.
|
| « Last Edit: Oct 13th, 2004, 1:51pm by Jamie OConnell » |
IP Logged |
--Jamie
Music is its own reward.
|
|
|
|
User Forum ::
Powered by YaBB
Home 
Help 
Search 
Members 
Login 
Register
Reply
Notify of replies
Send Topic
Print