|
|||||||
![]() |
|
|
Thread Tools |
|
|
#1 |
|
DriverHeaven Junior Member
Join Date: Dec 2002
Location: Scotland
Posts: 93
Rep Power: 0 ![]() |
multi-client MIDI?
would it be possible to have multi-client midi capabilities (i.e. 2 programs can use the midi interface at the same time) using the SB0060? or is it a hardware limitation, and therefore not possible?
|
|
|
|
|
|
#2 |
|
kX Project Lead Programmer and Coordinator
Join Date: Dec 2002
Posts: 3,119
Rep Power: 75 ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
multiclient capability is already supported for all the MIDI/UART devices except UART OUT
/Eugene |
|
|
|
|
|
|
|
|
DriverHeaven Junior Member
Join Date: Dec 2002
Location: Scotland
Posts: 93
Rep Power: 0 ![]() |
Quote:
....any idea when this will be implemented? in the next few releases?
|
|
|
|
|
|
|
#4 |
|
kX Project Lead Programmer and Coordinator
Join Date: Dec 2002
Posts: 3,119
Rep Power: 75 ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
this port cannot be made 'multiclient' -- this will cause synchronization issues
(imagine: two applications output data simultaneously -- this will mix up all midi events) you may try searching the net for some third-party 'virtual' midi drivers that have the desired functionality /Eugene |
|
|
|
|
|
|
|
DriverHeaven Junior Member
Join Date: Dec 2002
Location: Scotland
Posts: 93
Rep Power: 0 ![]() |
ok, here's what i'm trying to do...
i've got a program called "sound quest midi quest" it's a patch manager for hardware synths. it lets you upload and download and organise all your patches. there's a vst version, but i can't get it to work in cubase. I can select UART IN as the IN port ok, but when I try to select UART OUT as the OUT port, it says "can't open midi out port kx UART sb...... driver may already be in use" the documentation states: "Important: It is also important to note that both Midi Quest and Cubase will need to have these ports open simultaneously so you need to use a MIDI interface with "multi-client" drivers (or constantly enable and disable MIDI drivers in Cubase and Midi Quest VST). Multi-client drivers allow more than one MIDI application to access the interface at the same time. Companies which offer multi-client drivers include MIDI Man, Opcode, MOTU, and Turtle Beach. You will find that the driver which come with your standard sound card, including those made by Creative Labs, are not multi-client." any ideas on how I could get this to work? |
|
|
|
|
|
|
|
|
DriverHeaven Junior Member
Join Date: Dec 2002
Location: Scotland
Posts: 93
Rep Power: 0 ![]() |
Quote:
|
|
|
|
|
|
|
#7 |
|
DH Senior Member
Join Date: Jan 2003
Location: The Netherlands
Posts: 1,932
Rep Power: 64 ![]() ![]() ![]() ![]() |
As Eugene already suggested;
Try some "virtual midi drivers" sometimes called "virtual midi cabels" like: Hubbie's Midi Loopback Driver, or MidiYoke. MidiYoke works ok in XP, but I dunno for sure about the multiclient stuff. Hubbie''s I used alot on W9X and its multi-client functions works great. Dunno if Hubbie's has a working version for XP. G-luck....... |
|
|
|
|
|
#8 |
|
HardwareHeaven Lover
Join Date: Feb 2003
Posts: 213
Rep Power: 0 ![]() |
Midi yoke, together with MidiOX works to solve this problem I guess... you can get them from the same site (google for midiox)
|
|
|
|
|
|
#9 |
|
DriverHeaven Lover
Join Date: Mar 2003
Posts: 228
Rep Power: 0 ![]() |
I use Midi Ox and Midi Yoke together and it works great and both are free if i remember correctly.
Schel Sullivan |
|
|
|
|
|
#10 |
|
DH Senior Member
Join Date: Jan 2003
Location: The Netherlands
Posts: 1,932
Rep Power: 64 ![]() ![]() ![]() ![]() |
Correct me if i am wrong, but trance1meister question is how to run
"Sound Quest" and Cubase parralel using the same Midi I/O's Cubase does. I really dont see how MidiOx fit's in this story. MidiYoke or Hubbie's wil solve his problem if setup properly. Yes, both MidiYoke and MidiOX are free at: http://www.midiox.com/index.htm?<a h.../myoke.htm</a> Correction mispelled name. It's: "Hubi's MIDI Loopback Device" Also free at: http://members.magnet.at/hubwin/midi.html Cheers..... |
|
|
|
|
|
#11 |
|
HardwareHeaven Lover
Join Date: Feb 2003
Posts: 213
Rep Power: 0 ![]() |
As I see it, MidiOX would be used to mix 'n match the midi channels or something to the correct midi out... using 2 midi yoke lines as input for MidiOX... thas where MidiOX comes in... (Yoke in itself cannot route or map any lines itself to the UART... you need MidiOX for that... or maybe Cubase itself, but setting it up in cubase, with all mappings, would probably be more of a hassle then simply using OX)
|
|
|
|
|
|
#12 |
|
DH Senior Member
Join Date: Jan 2003
Location: The Netherlands
Posts: 1,932
Rep Power: 64 ![]() ![]() ![]() ![]() |
Ahh.., now I understand your aproach using OX as "the router".
You are totaly right Mata Hari! That's why I prefer Hubi's Midi Loopback Driver. Just like MidiYoke it provides the virtual midi ports but in addition you can fire up an unlimited nr. of "Virtual midi cables" (with a minimum of overhead) and do every possible routing/merging. That way you can have several active Midi apps streaming midi data to 1 physical Midi port or between the apps themselfs. To bad that (AFAIK) hubi's is not NT/XP compatibel ![]() So yes,..MidiYoke+Ox is the way to go. Thanks for the clarification...(funny, I wasn't the one with the problem )Cheers all.... |
|
|
|
![]() |
| Thread Tools | |
|
|