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-)>
Similar Messages
-
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 bEndpoinHi,
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 -
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,
dylanOh my god. All I had to do was reboot. Marking as closed.
-
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.pngthis 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. ) -
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. ) -
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 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!
-
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!
-
Connecting an external Midi device issues
Hi,
I bought a Yamaha ES synth.. can someone help me configure Logic so that I can hear what I am doing during playback...Is setting up a MIDI device THAT hard?
What are the options for me woth an external synth? Do I have to plug it in as audio? Id like to run it like a software instrument..
ANyone use external synths here?To hear audio you have to connect the Motif audio out into your Audio interface, until you decide to buy the Yamaha Firewire card for the Motif.
cheers
rob -
MacBook Pro USB Audio Device Issues
Hello,
I am currently using a MacBook Pro 2012 model and I am having trouble with connecting an audio import source via USB cable. The device I am trying to connect is a pair of Astro A40 headset with the MixAmp. According to various sources, the amp needs to be plugged in into a USB port. I have seen this done and when they go to System Preferences > Sound the device is shown. Unfortunately, I follow the same procedure as the one found on various sites and my computer is not recognizing that anything has been plugged in. I have tried both USB ports and nothing seems to be working.
Anyone ever hear anything about the newest model of MacBook having troubles with detecting audio devices via USB ports? Any help would be greatly appreciated.
Thanks,
MichaelSo far as the Go Pro connectivity, it was an issue on the Go Pro end. In order for the Go Pro to be found, I needed to remove all accesories. iPhoto still does not pick it up, although Finder did.
Flash Drives still not found.
Odd as I remember I used to be able to just plug in a device that had anything to do with pictures or videos and iPhoto would just automatically detect it and ask to import. -
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? -
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. -
Mid 2010 Macbook Pro - USB & Midi Issues
It all started when I recently bought a Pioneer DJM-900srt and switch from Traktor to Serato Dj. Now, I have been using my current Korg Nanocontrol for about 2 years problem free using manly Ableton Live 8 and Traktor Pro 2. Never needing to download any drivers and/or control editors. Fast forward to recently. Unknown to me at the time Serato Dj had some known issues with Midi mapping (that i should of researched more) but I went ahead and downloaded the latest Korn Nancontrol driver and control editor. Thinking 1) It might solve my Serato Dj problem and 2) what could it hurt? The second turned to be a nightmare.
So before I downloaded the driver and control editor I could plug in and unplug any of my midi usb devices, audio interfaces and Dj mixer in no specific order and at anytime and every thing would work and midi map as it was meant to. However, after downloading the driver all **** broke loose. While the driver was on my laptop none of my listed midi devices would connect properly and half the time the program would fail or just not open. I know you're not Allen & Heath but I also tried to download the latest driver from their website for my non working Xone 1D; Ableton, Serato Dj and Audio/Midi setup in utilities just will not open so i cant even tell if the midi devices are functioning properly. So I went on and deleted the Korg driver, editor and the Xone 1D driver.
After deleting the drivers and Korg control editor things now somewhat work but far from how they should. In order for things to function somewhat properly I must turn on the devices in this exact order. Turn on the computer and let it fully boot up. Plug in via USB to my laptop and turn on the Djm-900srt. Plug in my USB 7 port extender (with power supply) plug in my Korg Nano and my Maschine Mikro into the extender and turn it on. Boot up Ableton to quickly check if the devices mounted properly. Open up either Traktor or Serato and rock the house. The Allen & Heath Xone 1D has been dead in the water since the initial Korg Driver instal.
I can get screen shots of anything if it will help after work today. Around 5pm CST
Detailed specs:
Computer-
Model Name: MacBook Pro
Model Identifier: MacBookPro6,1
Processor Name: Intel Core i7
Processor Speed: 2.66 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache (per core): 256 KB
L3 Cache: 4 MB
Memory: 4 GB
Dj Gear-
Mixer - Djm-900srt
Midi Devices - Korg Nanokontrol 1st gen, Maschine Mikro 1st gen, Allen & Heath Xone 1D
P.S. Any new USB device will not function or be recognized.Please help. I have racked my brain and I still can't figure out how to fix this. I cannot believe that 1 korg driver download permanently ruined my computer. I swear to everything holy that my computer was running like a well oiled machine before the download and Korg has been little to no help.
-
My 2007 Macbook pro Intel Core 2 Duo Processor Speed 2.33 GHz has power issues with one or some of my USB powered devices. Last night I could not back up my Lacie external drives with software SuperDuper, hard drive copier. I also had a message that Time machine failed. I have two powered 12V USB
routers that are plugged into a 550VA CyberPower surge protector. I often receive these insufficient USB power for devices messages a dozen times even when I do not have devices like camera, Ipad, Ipod, and Tascam digital audio recorder plugged in. Is there a way to troubleshoot these USB routers or should I consider that one of the routers may be defective and replace them?
DavidMy 2007 Macbook pro Intel Core 2 Duo Processor Speed 2.33 GHz has power issues with one or some of my USB powered devices. Last night I could not back up my Lacie external drives with software SuperDuper, hard drive copier. I also had a message that Time machine failed. I have two powered 12V USB
routers that are plugged into a 550VA CyberPower surge protector. I often receive these insufficient USB power for devices messages a dozen times even when I do not have devices like camera, Ipad, Ipod, and Tascam digital audio recorder plugged in. Is there a way to troubleshoot these USB routers or should I consider that one of the routers may be defective and replace them?
David -
Still having Problems with yamaha USB UX16 midi device can anyone help??
I have setup drivers on my computer which have installed successfully. In logic I have setup environment so Physical input sequenser and keyboard are all connected up in Click and Ports layer.
When I am trying to play keyboard I still have no input or outport signal in transport window I am stuck on what to do??
please can someone help???I take back all I said. After reading reviews of this product, take it back to wherever you bought it and buy something else, anything else, everyone hates this thing, and is having problems with it. get a midisport instead.
http://www.midiman.com/index.php?do=products.list&ID=usbmidiinterfaces
here are a couple of reviews:
Dec 12, 2006 - It is hit or miss as far as compatability goes and you don't know until it is too late if the full instruction set is going to be sent/recieved intact. Tried it on various Macs, PCs and inconsistent in every situation. Yamaha needs to issue a full recall on this POC called the UX-16.
Nov 6, 2004 - The first Yamaha UX 16 that I bought worked okay for a day, then started to cause a buzzing noise. The next day, it was not recognized at all by my laptop. I returned it to the retailer, hoping to find a competitive portable USB/MIDI interface at another store. After failing to find an alternative at the other store, I bought the Yamaha UX16 again, hoping that the first dud was a fluke.
The second UX16 also worked for one day before giving out.
Avoid the UX16.
Apr 12, 2004 - This thing only works for a short period of time then quits being detectable to windows for random periods of time. Totally unreliable.
Maybe you are looking for
-
Need support to develop a Web Application-T Shirt Designer
Hello Everyone I am new here. So a big hello to all of you. Well, I am writing here because I urgently need an expert opinion on the matter mentioned below. And I would be glad if I could receieve some professional advice on this forum. I have to cre
-
Is there anyway to have policies applied to the computer while connected to domain and once the user disconnects (ie go home) all the policies go back the way they were. for example CD ROM and usb are disabled in domain but once the user is out of co
-
Which iPad works best with a keynote presentation on a projector? Thanks!
-
My first time to post a note. For several years I have selected to burn DVD to a folder. From there I burn it to a DVD. I have reinstall premiere 12 now several times. I select to burn to a folder and it seems to go through all the stages. Howeve
-
Portal Header details to be added
Hi, In the SAP GUI, in a report program, I'm creating a URL by calling the function module CALL_BROWSER. I'm calling the report program in Portals. In the report program, when I call the URL, the URL should appear with Portal header details. When the