Customize USB Class Compliant MIDI Driver
Customize USB Class Compliant MIDI Driver
- Subject: Customize USB Class Compliant MIDI Driver
- From: "audio @dslextreme.com" <email@hidden>
- Date: Wed, 21 Sep 2011 05:06:49 -0700
I’m working on a product that exposes a class compliant USB MIDI
interface. The Apple in-box MIDI driver
matches and loads properly on this device and all MIDI functions are working. I need to implement some custom features and require
access to the MIDI data stream at the “driver layer.” (Between the MIDI server
and the device)
If there was a way to prevent the in-box MIDI driver from attaching
to my device, I could achieve my goals by implementing a USB MIDI driver CFPlug-in. However, I’m not sure if this is the best approach,
or if it’s possible.
Questions:
What is the proper method to implement a custom MIDI driver when
the hardware is class compliant?
Are
there some CFPlug-in methods I can use to reliably discover and hook the data
handlers of my devices class compliant driver instance?
Using a code-less kext, I was able to match against
my devices MIDI class Interface, but the in-box driver still discovered my devices
USB MIDI Interface; I don’t understand how a code-less kext would prevent a UserClient
from finding a device.
Thanks for reading my post,
-John
_______________________________________________
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