tlw


Those saying a multi-client driver are right, and it's the best solution if one is available.

Otherwise, using MIDIox as a virtual splitter seems to work OK for me on Win7 64bit with UAC disabled.

I really can’t see the difference they both appear to use a buffer to copy data and allow two applications to use one midi stream. Maybe some one can explain the difference to me. One is more stable than the other?

I found the Asio Multiclient application. Unfortunately, it does not work with Sonar X1 64bit. Sonar X1 offers other audio drivers. Is it possible to use one of them, if another audio application uses another one? [I will try that.] tlw, you write about MidiOx as virtual splitter. I am not familiar with MidiOx. Do you have a short description or some screenshots of how to get a virtual splitter for a midi in device?

PROBLEM SOLVED WITH MIDI-OX! :-) That was a great tip. Midi-ox did exactly what I wished: Create two virtual ports from one midi-device. Is it possible that Midi-Ox is directly started, every time the computer starts?

Should be able to just drop the shortcut for MIDI-OX into the "Startup"
 folder in your "Programs" menu.

Provided the hardware connections haven't changed, MIDI-OX should start configured the same way as its last session.
 
MIDI-OX is definitely "THE" MIDI utility to have in the DAW arsenal!!

Funny this one !
I have just started having simmilar issues with midiquest as a mfx plugin. It used to work (like last week) but now it cannot access any of my midi ports which all have multi client drivers. I can use MIDI quest VYzeX or other Soft syns/Apps stand alone. They all happily share the midi ports but no midi quest MFX for no apparent reason. Rebirth works as rewire inside sonar and the midi drivers are fine sharing . ANY IDEAS?

rabeach

tlw


Those saying a multi-client driver are right, and it's the best solution if one is available.

Otherwise, using MIDIox as a virtual splitter seems to work OK for me on Win7 64bit with UAC disabled.

I really can’t see the difference they both appear to use a buffer to copy data and allow two applications to use one midi stream. Maybe some one can explain the difference to me. One is more stable than the other?

Stability has little to do with it. A multi-client driver will usually be supplied by the manufacturer of MIDI gear to go with their hardware. If one isn't available for the hardware, or in the case of software the software won't let you share a MIDI port with other software, a tool like MIDIox (or one of the other MIDI "virtual cables" around) comes into it's own.


MIDIox though does a lot of other things all of which are useful. Not just a MIDI router, it's also good for testing and fault finding, sysex dumps and all kinds of things. If you want to find out where MIDI is going in a PC, it makes the job easy. One of the most useful MIDI tools there is, and completely free.

tlw

rabeach

tlw


Those saying a multi-client driver are right, and it's the best solution if one is available.

Otherwise, using MIDIox as a virtual splitter seems to work OK for me on Win7 64bit with UAC disabled.

I really can’t see the difference they both appear to use a buffer to copy data and allow two applications to use one midi stream. Maybe some one can explain the difference to me. One is more stable than the other?

Stability has little to do with it. A multi-client driver will usually be supplied by the manufacturer of MIDI gear to go with their hardware. If one isn't available for the hardware, or in the case of software the software won't let you share a MIDI port with other software, a tool like MIDIox (or one of the other MIDI "virtual cables" around) comes into it's own.


MIDIox though does a lot of other things all of which are useful. Not just a MIDI router, it's also good for testing and fault finding, sysex dumps and all kinds of things. If you want to find out where MIDI is going in a PC, it makes the job easy. One of the most useful MIDI tools there is, and completely free.

I  use midi-ox and midi-yoke just didn't see why you thought multi-client driver was the better solution. Certainly if it was available with the OP's hardware it would be easier to implement and a better solution. But a third party solution as suggested above seemed to me to be the same as using midi-ox.

rivers88


Should be able to just drop the shortcut for MIDI-OX into the "Startup"
 folder in your "Programs" menu.

Provided the hardware connections haven't changed, MIDI-OX should start configured the same way as its last session.
 
MIDI-OX is definitely "THE" MIDI utility to have in the DAW arsenal!!

I copied the shortcut in the autostart folder. Problem is that the configuration only lasts, if the loop-cable is opened before. And both applications, Midi ox and loop cable, starts at the same time (or the cable before Midi Ox, I do not know). Is there a possibility to define the Autostart-options so that Midi ox is started AFTER the virtual loop cable?

windplayer

rivers88


Should be able to just drop the shortcut for MIDI-OX into the "Startup"
 folder in your "Programs" menu.

Provided the hardware connections haven't changed, MIDI-OX should start configured the same way as its last session.
 
MIDI-OX is definitely "THE" MIDI utility to have in the DAW arsenal!!

I copied the shortcut in the autostart folder. Problem is that the configuration only lasts, if the loop-cable is opened before. And both applications, Midi ox and loop cable, starts at the same time (or the cable before Midi Ox, I do not know). Is there a possibility to define the Autostart-options so that Midi ox is started AFTER the virtual loop cable?

Other options -
 
Setup the the virtual MIDI driver you're using to run as a Windows Service automatically - it should load ahead of anything in the Startup folder.
(You may have to do a web search to see how to do that for your particular driver ~ generally pretty easy).
 
OR
 
Leave the virtual MIDI driver as you have it now.
Insted of adding MIDI-OX to the Startup folder, pin it to the Taskbar or Start Menu.
You can then start MIDI-OX with one mouse click.

rivers88

windplayer

rivers88


Should be able to just drop the shortcut for MIDI-OX into the "Startup"
 folder in your "Programs" menu.

Provided the hardware connections haven't changed, MIDI-OX should start configured the same way as its last session.
 
MIDI-OX is definitely "THE" MIDI utility to have in the DAW arsenal!!

I copied the shortcut in the autostart folder. Problem is that the configuration only lasts, if the loop-cable is opened before. And both applications, Midi ox and loop cable, starts at the same time (or the cable before Midi Ox, I do not know). Is there a possibility to define the Autostart-options so that Midi ox is started AFTER the virtual loop cable?

Other options -
 
Setup the the virtual MIDI driver you're using to run as a Windows Service automatically - it should load ahead of anything in the Startup folder.
(You may have to do a web search to see how to do that for your particular driver ~ generally pretty easy).
 
OR
 
Leave the virtual MIDI driver as you have it now.
Insted of adding MIDI-OX to the Startup folder, pin it to the Taskbar or Start Menu.
You can then start MIDI-OX with one mouse click.

Interesting idea, to run the virtual MIDI driver as Windows Service.
I use the Loop cable of Tobias Erichson and installed the NT wrapper to define the cable as Windows Service.
http://www.duodata.de/ntwrapper/
The service appears, but the application does not open. :-(