Author Topic: multi-client MIDI Drivers? MIDIMan (m-audio), Opcode, MOTU, and Turtle Beach  (Read 1487 times)

0 Members and 1 Guest are viewing this topic.

Offline chrisNova777

  • Administrator
  • Posts: 8554
  • Gender: Male
  • "Vintage MIDI Sequencing + Audio Production"
    • | vintage audio production software + hardware info
taken from the sound quest midi quest documentation circa 2002:

"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 MIDIMan(m-audio), 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."


All MIDI interfaces will be supplied with driver software, but this can be of several types, and it's worth explaining the difference between them. There's still much confusion about what constitutes a multi-client driver. Although it is possible for a single driver, that will run multiple MIDI ports, to be supplied, the musician's overriding need is for multiple programs to be able to access a single MIDI device. Here are definitions of the three types of 'multi' driver:

MULTI-CLIENT: This is a driver for a single port (such as MIDI) that allows several programs to access it simultaneously -- a sequencer and an editor, for example. Both the MIDI input and/or output may be multi-client. This interactive capability greatly aids the musician, by allowing you (for example) to change sounds in real time using a synth editor, while simultaneously playing back a sequence using another application.

• MULTI-PORT: This is a single driver that can send signals to several separate ports on a single interface -- each port will feature an additional 16 MIDI channels. An example of this is the MIDI Edge 1x4 interface, which has four independent MIDI outputs on a single card. Although this is extremely valuable, if each also has multi-client capability (as seems to be the case) that's really the icing on the cake. The other huge advantage of this type of interface is that the driver will normally only use a single interrupt -- even for an 8-in/8-out device!

• MULTI-CARD: The latest breed of soundcards sometimes come with drivers that are capable of controlling several other cards of the same type. Due to the often acute shortage of DMAs and IRQs in the average PC, a single driver that can run several pieces of hardware is welcome news indeed. The MIDI Edge 1x4 drivers can run two of these cards, and drivers are available for some Turtle Beach soundcards that will allow up to four cards to run from a single driver, giving multiple inputs and outputs. Although each card will probably use additional resources, designing drivers in this way will streamline processor overhead and minimise system conflicts. The alternative (trying to run up to four copies of the same driver, each with different settings) does not bear thinking about!