Re: MIDI Plugin exclusive access
Re: MIDI Plugin exclusive access
- Subject: Re: MIDI Plugin exclusive access
- From: Herbie Robinson <email@hidden>
- Date: Wed, 22 Aug 2007 00:42:35 -0400
The MIDI Driver plug-ins get loaded from another process and the
application doesn't control when that process starts (it may already
be running when the application starts); so, any sort of trick with
creating temp files won't work.
OTOH, the whole point of writing the MIDI driver is so the hardware
can be shared. If one wants exclusive access, just attach the USB
device directly from the application and don't use the MIDI API at
all. You can still borrow all the device discovery code from the
Sample driver.
At 2:06 PM -0700 8/16/07, Todd Blanchard wrote:
You could try writing a lock file in /tmp on initialize.
On Aug 16, 2007, at 7:45 AM, haibo ye wrote:
Hi,
I created a MIDI plugin based on SampleUSBMIDIDriver.
It works fine with some MIDI clients, but I want the
MIDI plugin to be accessed exclusively, meaning that
only one client can open the MIDI device. I searched
the Apple mailing list, but could not find the answer.
Is there anyone who knows how to do it?
--
-*****************************************
** http://www.curbside-recording.com/ **
******************************************
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden