My first hunch is that your Descriptors are not quite right. The folks over at [email protected] should be able to help you. I think that might be the first place to start with your question.
Brian On Dec 2, 2014, at 6:32 AM, Philip Lukidis <[email protected]> wrote: > I hope that this is the right list to which I should send this question (if > not, please let me know where I should attempt to address this). My issue is > with respect to VDCAssistant on 10.10.x. It opens at least one of our USB > Audio Class 2.0 devices (via IOUSBDeviceInterface182::USBDeviceOpenSeize), > thus preventing our frameworks from doing the same. At this point I'm not > sure if any of our other devices are affected in this way. Our USB Audio > Class 2.0 device has absolutely nothing to do with the onboard camera- > indeed, this even happens on a MacMini which has no camera, as well as a > Macbook which does have a camera. This does not happen on 10.9.x on either > Mac. > This is a serious problem for us- is there anyone from Apple who could > comment on why this is happening, and if there is something we could do to > have VDCAssistant cease to open our audio device(s)? I have pasted the > syslog message below (blanking out our USB VID/PID). > _______________________________________________ Do not post admin requests to the list. They will be ignored. Coreaudio-api mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/coreaudio-api/archive%40mail-archive.com This email sent to [email protected]
