El Capitan USB audio problems.

I have the same DAC. When I have it connected to my Macbook Pro, not only do I get no sound, but media won't play at all. Not from the Finder, or iTunes, or the Web. I get a beachball in whatever media I am trying to play. Tried changing multiple settings, resetting PRAM, restarting, selecting different USB ports etc... No dice.

I change from the NuForce to the internal speakers or headphone output and everything is fine.

Everything worked perfectly in Yosemite.

Try MIDI settings again.

Mark usb audio setting

You may need to change the hz settings from original 38xxxxx to 19xxxx since upgrading may revert to original settings.

Hello, I'm having the same problem with a set of Bose Companion 5 speakers. Worked perfectly in Yosemite. Now with El Capitan, if I don't play audio for a while, pause a video, or switch tracks, the sound will be routed to the internal speakers of my MacBook Pro. I have to go into the audio preferences, select the internal speakers and then the Bose to get them working again.

Just checked the Hz settings, and I only have one option available (48000.0 Hz).

Same problem for me and Nuforce uDAC 2. When I connected it was recognized but connects/disconnects every 1s.

Same with uDAC 2. It'l connect, burp, and go back to Internal Speakers on my 27" late 2014 iMac retina. It keeps trying, but can't hold on and just hiccups the music before returning to the speakers.

Also, Mac will not boot with it plugged in it seems, hangs about midway through progress bar. Unplug, good to go on boot.

Two different audio DACs, don't work. Worked fine under Yosemite. Even worse, the headphone audio out on my MBP early 2011 is silent too. It would be so nice if they can fix this soon.

Same problem with my Late 2012 Mac mini with Teac A-H01 DAC

Has anyone else noticed if their USB driver is now listed under the 3.0 bus? The Teac DAC is a USB 2.0 device.

I'm having the same issue here using a ZOOM R16 and PreSonus Studio Monitors not working with El Cap. They appear in Settings and worked perfectly before. Definitely wouldn't have "upgraded" if I'd known it would kill my being able to listen to well, anything.

Anyone know of a workaround that doesn't involve reinstalling Yosemite?

Well when you are adventurous you could turn of the system integrity protection temporarily and install Yosemite drivers manually. Would be nice to see what happens. Nothing will explode, but make sure you have a proper back up of your data in case your system refuses to boot and you have to reinstall.

In Linux by the way this is a very normal action to do, although you have more recovery options there.

Lots of information about how to deal with OSX-drivers can be found on the net by people who try to install OSX on non Apple hardware - what they call a H ackintosh. Google on that specific term. Reading their knowledge and using it on a Mac is not against any license.

Otherwise wait and pray.

Same here, Nuforce Udac, worked fine under Yosemite now can't use it. Come on apple.

Well, add me to the list of Nuforce uDAC users having problems. 😟

The audio should have been tested! Jobs would never have let this happen. Have you any idea how many people around the world that you've hurt with this move? I work exclusively from my Macbook Pro designing online learning modules. You just cost me many days income scrambling to fire up my old PC Laptop. You should have warned us that Screencast would not work, that Techsmith Snagit and Camtasia would not work, or audio Hijack, Piezo and others. You really annoy me. Fire the guy responsible for this mess and never do it again.

The 3.0 usb is allegedly backward compatible with 2.0

Not sure if it's this problem or just got myself in a state. iTunes plays for a bit through my Rane Sixty Two, then craps out, and no longer plays audio, neither through the mixer nor through the internal speakers.

I just listened to a recent Accidental Tech Podcast. Marco Arment says he's not updating to El Capitan because the ongoing USB audio issues. He's an audiophile, so this isn't surprising.

Wish I had heard about this bug before I updated.