3/25/2018
Posted by 

Apple Footer This site contains user submitted content, comments and opinions and is for informational purposes only. Apple may provide or recommend responses as a possible solution based on the information provided; every potential issue may involve several factors not detailed in the conversations captured in an electronic forum and Apple can therefore provide no guarantee as to the efficacy of any proposed solutions on the community forums. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the.

This section describes the Usbccgp.sys driver provided by Microsoft for composite devices. Many USB devices expose multiple USB interfaces. In USB terminology, these devices are called composite devices. Microsoft Windows 2000 and Windows 98 operating systems include a generic parent facility in the USB bus driver (Usbhub.sys) that exposes each interface of the composite device as a separate device. In Microsoft Windows XP and Windows Me, this facility is streamlined and improved by transferring it to an independent driver called the USB generic parent driver (Usbccgp.sys). Using the features of the generic parent driver, device vendors can make selective use of Microsoft-supplied driver support for some interfaces.

If you're going to use a Windows PC as a audio source via USB. In the DAC via USB and see if it finds and installs drivers. You do not need drivers for Mac. Mar 24, 2011 Generic USB Audio Device Driver - Take It From Here! Introducing the USB-SOUND7 Surround Sound USB Audio Adapter for Windows and Mac. Myphone Pinoy Content Free Download on this page.

Ploytec GmbH does ASIO drivers (Windows and Mac) and hardware for digital audio via USB1.1, USB2.0 and USB3.0. They do reference designs and a couple of audio and.

Generic Usb Audio Driver MacGeneric Audio Driver Problem

The interfaces of some composite device operate independently. For example, a composite USB keyboard with power buttons might have one interface for the keyboard and another interface for the power buttons. The USB generic parent driver enumerates each of these interfaces as a separate device.

The operating system loads the Microsoft-supplied keyboard driver to manage the keyboard interface, and the Microsoft-supplied power keys driver to manage the power keys interface. If the composite device has an interface that is not supported by native Windows drivers, the vendor of the device should provide a driver for the interfaces and an INF file. The INF file should have an INF DDInstall section that matches the device ID of interface. The INF file must not match the device ID for the composite device itself, because this prevents the generic parent driver from loading.

For an explanation of how the operating system loads the USB generic parent driver, see. Some devices group interfaces into interface collections that work together to perform a particular function.

When interfaces are grouped in interface collections, the generic parent driver treats each collection, rather than each individual interfaces, as a device. For more information on how the generic parent driver manages interface collections, see. After the operating system loads the client drivers for the interfaces of a composite device, the generic parent driver multiplexes the data flow from the client drivers, combining these separate interactions into a single data stream for the composite device.