Generic "usb midi device" in 10.9 / Mavericks

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. 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. 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 is expected and desired, especially with devices that unlock features in non-free software.
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. 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.
Now, according to https://developer.apple.com/library/mac/technotes/tn2274/_index.html, 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. The device that isn't coming up correctly meets those criteria, so I wonder what else is missing.
Here's a dump:
Information for device Bar (VID=0x0f00 PID=0x0baa):
Connection Information:
Connection status: Device connected
Device actual bus speed: High
Device is hub: No
Device address: 0x0001
Current configuration value: 0x01
Number of open pipes: 5
Device Descriptor:
0x12    bLength
0x01    bDescriptorType
0x0200    bcdUSB
0xEF    bDeviceClass   (Miscellaneous device)
0x02    bDeviceSubClass
0x01    bDeviceProtocol
0x40    bMaxPacketSize0   (64 Bytes)
0x0f00    idVendor
0x0baa    idProduct
0x0010    bcdDevice
0x01    iManufacturer   "Foo"
0x03    iProduct   "Bar"
0x00    iSerialNumber
0x02    bNumConfigurations
Device Qualifier Descriptor:
0x0A    bLength
0x06    bDescriptorType
0x0200    bcdUSB
0x00    bDeviceClass
0x00    bDeviceSubClass
0x00    bDeviceProtocol
0x40    bMaxPacketSize0   (64 Bytes)
0x01    bNumConfigurations
0x00    bReserved
Configuration Descriptor:
0x09    bLength
0x02    bDescriptorType
0x0169    wTotalLength
0x05    bNumInterfaces
0x01    bConfigurationValue
0x00    iConfiguration
0x80    bmAttributes   (Bus-powered Device)
0xFA    bMaxPower   (500 mA)
Interface Association Descriptor:
0x08    bLength
0x0B    bDescriptorType
0x00    bFirstInterface
0x04    bInterfaceCount
0x01    bFunctionClass   (Audio Device Class)
0x00    bFunctionSubClass
0x20    bFunctionProtocol
0x00    iFunction
Interface Descriptor:
0x09    bLength
0x04    bDescriptorType
0x00    bInterfaceNumber
0x00    bAlternateSetting
0x00    bNumEndPoints
0x01    bInterfaceClass   (Audio Device Class)
0x01    bInterfaceSubClass   (Audio Control Interface)
0x20    bInterfaceProtocol
0x00    iInterface
AC Interface Header Descriptor:
0x09    bLength
0x24    bDescriptorType
0x01    bDescriptorSubtype
0x0200    bcdADC
0x08    bCategory
0x0087    wTotalLength
0x00    bmControls
AC Clock Source Descriptor:
0x08    bLength
0x24    bDescriptorType
0x0A    bDescriptorSubtype
0x29    bClockID
0x03    bmAttributes
0x07    bmControls
0x00    bAssocTerminal
0x0E    iClockSource   "Foo Internal Clock"
AC Clock Selector Descriptor:
0x08    bLength
0x24    bDescriptorType
0x0B    bDescriptorSubtype
0x28    bClockID
0x01    bNrInPins
0x29    baCSourceID(1)
0x03    bmControls
0x0D    iClockSelector   "Foo Clock Selector"
AC Input Terminal Descriptor:
0x11    bLength
0x24    bDescriptorType
0x02    bDescriptorSubtype
0x02    bTerminalID
0x0101    wTerminalType   (USB Streaming)
0x00    bAssocTerminal
0x28    bCSourceID
0x04    bNrChannels
0x00000000    bmChannelConfig
0x12    iChannelNames
0x00    bmControls
0x06    iTerminal   "Bar "
AC Feature Unit Descriptor:
0x1A    bLength
0x24    bDescriptorType
0x06    bDescriptorSubtype
0x0A    bUnitID
0x02    bSourceID
0x0000000F    bmaControls(0)
0x0000000F    bmaControls(1)
0x0000000F    bmaControls(2)
0x0000000F    bmaControls(3)
0x0000000F    bmaControls(4)
0x00    iFeature
AC Output Terminal Descriptor:
0x0C    bLength
0x24    bDescriptorType
0x03    bDescriptorSubtype
0x14    bTerminalID
0x0301    wTerminalType   (Speaker)
0x00    bAssocTerminal
0x0A    bSourceID
0x28    bCSourceID
0x0000    bmControls
0x00    iTerminal
AC Input Terminal Descriptor:
0x11    bLength
0x24    bDescriptorType
0x02    bDescriptorSubtype
0x01    bTerminalID
0x0201    wTerminalType   (Microphone)
0x00    bAssocTerminal
0x28    bCSourceID
0x04    bNrChannels
0x00000000    bmChannelConfig
0x16    iChannelNames
0x00    bmControls
0x00    iTerminal
AC Feature Unit Descriptor:
0x1A    bLength
0x24    bDescriptorType
0x06    bDescriptorSubtype
0x0B    bUnitID
0x01    bSourceID
0x0000000F    bmaControls(0)
0x0000000F    bmaControls(1)
0x0000000F    bmaControls(2)
0x0000000F    bmaControls(3)
0x0000000F    bmaControls(4)
0x00    iFeature
AC Output Terminal Descriptor:
0x0C    bLength
0x24    bDescriptorType
0x03    bDescriptorSubtype
0x16    bTerminalID
0x0101    wTerminalType   (USB Streaming)
0x00    bAssocTerminal
0x0B    bSourceID
0x28    bCSourceID
0x0000    bmControls
0x07    iTerminal   "Bar "
Interface Descriptor:
0x09    bLength
0x04    bDescriptorType
0x01    bInterfaceNumber
0x00    bAlternateSetting
0x00    bNumEndPoints
0x01    bInterfaceClass   (Audio Device Class)
0x02    bInterfaceSubClass   (Audio Streaming Interface)
0x20    bInterfaceProtocol
0x00    iInterface
Interface Descriptor:
0x09    bLength
0x04    bDescriptorType
0x01    bInterfaceNumber
0x01    bAlternateSetting
0x02    bNumEndPoints
0x01    bInterfaceClass   (Audio Device Class)
0x02    bInterfaceSubClass   (Audio Streaming Interface)
0x20    bInterfaceProtocol
0x00    iInterface
AS Interface Descriptor:
0x10    bLength
0x24    bDescriptorType
0x01    bDescriptorSubtype
0x02    bTerminalLink
0x00    bmControls
0x01    bFormatType
0x00000001    bmFormats
0x04    bNrChannels
0x00000000    bmChannelConfig
0x12    iChannelNames
AS Format Type 1 Descriptor:
0x06    bLength
0x24    bDescriptorType
0x02    bDescriptorSubtype
0x01    bFormatType
0x04    bSubslotSize
0x18    bBitResolution   (24 Bits/sample)
Endpoint Descriptor:
0x07    bLength
0x05    bDescriptorType
0x01    bEndpointAddress   (OUT Endpoint)
0x05    bmAttributes    (Transfer: Isochronous / Synch: Asynchronous / Usage: Data)
0x00D0    wMaxPacketSize   (208 Bytes)
0x01    bInterval
AS Isochronous Data Endpoint Descriptor:
0x08    bLength
0x25    bDescriptorType
0x01    bDescriptorSubtype
0x00    bmAttributes
0x00    bmControls
0x02    bLockDelayUnits   (Decoded PCM samples)
0x0008    wLockDelay
Endpoint Descriptor:
0x07    bLength
0x05    bDescriptorType
0x81    bEndpointAddress   (IN Endpoint)
0x11    bmAttributes    (Transfer: Isochronous / Synch: None / Usage: Feedback)
0x0004    wMaxPacketSize   (4 Bytes)
0x04    bInterval
Interface Descriptor:
0x09    bLength
0x04    bDescriptorType
0x02    bInterfaceNumber
0x00    bAlternateSetting
0x00    bNumEndPoints
0x01    bInterfaceClass   (Audio Device Class)
0x02    bInterfaceSubClass   (Audio Streaming Interface)
0x20    bInterfaceProtocol
0x00    iInterface
Interface Descriptor:
0x09    bLength
0x04    bDescriptorType
0x02    bInterfaceNumber
0x01    bAlternateSetting
0x01    bNumEndPoints
0x01    bInterfaceClass   (Audio Device Class)
0x02    bInterfaceSubClass   (Audio Streaming Interface)
0x20    bInterfaceProtocol
0x00    iInterface
AS Interface Descriptor:
0x10    bLength
0x24    bDescriptorType
0x01    bDescriptorSubtype
0x16    bTerminalLink
0x00    bmControls
0x01    bFormatType
0x00000001    bmFormats
0x04    bNrChannels
0x00000000    bmChannelConfig
0x16    iChannelNames
AS Format Type 1 Descriptor:
0x06    bLength
0x24    bDescriptorType
0x02    bDescriptorSubtype
0x01    bFormatType
0x04    bSubslotSize
0x18    bBitResolution   (24 Bits/sample)
Endpoint Descriptor:
0x07    bLength
0x05    bDescriptorType
0x82    bEndpointAddress   (IN Endpoint)
0x05    bmAttributes    (Transfer: Isochronous / Synch: Asynchronous / Usage: Data)
0x00D0    wMaxPacketSize   (208 Bytes)
0x01    bInterval
AS Isochronous Data Endpoint Descriptor:
0x08    bLength
0x25    bDescriptorType
0x01    bDescriptorSubtype
0x00    bmAttributes
0x00    bmControls
0x02    bLockDelayUnits   (Decoded PCM samples)
0x0008    wLockDelay
Interface Descriptor:
0x09    bLength
0x04    bDescriptorType
0x03    bInterfaceNumber
0x00    bAlternateSetting
0x02    bNumEndPoints
0x01    bInterfaceClass   (Audio Device Class)
0x03    bInterfaceSubClass   (MIDI Streaming Interface)
0x00    bInterfaceProtocol
0x00    iInterface
MS Interface Header Descriptor:
0x07    bLength
0x24    bDescriptorType
0x01    bDescriptorSubtype
0x0100    bcdMSC
0x0041    wTotalLength
MS MIDI IN Jack Descriptor:
0x06    bLength
0x24    bDescriptorType
0x02    bDescriptorSubtype
0x01    bJackType
0x01    bJackID
0x00    iJack
MS MIDI IN Jack Descriptor:
0x06    bLength
0x24    bDescriptorType
0x02    bDescriptorSubtype
0x02    bJackType
0x02    bJackID
0x00    iJack
MS MIDI OUT Jack Descriptor:
0x09    bLength
0x24    bDescriptorType
0x03    bDescriptorSubtype
0x01    bJackType
0x03    bJackID
0x01    bNrInputPins
0x02    baSourceID(1)
0x01    baSourcePin(1)
0x00    iJack
MS MIDI OUT Jack Descriptor:
0x09    bLength
0x24    bDescriptorType
0x03    bDescriptorSubtype
0x02    bJackType
0x04    bJackID
0x01    bNrInputPins
0x01    baSourceID(1)
0x01    baSourcePin(1)
0x00    iJack
Endpoint Descriptor (Audio/MIDI):
0x09    bLength
0x05    bDescriptorType
0x02    bEndpointAddress   (OUT Endpoint)
0x02    bmAttributes    (Transfer: Bulk / Synch: None / Usage: Data)
0x0200    wMaxPacketSize   (512 Bytes)
0x00    bInterval
0x00    bRefresh
0x00    bSynchAddress
MS Bulk Data Endpoint Descriptor:
0x05    bLength
0x25    bDescriptorType
0x01    bDescriptorSubtype
0x01    bNumEmbMIDIJack
0x01    baAssocJackID(1)
Endpoint Descriptor (Audio/MIDI):
0x09    bLength
0x05    bDescriptorType
0x83    bEndpointAddress   (IN Endpoint)
0x02    bmAttributes    (Transfer: Bulk / Synch: None / Usage: Data)
0x0200    wMaxPacketSize   (512 Bytes)
0x00    bInterval
0x00    bRefresh
0x00    bSynchAddress
MS Bulk Data Endpoint Descriptor:
0x05    bLength
0x25    bDescriptorType
0x01    bDescriptorSubtype
0x01    bNumEmbMIDIJack
0x03    baAssocJackID(1)
Interface Descriptor:
0x09    bLength
0x04    bDescriptorType
0x04    bInterfaceNumber
0x00    bAlternateSetting
0x00    bNumEndPoints
0xFE    bInterfaceClass   (Application Specific)
0x01    bInterfaceSubClass
0x01    bInterfaceProtocol
0x0F    iInterface   "Foo DFU"
Configuration Descriptor:
0x09    bLength
0x02    bDescriptorType
0x0169    wTotalLength
0x05    bNumInterfaces
0x01    bConfigurationValue
0x00    iConfiguration
0x80    bmAttributes   (Bus-powered Device)
0xFA    bMaxPower   (500 mA)
Interface Association Descriptor:
0x08    bLength
0x0B    bDescriptorType
0x00    bFirstInterface
0x04    bInterfaceCount
0x01    bFunctionClass   (Audio Device Class)
0x00    bFunctionSubClass
0x20    bFunctionProtocol
0x00    iFunction
Interface Descriptor:
0x09    bLength
0x04    bDescriptorType
0x00    bInterfaceNumber
0x00    bAlternateSetting
0x00    bNumEndPoints
0x01    bInterfaceClass   (Audio Device Class)
0x01    bInterfaceSubClass   (Audio Control Interface)
0x20    bInterfaceProtocol
0x00    iInterface
AC Interface Header Descriptor:
0x09    bLength
0x24    bDescriptorType
0x01    bDescriptorSubtype
0x0200    bcdADC
0x08    bCategory
0x0087    wTotalLength
0x00    bmControls
AC Clock Source Descriptor:
0x08    bLength
0x24    bDescriptorType
0x0A    bDescriptorSubtype
0x29    bClockID
0x03    bmAttributes
0x07    bmControls
0x00    bAssocTerminal
0x0E    iClockSource   "Foo Internal Clock"
AC Clock Selector Descriptor:
0x08    bLength
0x24    bDescriptorType
0x0B    bDescriptorSubtype
0x28    bClockID
0x01    bNrInPins
0x29    baCSourceID(1)
0x03    bmControls
0x0D    iClockSelector   "Foo Clock Selector"
AC Input Terminal Descriptor:
0x11    bLength
0x24    bDescriptorType
0x02    bDescriptorSubtype
0x02    bTerminalID
0x0101    wTerminalType   (USB Streaming)
0x00    bAssocTerminal
0x28    bCSourceID
0x04    bNrChannels
0x00000000    bmChannelConfig
0x12    iChannelNames
0x00    bmControls
0x06    iTerminal   "Bar "
AC Feature Unit Descriptor:
0x1A    bLength
0x24    bDescriptorType
0x06    bDescriptorSubtype
0x0A    bUnitID
0x02    bSourceID
0x0000000F    bmaControls(0)
0x0000000F    bmaControls(1)
0x0000000F    bmaControls(2)
0x0000000F    bmaControls(3)
0x0000000F    bmaControls(4)
0x00    iFeature
AC Output Terminal Descriptor:
0x0C    bLength
0x24    bDescriptorType
0x03    bDescriptorSubtype
0x14    bTerminalID
0x0301    wTerminalType   (Speaker)
0x00    bAssocTerminal
0x0A    bSourceID
0x28    bCSourceID
0x0000    bmControls
0x00    iTerminal
AC Input Terminal Descriptor:
0x11    bLength
0x24    bDescriptorType
0x02    bDescriptorSubtype
0x01    bTerminalID
0x0201    wTerminalType   (Microphone)
0x00    bAssocTerminal
0x28    bCSourceID
0x04    bNrChannels
0x00000000    bmChannelConfig
0x16    iChannelNames
0x00    bmControls
0x00    iTerminal
AC Feature Unit Descriptor:
0x1A    bLength
0x24    bDescriptorType
0x06    bDescriptorSubtype
0x0B    bUnitID
0x01    bSourceID
0x0000000F    bmaControls(0)
0x0000000F    bmaControls(1)
0x0000000F    bmaControls(2)
0x0000000F    bmaControls(3)
0x0000000F    bmaControls(4)
0x00    iFeature
AC Output Terminal Descriptor:
0x0C    bLength
0x24    bDescriptorType
0x03    bDescriptorSubtype
0x16    bTerminalID
0x0101    wTerminalType   (USB Streaming)
0x00    bAssocTerminal
0x0B    bSourceID
0x28    bCSourceID
0x0000    bmControls
0x07    iTerminal   "Bar "
Interface Descriptor:
0x09    bLength
0x04    bDescriptorType
0x01    bInterfaceNumber
0x00    bAlternateSetting
0x00    bNumEndPoints
0x01    bInterfaceClass   (Audio Device Class)
0x02    bInterfaceSubClass   (Audio Streaming Interface)
0x20    bInterfaceProtocol
0x00    iInterface
Interface Descriptor:
0x09    bLength
0x04    bDescriptorType
0x01    bInterfaceNumber
0x01    bAlternateSetting
0x02    bNumEndPoints
0x01    bInterfaceClass   (Audio Device Class)
0x02    bInterfaceSubClass   (Audio Streaming Interface)
0x20    bInterfaceProtocol
0x00    iInterface
AS Interface Descriptor:
0x10    bLength
0x24    bDescriptorType
0x01    bDescriptorSubtype
0x02    bTerminalLink
0x00    bmControls
0x01    bFormatType
0x00000001    bmFormats
0x04    bNrChannels
0x00000000    bmChannelConfig
0x12    iChannelNames
AS Format Type 1 Descriptor:
0x06    bLength
0x24    bDescriptorType
0x02    bDescriptorSubtype
0x01    bFormatType
0x04    bSubslotSize
0x18    bBitResolution   (24 Bits/sample)
Endpoint Descriptor:
0x07    bLength
0x05    bDescriptorType
0x01    bEndpointAddress   (OUT Endpoint)
0x05    bmAttributes    (Transfer: Isochronous / Synch: Asynchronous / Usage: Data)
0x00D0    wMaxPacketSize   (208 Bytes)
0x01    bInterval
AS Isochronous Data Endpoint Descriptor:
0x08    bLength
0x25    bDescriptorType
0x01    bDescriptorSubtype
0x00    bmAttributes
0x00    bmControls
0x02    bLockDelayUnits   (Decoded PCM samples)
0x0008    wLockDelay
Endpoint Descriptor:
0x07    bLength
0x05    bDescriptorType
0x81    bEndpointAddress   (IN Endpoint)
0x11    bmAttributes    (Transfer: Isochronous / Synch: None / Usage: Feedback)
0x0004    wMaxPacketSize   (4 Bytes)
0x04    bInterval
Interface Descriptor:
0x09    bLength
0x04    bDescriptorType
0x02    bInterfaceNumber
0x00    bAlternateSetting
0x00    bNumEndPoints
0x01    bInterfaceClass   (Audio Device Class)
0x02    bInterfaceSubClass   (Audio Streaming Interface)
0x20    bInterfaceProtocol
0x00    iInterface
Interface Descriptor:
0x09    bLength
0x04    bDescriptorType
0x02    bInterfaceNumber
0x01    bAlternateSetting
0x01    bNumEndPoints
0x01    bInterfaceClass   (Audio Device Class)
0x02    bInterfaceSubClass   (Audio Streaming Interface)
0x20    bInterfaceProtocol
0x00    iInterface
AS Interface Descriptor:
0x10    bLength
0x24    bDescriptorType
0x01    bDescriptorSubtype
0x16    bTerminalLink
0x00    bmControls
0x01    bFormatType
0x00000001    bmFormats
0x04    bNrChannels
0x00000000    bmChannelConfig
0x16    iChannelNames
AS Format Type 1 Descriptor:
0x06    bLength
0x24    bDescriptorType
0x02    bDescriptorSubtype
0x01    bFormatType
0x04    bSubslotSize
0x18    bBitResolution   (24 Bits/sample)
Endpoint Descriptor:
0x07    bLength
0x05    bDescriptorType
0x82    bEndpoin

Hi,
I have same issue with my device, but what's strange is that it's correctly detected under Yosemite but not under 10.9.4,
It's always detected as Generic Midi device under 10.9.4
Do you find the reason ?
Thx

Similar Messages

Where can I find the generic usb-midi driver?

Hello All,
I'm having trouble with logic recording any midi signal as having latency. This is not the usual buffer question as I'm not concerned about a laggy audio playback when I depress a midi key - I'm more concerned about having logic record what midi I play exactly when I play it.
In an effort to solve the issue, I thought I'd try to re-install the generic usb-midi drivers that come with osx, but I can't find them - can anyone point me in the right direction? Are there "better" drivers?
If you're interested in the original problem or think you might have a solution, the original thread is here:
http://discussions.apple.com/thread.jspa?threadID=2399493&tstart=0
Thanks,
mario

five fathom wrote:
How can this be normal? If logic can't track a midi performance accurately then that's a huge flaw... What are other artists doing to work around this? Mousing everything is not an attractive option.
MIDI is an old protocol, and not a very fast one.
Different audio devices and different audio device drivers take different amounts of time to process audio and bring it to the outputs, or to process audio that comes IN through the inputs and is recorded, resulting in different latency for different interfaces.
This is normal, and completely expected - once you've read up on the basics of computer-aided recording, which is why people are telling you to read up on "latency" in the Logic manual.
This is why Logic has come with latency adjustment for playback/recording and MIDI output (positive or negative) for years and years - another reason why people are telling you to read up on "latency" in the Logic manual.

Can any generic USB wireless device work on my Mac Mini?

I am needing to connect my computer to the internet and i was wondering if just any generic USB wireless device will be able to connect too my wireless router???
if not what would be my best bet?

It would not be accurate to say that any generic USB wifi adapter will work with MacOS because not all have suitable drivers. Some do, but I suspect the majority do not. Many of the adapters that exist will work with Windows however, if you have an Intel mini and run Parallels, Fusion or BootCamp, because the vast majority of drivers are written for Windows rather than MacOS.
However, there are some USB adapters that do work (http://www.engadget.com/2008/07/30/asus-usb-n11-wireless-n-usb-adapter-ships-wit h-ezlink/ for example). If you are considering such a device, ensure it has MacOS drivers either supplied or available for download, and specifically that the drivers are suited to the MacOS version you have.
Be aware that USB is probably the least reliable way to connect a system, so it shouldn't be regarded as a best possible network solution!

Usb midi devices do not appear on os10.4.10

i've seen some similar complaints about firewire audio devices, and usb harddrive on this forum;
i've got a a few usb midi devices (m-audio oxygen8 and edirol ua-25) that do not show up anywhere on my computer (black macbook, os 10.4.10); i've checked the audio midi setup area, and all of the various software preference areas (garageband, absynth, reaktor, etc).
the workarounds for the firewire audio don't look like the right thing to do. i've installed the v1.1 audio update. with no change in problem.
the edirol usb device is an audio and midi device; the audio works fine (before i did the 1.1 update, crossing fingers that it still works) but the midi does not appear to exist on my system.
i've updated the drivers from the respective hardware vendors, no luck. looked for similar issues in all the knowledgebases i could find. every answer tells me to do what i did the first time. so i do it again and it still doesn;t work.
has anyone else had this issue? or has anyone else had a positive experience with usb midi devices?
i've recently switched from pc to mac,
so i've some out of depth feeling on the details of mac fer sure.
thanks,
dylan

Oh my god. All I had to do was reboot. Marking as closed.

No more sound to USB midi device Alesis iMultimix8USB

Hello
After playing hours and days without any problems it's no longer possible to communicate with my Alesis midi device iMultimix8USB.
I did all the latest updates. I did on my macbook pro too and it the device is working there fine. So the device is ok and the problem must be with my macbook.
So before the problem I plugged out the USB-cable and the sound switched without any problems to the internal speakers. After plugging in the UBS-cable back the sound stayed on the internal speakers. I have no idea what is wrong now.
In the system profiler it shows under USB the "USB Audio CODEC" entry from my midi device. So that should be OK. But in the system settings "Sound" I cannot find the old entries for the device under "Output". Only the integrated speakers are listed.
So what is missing? Thanks for any advice.

Oh, I remembered some problems while starting with iMultimix8USB some years ago. There I had to install a "special" driver to make it running (http://discussions.apple.com/thread.jspa?threadID=1797831&tstart=0).
Now I followed the instructions to deinstall the Yahama-USB-Driver and now it works again!
I think, the involved kernel rebuilt has somehow brought back the official Apple driver which is working now with the iMultimix8USB. This was not the case some years ago. But anyway it works now.

USB midi device not showin up/installing

hello.
thanks in advance for anyone that can help me out here.
after many late nights trying to install the nana pad2 on my imac and failing...i've run out of ideas.
imac 27" OSX 10.7.5
2.8 core i5
12G ram.
i have the latest drivers (got them last night...again)
installed and re installed and manually deleted them and tried reinstalling several times.
no matter what i do the korg will not show up in
'UTILITIES' > Audio MIDI setup. nothing shows up in there other then my presonus audio interface.
i go into studio one and with the nano plugged in (via new usb cable) i can get midi "info" data to show up in the
'MIDI monitor' when hitting the pads...but no instruments are able to be triggered by the pad.
i've followed the install instruction for adding devices in studio one. but the main issue here is its not showing up at all in my imac "utilities".
i see some on the forums have got it working...but dont actually show or say how.
anyone out there conquered this??
thanks.
http://i1351.photobucket.com/albums/p797/sikapple/imac_nano2014-02-15at42643PM_z ps7cb1755d.png

this is what i was looking for.
if anyone else has this issue:
audio midi setup > preferences > open specific winows.
(korg midi device is still not working in daw though. )

USB MIDI devices not detected under OS 10.5.2

Leopard's Audio Midi Configuration doesn't detect my Korg microKontrol, Novation Remote Zero SL and my Evolution MK-249C2 MIDI keyboard. Firewire MIDI device is detected (RME fireface 800).
Using the "latest" drivers - Novation Automap Universal 2.0.1178 driver, microKontrol 1.0.7 driver, Evolution keyboard doesn't need a driver.
installed Leopard yesterday, but I think I'll switch back to Tiger...

USB Hub was faulty!

Garageband recognize USB MIDI device - Still will not play.

I am using the newest version of Garageband with Yamaha YPG 525 keyboard connected via USB as a MIDI controller. Drivers installed successfully. This is not my first Yamaha keyboard used with Garageband. This issue I'm having is that under System Preferences it shows the MIDI device connected but will not allow me to select as the "input" device. It shows up in the "Audio MIDI Setup" app, and I've selected the "Send All Notes On" under the Yamaha driver application listed in System preferences. It's getting very frustrating because clearly GB sees it's there but just refuses to make playing it an option. I have searched dozens of forums but cannot find someone having the same issue. Please help!

this is what i was looking for.
if anyone else has this issue:
audio midi setup > preferences > open specific winows.
(korg midi device is still not working in daw though. )

USB MIDI devices not detected (3 out of 4)

Leopard's Audio Midi Configuration doesn't detect the Korg microKontrol, Novation Remote Zero SL and Evolution MK-249C2 MIDI keyboard. Firewire MIDI device is detected (RME fireface 800).
Using the "latest" drivers - Novation Automap Universal 2.0.1178 driver, microKontrol driver is pre-Leopard, Evolution keyboard doesn't need a driver.

USB Hub was faulty!

USB MIDI device issues

My CLP-970A yamaha clavinova is not being picked up by garageband eventhough the UX16 USB device is recognized in the Audio MIDI setup window. I added the clavinova as a device and it tested "good".
I have a G5 iMac and run 10.3.9 the device manual says the UX16 supports OS X 10.1.2 through 10.2.6 so I looked on the Yamaha site. They have an update listed for OS X but there is no other information, no date created, or what the patch is intended to do etc.
Is this just a bad set up?
Does someone have a much easier and better solution to recording clavinova music in garageband? Suggestions, comments, please...Thanks!

I have tried software track and real instrument track.
A "Real" track will absolutely not work, MIDI is a software instrument.
You also didn't answer the first question I asked, does GB tell you a MIDI device is conected?
Is there a better interface
I can't speak for "better" but here are a few exmples of interfaces:
http://www.thehangtime.com/gb/gbfaq2.html#interfaces
Don't give up yet
--HangTime [Will Compute for Food] B-)>

UDev rules not working for MidiSport 2x2 usb midi device

I installed arch a couple of months ago and am loving it so far. Any problems I've had so far have already been solved in the forums, but this one's really got me. I have a MidiSport 2x2 that I want the firmware to be loaded on everytime I plug it in. I installed (there's not an arch package) a package that is supposed to do just that. (It's called midisport-firmware-1.2.tar.gz). However, the package seems to be out of date (2006) and I even had to modify a couple places in the configure script to get it to work with current program revisions. However, once installed, it does nothing. It installed firmware files and udev rules for the device into a couple of directories. When I run the command that is supposed to load the firmware, it works fine. But for some reason, (I even checked the udev kernel log) it's like the event isn't even being triggered. Here's part of the original file that came with the package that's supposed to load the firmware:
# midisport-firmware.rules - udev rules for loading firmware into MidiSport devices
# DEVPATH=="/*.0" selects interface 0 only
# (some udev versions don't work with SYSFS{bInterfaceNumber})
# MidiSport 2x2
ACTION=="add", SUBSYSTEM=="usb", DEVPATH=="/*.0", ENV{PRODUCT}=="763/1001/*", RUN+="/sbin/fxload -s /usr/local/share/usb/maudio/MidiSportLoader.ihx -I /usr/local/share/usb/maudio/MidiSport2x2.ihx"
# vim: ft=conf
And here's what I modified it to in an attempt to make it work:
# MidiSport 2x2
ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="0763", ATTR{idProduct}=="1001", RUN+="/sbin/fxload -D /dev/%k -s /usr/local/share/usb/maudio/MidiSportLoader.ihx -I /usr/local/share/usb/maudio/MidiSport2x2.ihx"
I would really appreciate help from anyone who knows about this kind of thing, as I can't figure out what's going wrong. If it's something wrong with the config, please let me know. Actually, some HAL events popped up when I was testing this out. Is it possible HAL is blocking the udev event somehow?

Hi,
The firmware files must be put in /lib/firmware so they can be found by the kernel. Are they being put there?

How to list all USB AUDIO DEVICES using PowerShell on Windows 7

Hi all,
I'm starting today on the powershell programming world, and my first task is list all USB Headsets plugged on my computer, I wanna get the name of this devices like is shown on Windows Volume Control.
My headset is a ZOX DH-60, every time that I change the USB port, the name changes, like Headset ZOX DH-60, then Headset 2 ZOX DH-60, how could I get this name using powershell ?
Thanks,
Best Regards
Leonardo Lima

Hi,
Nope... see my command and return
Get-WmiObject Win32_PnPEntity | ? {$_.Service -eq 'usbaudio'} | Select * | Format-List
__GENUS : 2
__CLASS : Win32_PnPEntity
__SUPERCLASS : CIM_LogicalDevice
__DYNASTY : CIM_ManagedSystemElement
__RELPATH : Win32_PnPEntity.DeviceID="USB\\VID_0D8C&PID_000E&MI_00\\8&149B33FB&0&0000"
__PROPERTY_COUNT : 24
__DERIVATION : {CIM_LogicalDevice, CIM_LogicalElement, CIM_ManagedSystemElement}
__SERVER : HOBBIT
__NAMESPACE : root\cimv2
__PATH : \\HOBBIT\root\cimv2:Win32_PnPEntity.DeviceID="USB\\VID_0D8C&PID_000E&MI_00\\8&149B33FB&0&0000"
Availability :
Caption : Generic USB Audio Device
ClassGuid : {4d36e96c-e325-11ce-bfc1-08002be10318}
CompatibleID : {USB\Class_01&SubClass_01&Prot_00, USB\Class_01&SubClass_01, USB\Class_01}
ConfigManagerErrorCode : 0
ConfigManagerUserConfig : False
CreationClassName : Win32_PnPEntity
Description : Dispositivo de áudio USB
DeviceID : USB\VID_0D8C&PID_000E&MI_00\8&149B33FB&0&0000
ErrorCleared :
ErrorDescription :
HardwareID : {USB\VID_0D8C&PID_000E&REV_0100&MI_00, USB\VID_0D8C&PID_000E&MI_00}
InstallDate :
LastErrorCode :
Manufacturer : (Áudio USB genérico)
Name : Generic USB Audio Device
PNPDeviceID : USB\VID_0D8C&PID_000E&MI_00\8&149B33FB&0&0000
PowerManagementCapabilities :
PowerManagementSupported :
Service : usbaudio
Status : OK
StatusInfo :
SystemCreationClassName : Win32_ComputerSystem
SystemName : HOBBIT
Scope : System.Management.ManagementScope
Path : \\HOBBIT\root\cimv2:Win32_PnPEntity.DeviceID="USB\\VID_0D8C&PID_000E&MI_00\\8&149B33FB&0&0000"
Options : System.Management.ObjectGetOptions
ClassPath : \\HOBBIT\root\cimv2:Win32_PnPEntity
Properties : {Availability, Caption, ClassGuid, CompatibleID...}
SystemProperties : {__GENUS, __CLASS, __SUPERCLASS, __DYNASTY...}
Qualifiers : {dynamic, Locale, provider, UUID}
Site :
Container :
__GENUS : 2
__CLASS : Win32_PnPEntity
__SUPERCLASS : CIM_LogicalDevice
__DYNASTY : CIM_ManagedSystemElement
__RELPATH : Win32_PnPEntity.DeviceID="USB\\VID_074D&PID_3556&MI_00\\8&285F78A6&0&0000"
__PROPERTY_COUNT : 24
__DERIVATION : {CIM_LogicalDevice, CIM_LogicalElement, CIM_ManagedSystemElement}
__SERVER : HOBBIT
__NAMESPACE : root\cimv2
__PATH : \\HOBBIT\root\cimv2:Win32_PnPEntity.DeviceID="USB\\VID_074D&PID_3556&MI_00\\8&285F78A6&0&0000"
Availability :
Caption : ZOX DH-60
ClassGuid : {4d36e96c-e325-11ce-bfc1-08002be10318}
CompatibleID : {USB\Class_01&SubClass_01&Prot_00, USB\Class_01&SubClass_01, USB\Class_01}
ConfigManagerErrorCode : 0
ConfigManagerUserConfig : False
CreationClassName : Win32_PnPEntity
Description : Dispositivo de áudio USB
DeviceID : USB\VID_074D&PID_3556&MI_00\8&285F78A6&0&0000
ErrorCleared :
ErrorDescription :
HardwareID : {USB\VID_074D&PID_3556&REV_0006&MI_00, USB\VID_074D&PID_3556&MI_00}
InstallDate :
LastErrorCode :
Manufacturer : (Áudio USB genérico)
Name : ZOX DH-60
PNPDeviceID : USB\VID_074D&PID_3556&MI_00\8&285F78A6&0&0000
PowerManagementCapabilities :
PowerManagementSupported :
Service : usbaudio
Status : OK
StatusInfo :
SystemCreationClassName : Win32_ComputerSystem
SystemName : HOBBIT
Scope : System.Management.ManagementScope
Path : \\HOBBIT\root\cimv2:Win32_PnPEntity.DeviceID="USB\\VID_074D&PID_3556&MI_00\\8&285F78A6&0&0000"
Options : System.Management.ObjectGetOptions
ClassPath : \\HOBBIT\root\cimv2:Win32_PnPEntity
Properties : {Availability, Caption, ClassGuid, CompatibleID...}
SystemProperties : {__GENUS, __CLASS, __SUPERCLASS, __DYNASTY...}
Qualifiers : {dynamic, Locale, provider, UUID}
Site :
Container :
__GENUS : 2
__CLASS : Win32_PnPEntity
__SUPERCLASS : CIM_LogicalDevice
__DYNASTY : CIM_ManagedSystemElement
__RELPATH : Win32_PnPEntity.DeviceID="USB\\VID_074D&PID_3556&MI_00\\8&3B19294B&0&0000"
__PROPERTY_COUNT : 24
__DERIVATION : {CIM_LogicalDevice, CIM_LogicalElement, CIM_ManagedSystemElement}
__SERVER : HOBBIT
__NAMESPACE : root\cimv2
__PATH : \\HOBBIT\root\cimv2:Win32_PnPEntity.DeviceID="USB\\VID_074D&PID_3556&MI_00\\8&3B19294B&0&0000"
Availability :
Caption : ZOX DH-60
ClassGuid : {4d36e96c-e325-11ce-bfc1-08002be10318}
CompatibleID : {USB\Class_01&SubClass_01&Prot_00, USB\Class_01&SubClass_01, USB\Class_01}
ConfigManagerErrorCode : 0
ConfigManagerUserConfig : False
CreationClassName : Win32_PnPEntity
Description : Dispositivo de áudio USB
DeviceID : USB\VID_074D&PID_3556&MI_00\8&3B19294B&0&0000
ErrorCleared :
ErrorDescription :
HardwareID : {USB\VID_074D&PID_3556&REV_0006&MI_00, USB\VID_074D&PID_3556&MI_00}
InstallDate :
LastErrorCode :
Manufacturer : (Áudio USB genérico)
Name : ZOX DH-60
PNPDeviceID : USB\VID_074D&PID_3556&MI_00\8&3B19294B&0&0000
PowerManagementCapabilities :
PowerManagementSupported :
Service : usbaudio
Status : OK
StatusInfo :
SystemCreationClassName : Win32_ComputerSystem
SystemName : HOBBIT
Scope : System.Management.ManagementScope
Path : \\HOBBIT\root\cimv2:Win32_PnPEntity.DeviceID="USB\\VID_074D&PID_3556&MI_00\\8&3B19294B&0&0000"
Options : System.Management.ObjectGetOptions
ClassPath : \\HOBBIT\root\cimv2:Win32_PnPEntity
Properties : {Availability, Caption, ClassGuid, CompatibleID...}
SystemProperties : {__GENUS, __CLASS, __SUPERCLASS, __DYNASTY...}
Qualifiers : {dynamic, Locale, provider, UUID}
Site :
Container :

Can't connect MIDI devices in Audio Midi Setup

In the help for Audio Midi Setup, step 7 says you can connect devices as follows:
"7. To specify the connection between MIDI devices, drag the output or input connectors above the device icon to the corresponding connector on the other device icon."
I can drag out a line from the device ports ("connectors"), but cannot find a way to make those lines "stick" to a second MIDI device or its ports -- i.e., I cannot connect devices like this at all.
Is this just me? Is this feature not yet implemented perhaps?
Thanks!

Ok, I finally solved this. For whatever reason, I could not set up connections between my auto-detected USB MIDI devices in Audio MIDI Setup -- maybe it is just not designed for this, or maybe I'm still not understanding what to do. i.e., I could not connect my E-MU 0404/USB to any port on my MOTU MIDI Express 128.
However, I was able to configure the individual MIDI interfaces (i.e. the E-MU or the MOTU, separately), using "Add Device" and then connecting between those interface devices and the newly added devices. This was the first time I had seen the "connectors" actually "take" and connect between entities within the Audio MIDI Setup utility, so that was a relief. Presumably doing this informs applications on the Mac how the MIDI system is set up -- I just thought it did more than that, i.e. allow direct routing between MIDI devices using just the utility itself.
I still don't know if I am meant to be able to connect a keyboard to a synth using just Audio MIDI Setup alone (what I had hoped), but I certainly can't seem to get that simple config to work and will have to resort to using some additional software like a sequencer. Not my preference, but c'est la vie.
Thanks for all the suggestions,
Stewart.

How to get bootcamp to install from USB on Mid 2010 Macbook Pro in Mavericks

Ok, finally ran into my first problem with Mavericks. It's a doozy. Please if anyone has any advice, let me know.
My bootcamp partition was acting a little buggy. I also wanted to make the partition larger, so I went ahead and erased it, made a larger partition and was getting ready to install windows 7.
Unfortunately, little to my knowledge, bootcamp assistant is programmed to not allow installation of Windows via USB if your computer had an optical drive in it's factory delivered form.
I have removed my optical drive in favor of a second hard drive and encased my original superdrive into an External USB hub.
There apparently used to be a solution involving editing the plist.info text document to allow USB installation. However, as of MAVERICKS, this document is now locked and unable to be edited.
I was running windows 7 fine until I scrapped it, and now I have no way to re-install windows short of going through a laborious process of re-installing my optical drive into my laptop, installing, and then re-installing my hard drive back in. The only reason is due to a software bias for my series of laptop because it "used to have" an optical drive.
Does anyone know of any way that I can bypass this issue to get Windows Re-installed to a bootcamp partition on a mid-2010 macbook pro without using the optical drive?
Thanks in advance!

Remove the Boot Camp partition only with Boot Camp Assistant, not with Disk Utility.
Install or Reinstall OS X from Scratch
Be sure you backup your files to an external drive or second internal drive because the following procedure will remove everything from the hard drive.
Boot to the Recovery HD:
Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
Erase the hard drive:
1. Select Disk Utility from the main menu and click on the Continue button.
2. After DU loads select your startup volume (usually Macintosh HD) from the
      left side list. Click on the Erase tab in the DU main window.
3. Set the format type to Mac OS Extended (Journaled.) Optionally, click on
      the Security button and set the Zero Data option to one-pass. Click on
      the Erase button and wait until the process has completed.
4. Quit DU and return to the main menu.
Reinstall OS X: Select Reinstall OS X and click on the Install button.
Note: You will need an active Internet connection. I suggest using Ethernet if possible
           because it is three times faster than wireless.

Macbook 2012 Mid: Can't mount USB mass storage after upgrading to Mavericks

Hi guys,
I'm having big problems with USB mass storages. After upgrading to Mavericks my Mac doesn't see some USB storage devices (mostly USB sticks and Android phone's memory cards via USB. My external USB 3.0 hard disks work fine) at all even though the devices themselves (for example my Android phone) are clearly recognized according to the System Report. When I plug them in, they don't show up on my Finder or on Disk Utility.
I've searched everywhere and it seems like some other people are having the same problem, none seems to offer a definite solution. I've even formatted my HD and reinstalled Mavericks from the recovery partition. Now it mounts a USB stick that was in one of the USB ports at the time of installation but still doesn't read anything else! The funny thing is when I boot into Windows 8 on my Boot Camp partition, I can mount any USB devices including the USB stick and the Android phone I'm having problems on Mavericks without any problems. I can even see then when I boot into the recovery so there's clearly something wrong with Mavericks.
Any chance someone has figured out a solution for this? Apple should've address this long time ago.

Please read this whole message before doing anything.
This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem. You must hold down the shift key twice: once when you turn on the computer, and again when you log in.
Note: If FileVault is enabled, or if a firmware password is set, or if the startup volume is a Fusion Drive or a software RAID, you can’t do this. Ask for further instructions.
Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.
The login screen appears even if you usually login automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
Test while in safe mode. Same problem? Note: If the devices are not in Mac OS X format, they normally won't mount in safe mode, but they should appear in Disk Utility.
After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of the test.

Generic "usb midi device" in 10.9 / Mavericks

Similar Messages

Maybe you are looking for