orion orphaned process

by **D-Fusion** » Thu Apr 16, 2009 7:43 pm

What midi equipment do you use?
And is it USB or Midi Connection?

by **Marcin** » Thu Apr 16, 2009 8:30 pm

@D-Fusion - have You ever seen asio by midi connection? :-)

I found that there is no matter if it is USB or PCI sound card. Just probs when audio device is in use.

by **D-Fusion** » Fri Apr 17, 2009 6:09 am

-intro-one- wrote:@D-Fusion - have You ever seen asio by midi connection?

I found that there is no matter if it is USB or PCI sound card. Just probs when audio device is in use.

Read what i wrote again

I asked about what Midi equipment he uses and if it is connected via USB or MIDI.

The reason that i ask for this is because M-Audio's Midi equipment is known to do this kind of things if it is connected by USB and the solution then is to unplug the USB cable or turn of the keyboard to get the music program to quit.

This happens now and then in most music programs with USB connected Midi keyboards or hubs.

by **Marcin** » Fri Apr 17, 2009 6:16 am

@D-Fusion - right, sorry :-)

I was too sleepy yesterday

Maby there is some USB issue, but for me, as I said, I haven't probs since I use my own single instance app and in fact it can be one of many things.

by **suneel** » Fri Apr 17, 2009 3:17 pm

-intro-one- wrote:@D-Fusion - have You ever seen asio by midi connection?

lol funny

no dfusion i donot have midi equipment connected when this problem occurs. But i am using Focusrite liquid mix firewire hardware. it works as a vst plug. could this be the reason? dont know i will have to check it out later when i get time