![]() The device that isn't coming up correctly meets those criteria, so I wonder what else is missing. ![]() Now, according to, the Interface Association Descriptor needs to group all the audio descriptors together, they need to be contiguous, and they need to be ordered by Audio Control, then Audio Streaming, then MIDI streaming. If you use the drop down menu at the top of this window to switch to a different configuration, or define a new one, while the device is connected, it appears in the second configuration as Bar, with the correct manufacturer. However, with Mavericks, some devices (staying with the Foo/Bar example), though the audio interface gets named Bar, show up in the MIDI Studio window of AMS as "USB MIDI Device," and double-clicking reveals the manufacturer and model to be "Generic" and "USB MIDI Device," respectively. This is expected and desired, especially with devices that unlock features in non-free software. Microsoft-provided drivers for USB-IF approved device classes. If you double-click on the MIDI port, it shows the Model, "Bar," and additional information, including the manufacturer Foo, as retrieved from the USB descriptor. This article lists the Microsoft-provided drivers for the supported USB device classes. Some behave as they do in Mountain Lion and earlier: If manufacturer Foo makes a product Bar with audio and MIDI interfaces, then the Audio Midi Setup windows will show an audio interface named Bar, and a MIDI port named Bar. What does Mavericks need to use the product string from the USB descriptor as the name of the MIDI port? I have an assortment of USB Audio Class 2.0 compliant audio + MIDI interfaces.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |