Re: Custom Midi USB Plugin: now two devices
Re: Custom Midi USB Plugin: now two devices
- Subject: Re: Custom Midi USB Plugin: now two devices
- From: Doug Wyatt <email@hidden>
- Date: Fri, 17 Sep 2010 00:19:16 -0700
On Sep 16, 2010, at 21:45 , Chuck Carlson wrote:
> Hello,
>
> I'm customizing the SampleUSBMIDIDriver plugin and have added our usb vendor and product id and adjusted the parameters to MIDIDeviceCreate to add our manufacturer and product name.
>
> But, now two devices appear in Audio Midi Setup. Seems as though the default handler and the new plugin are creating their own device.
>
> How can I prevent this from happening?
Hi,
So, your device's descriptors say it is USB MIDI class compliant, causing the class driver to grab it as well as your own driver? If so, then what are you trying to accomplish by having your own driver? The best (and maybe only) way to avoid the class driver is to not publish the descriptors it's looking for.
If that's not the problem, then maybe there's something you're misinterpreting about how MIDIDevice objects are normally created by drivers when first located, then during subsequent sessions marked online or offline by the driver, and generally only deleted by the user when s/he's sure they're never coming back?
Doug
_______________________________________________
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