How can a custom class compliant MIDI driver override the Apple MIDI driver??
How can a custom class compliant MIDI driver override the Apple MIDI driver??
- Subject: How can a custom class compliant MIDI driver override the Apple MIDI driver??
- From: gorouben <email@hidden>
- Date: Mon, 24 Oct 2011 00:04:29 +0200
Hi,
I've seen several posts about this problem, but never a found any solution.
I've a MIDI driver for a class compliant device. My problem: the Apple driver is loaded as well, resulting in the device appearing twice in Audio Midi Setup.
I wouldn't need a custom driver, except when I need to overwrite the device and vendor name.
In a mail from Doug Wyatt from March 6th 2006, I found that workaround:
> To be more specific you could write a driver that doesn't grab the device and do I/O, leaving that to the class driver. Your driver, once installed, would look for instances of your hardware and set the endpoint names on it.
I tried this workaround. It works except that the first time the device gets plugged in. In that case, my driver seems to be loaded before Apple's driver, and either I get the double device in Audio Midi Setup or MIDIGetNumberOfDevices doesn't find my device.
Don't know if I'm understandable or not... Hope I am!
Anyway, I have two questions:
1) Is there a way to prevent Apple's class MIDI driver to be loaded?
2) If not, is there a way to have a driver loaded before Apple's so Doug's code can work even the first time?
Thanks in advance
Eric
_______________________________________________
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