Massive problem with audio interface

Hi guys,

I have the same problem. Just got the new Imac 27" haswell I7 16GB ram and fusion drive, running Mavericks. I got the POD UX2 installed all on the new Imac and nothing but problems. Just tried installing everything on my older macbook pro running on Mavericks and no problem at all.. This bothers me becuase I got the new Imac basically to record and produce music, I will get in touch with apple support and see what kind of solution they can provide with. Just wanted to post a comment as it is defenitely not Mavericks.

Just an FYI. Line 6 is collecting information on this. They know about the problem. You may want to call them as well to give them some additional data.

Good luck.

Exact same issues again... late 2013 iMac, fusion drive although some reports of this happening on late 2013 models regardless of drive type. Very frustrating - not even sure if apple is acknowleding the issue.

just came of the phone with apple support, tried a lot of things but no improvement. They have been very helpfull really, they are going to escalte this and discuss it with an apple engineer. Hopefully I will know more in a couple of days. Will come back if any news.

Jonnky K Did the fix you described work? with the partitions?

YES theryanpaul. I'm able to work right now.

I just finished a project in Reason today using my Firewire only MOTU Ultralite mk3.

I have a brand new 27' Haswell iMac with a 3TB Fusion Drive.

On the partitioin that has the SSD, I cannot get my audio interface to work.

On the partition without the SSD, everything works fine.

Hope this helps everyone until there's a fix. The problem is not thunderbolt or mavericks. It is FUSION DRIVE.

Here's my previous insructions on what has worked for me:

"1. Go to Disk Utility and Partition your drive. (IT TAKES A LONG TIME. JUST WAIT)

2. Install Mavericks on the Partition.

3. Transfer the information from your existing HD to the new partition.

4. Everything related to audio works again, but now you have no benefit of the solid state drive.

The solid state/HD connection only applies to the "main" partition.

If you switch away from it, you get none of the benefits and none of the problems."

2013 iMac 1TB Flash Drive

OS 10.8.5

Constant audio drop outs using Apogee Duet. I have to unplug and replug several times to get the system to recognize it. Sometimes when it is connected, Audio Prefs doesn't even recognize it and it shows up as "Unknown". When I click Audio Prefs before I get in, I get the spinning beachball and it takes a while for it to open. I have been in touch with Apogee but to no avail. It seems to work on my 2013 Macbook Pro, but I haven't tested extensively. It seems to get tripped up if I'm working in Ableton and get a Facetime call or if I try to use Youtube / Soundcloud. The system gets noticebly slower. When I switch back to Ableton, Duet is recognized (sometimes not recognized at all) but I cannot play anything inside the project window.

Not sure what to do at this point 😐

WORK AROUND:

So far it's working.

SEND EVERYTHING THROUGH SOUNDFLOWER

So far so good, will run some audio whilst I go out and see if it's still good when I get back... if it works I think I'm going to have to propose to you.

I spoke too soon, back to distortion. Infact it's made it worse... before if I just swapped back to standard audio output and then back to my soundcard it would temp fix it... now the distortion stays

Sorry : (

It's still working for me. However, I only had repeated sound dropouts. My comp still doesn't recognize Duet in sound prefs, but it still works when routed through Soundflower. Not sure why that is because it makes no sense.

I too am having this same issue on my new iMac 2013 3 TB fusion drive and mbox pro 3 connected via FireWire 400 to a FireWire 800 adapter to a 800 to Thunderbolt adapter. The audio keeps dropping out from a few seconds to a few minutes consistently. My imac came running Mountain Lion and I experienced a few pops and clicks, it was ultimately ignorable but there was also increased latency with real instrument recording. After testing the mavericks drivers for the mbox pro with my old MacBook Pro with no issues, I upgraded my iMac. The clicks and pops are gone, but the audio now drops out.

Have yet to try the prevent nap app fix, but will do so tmw, will also call apple and avid to see what they can do for me. I have read about others without fusion drives having issues too.

Hi, I am having problems as well. New late 2013 27" Imac I7 16GB Ram 1TB Fusion Drive. Huge latency issues and distortion in sound while I try to record guitar using POD UX2 LINE 6 interface. Spoke with apple care and tried mutliple things and nothing helped. They are looking into this with an engineer and are suposed to get back to me. I see many people are having very similar problems and all are running mavericks (as do I) and have the Fusiom Drive. I installed the interface on my 2010 MacBook Pro running mavericks and no problem at all, at least nothing I could really hear. Latency not an issue at all on the MBP. One of the things I start to heavily doubt is the USB 2.0 vs USB 3.0. The interface is 2.0 and Imac 3.0 (2.0 compatible). I have seen comments from people running on a USB hub and it helped them but comments where also if you didnt have the FD. I now here also see people that have their interface via FireWire Thunderbolt so that makes me believe it has not got to do with USB 2.0/3.0?? It is driving me mad.

Same problem here, i own a Allen & Heath ZED 12FX and a MacBookPro 9,2 with a normal SSD. Cracks and noise right from the start in Cubase. Music played from itunes, internet, etc is working fine. Apple please resolve this bug. I think the problem is in the USB Audio Codec.

Update: Tried the prevent app nap solution with no luck. Am currently downgrading my iMac back to mountain lion with internet recovery so it's more usable, but call apple after it's finished to see if they can help at all. It seems like there's an issue with the way that external audio interfaces, or anything that replaces the internal audio is dealt with internally. A fix for this will likely be in a future firmware update, and who knows when that'll come.