Q: El Capitan USB audio problems.

I have had this problem for YEARS, with my old iMac and with my new 2015 iMac.

Spotify + Peachtree audio randomly drops out.

At this point it people should be getting fired at Apple for leaving this kind of issue in the OS for this long.  It is a beyond a joke.  I have tried everything and spending $3000+ on a computer then realising it can't perform a simple task like playing music on an external DAC is just shocking.

fugazied wrote:

 

At this point it people should be getting fired at Apple for leaving this kind of issue in the OS for this long.

http://www.apple.com/feedback/

I agree. The iPhone company (formerly known as the company that cared about computing) has terrible build quality with its OS compared to previous times.

Freeze the feature build and show you can build a rock-solid OS (again) before adding gunk such as SIRI (rumoured for 10.12) and other toys.

Plugging in a USB audio device (in my case Yellowtec PUC device) shouldn't be a big deal. Yet El Capitain seems to make it so.

Mar 27 19:01:39 woof system_profiler[1052]: SPUSBDevice: IOServiceGetMatchingService did not return anything for location 0x00300000

Mar 27 19:01:40 woof system_profiler[1054]: SPUSBDevice: IOServiceGetMatchingService did not return anything for location 0x00300000

Mar 27 19:01:42 woof system_profiler[1056]: SPUSBDevice: IOServiceGetMatchingService did not return anything for location 0x00300000

Remove device, the system.log calms down. Plug it back in and the log fills up with several entries a second.

Switch ports to even the motherboard's own..

Mar 27 19:05:27 woof system_profiler[1368]: SPUSBDevice: IOServiceGetMatchingService did not return anything for location 0x00314000

Mar 27 19:05:27 woof system_profiler[1368]: SPUSBDevice: IOServiceGetMatchingService did not return anything for location 0x00310000

Mar 27 19:05:27 woof system_profiler[1368]: SPUSBDevice: IOServiceGetMatchingService did not return anything for location 0x00322000

Mar 27 19:05:27 woof system_profiler[1368]: SPUSBDevice: IOServiceGetMatchingService did not return anything for location 0x00320000

Mar 27 19:05:27 woof system_profiler[1368]: SPUSBDevice: IOServiceGetMatchingService did not return anything for location 0x00340000

I'm using 12" New Macbook and have few USB DAC/AMP (Fulla Schiit, MIYO, Encore mDSD). My Fulla Schiit never had problem on any version of El Captain. MIYO got issues on all version, even 10.11.4. I though it was MIYO problem as manufacturer guess it draws too much power from Macbook and OSX shut it down. After this, I bought a new Encore mDSD which reached me two weeks ago and was having distortion problem after 30~45mins listening on 10.11.3. In first hour of listening session after upgraded to 10.11.4, the distortion problem seems resolved. Will test it for longer later. However, I like the sound of MIYO the most. How Apple can help?!

Your not alone. A lot of people are still having serious problems. I for one have distortion issues on my inputs that is just randomly triggered. Just recently upgraded to El Capitan and what a huge disappointment this experience have been so far. So stupid of me thinking that El Capitan would be stable by now.

Can you test TRAKTOR PRO 2.10.2 update which is released yesterday.

In another discussion, one user reported that is solved his issue, even there is no fix mentioned in the changelog.

Did the El Capitan 10.11.4 update fix any of the problems I've been reading about on this thread?

The only issue I was having was with my MOTU 828 mk3, having to remove the USB cable and plug it back in before it would be recognized. Also some issues with the iConnectMIDI4 that could have been related.

Both seem to be resolved now.

FWIW I must say I am very surprised Apple let this one go for so long. Even if it was an issue deep within the new OS that crippled parts of Core Audio it should still have been resolved much sooner. Steve Jobs spent a couple of decades nurturing a relationship with the arts community, especially musicians, and to blow it all over some inane USB connection issue is beyond me.

Sorry @paulclark, I don't think that it has.

I just update (foolishly) to 10.11.4 this morning and now the problem seems eternal. I'm running a Macbook Air and trying to use the Bose Companion 5's and cannot get them to work no matter what I try. Unplug and re-plug in the other USB port used to work but not any longer. I've tried all the tricks that I know and I cannot get the audio to come out of them.

When I enter Audio Midi application, and select the "Bose USB Audio" option, then select the "output" tab->configure speakers, I'm able to hear audio come out of them - it's the test "buzzing" sound that shows the channels are functioning. So it seems that the signal is reaching them but for some reason... heck, this is a pain in the neck.

If anyone has any brilliant ideas on how to fix this at Apple I'd love to hear them.

Rob

HOLD ON>>> I just was fooling around inside of the "Audio Devices" section of the Audio Midi application and before to switch to other output sources all that I did was double-click on the desired output. It hasn't seemed to have any effect.

I decided to look under the "gear" at the bottom of the section which lists possible devices (Built-in Microphone, Built-in Output, Display Audio, Bose USB Audio) and noticed that there is an option labeled "Use this device for sound output" which wasn't "greyed out" and was selectable.

With the "Bose USB Audio" selected, I chose this option and it works!! What the...??? I'm glad that it is but that's a rather strange way to get it to do so. Hope that helps others!

For me all issues finally seem to have been fixed. The Digihub USB chip works again too.

This has been quite a lasting annoying experience. The discussion seems to have a new branch, but I am unable to get access to it.

which step exactly seems to solve your problem?

With respect to the Bose speakers I can confirm they are working with 10.11.4 but only if plugged directly into the host system. If a hub is used the speakers are disconnected worse than any version prior than 10.11.4.

By reconfiguring USB connections I was able to plug the Bose speakers directly into the Mac, thus avoiding the ongoing Apple 10.11 USB driver problems. That said a new issue is that waking the system from sleep with a Apple USB keyboard is not reliable. It is better plugging directly plugged into the Mac, but still an issue. This means that on my Mac Pro two of the three rear ports are dedicated to the speakers and keyboard leaving the third port to support a the remaining USB2 connections.

Notable is that I tried two different USB3 add-in cards (e.g. additional native ports w/o adding a hub) but both jammed the Apple mouse's Bluetooth signal when anything is plugged into the USB3 card (e.g. not just a hard drive). This latter issue is not really an Apple problem, though the Mac Pro's WiFI and Bluetooth antenna is in an absurd location for good propagation. I consider USB3 to be a failed specification given the choice of the clocking frequency, even with spread spectrum spreading to minimize desensitizing local WiFi / Bluetooth receivers. Thus USB3 is only truly useful when local wireless devices are not present.

Hey all. Joining in with major complaints as to what El Capitan has done to my setup. I'm running a 2009 imac with the Apogee One for iPad & Mac.

Similar issues. Crashes all audio from sleep, often drops out during usage. Lots of clicks and pops when listening back with Logic Pro or Final Cut Pro.

I have one thing that my quick skimming of the previous posts has not turned up. I contacted Apogee and they said uninstalling and reinstalling the software would correct the problem and after doing that it ran flawlessly for a week before it went back to the crashing all the audio.

Also, when Apogee is disconnected after the crash I can then open the sound prefs pane with no problem. If I leave the Sound pane open and RECONNECT the Apogee it comes up as a device but is labeled "unknown"

Not sure any of that tells us anything relevant, but …

This is extremely frustrating to say the least.

It is very frustrating.

My console log is full of scrap about USB device errors. UNPLUG the Yellowtec and the console quietens down. Plug it back in and it fills with things like this:

pr 26 00:00:10 woof system_profiler[63127]: SPUSBDevice: IOServiceGetMatchingService did not return anything for location 0x00314000

Apr 26 00:00:10 woof system_profiler[63127]: SPUSBDevice: IOServiceGetMatchingService did not return anything for location 0x00310000

Apr 26 00:00:10 woof system_profiler[63127]: SPUSBDevice: IOServiceGetMatchingService did not return anything for location 0x00322000

Apr 26 00:00:10 woof system_profiler[63127]: SPUSBDevice: IOServiceGetMatchingService did not return anything for location 0x00320000

Apr 26 00:00:10 woof system_profiler[63127]: SPUSBDevice: IOServiceGetMatchingService did not return anything for location 0x00340000

Apr 26 00:00:10 woof system_profiler[63127]: SPUSBDevice: IOServiceGetMatchingService did not return anything for location 0x00300000

Apr 26 00:00:10 woof system_profiler[63127]: SPUSBDevice: IOServiceGetMatchingService did not return anything for location 0x00400000

Now, you do get to use the device, yet randomly the sound corrupts and sounds like a high-speed tape dubbing or crackling. Stop playback. Replug and it goes away for a while.

What a joke Apple is turning out to be with their QA. The last few years has been terrible. Mind you, they have time and resources to add a new feature to the telephone or to add SIRI to the OS. How about making the darn basics work first?

A little further info for everyone here. I also happen to own a ZOOM H6 for field recording and it has a USB connection option. This last time my Apogee One crashed I unplugged it and immediately plugged my H6 in without restarting or otherwise trying to address the crash.

Sound prefs pane opened without incident and the H6 is working perfectly so far.

So I guess it's not all USB audio devices?

I'll update if anything changes.

Has anyone registered this bug since the lastest version of Mac OS was released? If not:

http://bugreport.apple.com/