High Sierra 10.13.2 cannot find my audio device

I got the reply from Avid.

Thank you for contacting Avid.

Apologies for the late response as we're getting a volume of cases lately.

Here's a link regarding the Fast Track Pro and its latest drivers:

http://avid.force.com/pkb/articles/en_US/Download/Fast-Track-Pro-Drivers

Based on the link, the latest driver made for this hardware is only compatible until Mac OS X 10.10.1

Since you have updated your OS version to High Sierra, unfortunately, there are no drivers available for this OS version anymore.

Regards,

So I guess Avid will no longer support FastTrack Pro if you have macOS > 10.10.1.

Apple told me to downgrade to 10.13.1. Avid told me to downgrade to 10.10.1.

Add me to the list of people who find that the 10.13.4 update "fixed" the USB driver issue for my Fast Track Pro.

I use the Fast Track Pro interface when I DJ because it allows discreet audio pass-through to two separate output channels (R+L/1&2+3+4) from the digital mixing console on my laptop. In other words, I can send audio from each side of the mixer to different channels in my PA system. I don't use any of the other inputs (other than the USB interface with my MacBook Pro), so I can't speak to their function.

I also got the message in the sounds control panel that the Fast Track Pro has "no output options," but it works flawlessly again.

Have you tried re-setting the System Management Controller (SMC)?

See the Apple support documentation for this at: support.apple.com/en-us/HT201295

Basic steps are:

1. Shut the iMac down
2. Un-plug the power cord for at least 30 seconds
3. Restore power to your iMac (plug back in)
4. Start-up normally

This actually fixed a similar problem I had recently getting a new USB Audio adapter (mic + earphone) to work.

I wouldn't necessarily characterize this as a "High Sierra" issue, however.

Hope it works for you!

It stinks that M-Audio (or Avid) dropped support for this thing, but they did so years ago.

That said though, it had always worked just fine using Mac's class-compliant audio device drivers with no other drivers needed...until 10.13.2 broke it. I too can confirm that it worked in 10.13.1.

I bit the bullet and bought a Focusrite Scarlett 2i4 (which IS still supported by the manufacturer and i can confirm DOES work in 10.13.2). Apple's answer is everything has always been "Oh, we dropped support for that older thing, you need to buy the newer thing." ALWAYS. So don't hold out hope that Apple is going to "fix" this. They're not. If you need a working audio interface, start shopping.

This fix I posted about works and has been confirmed by several users:

Re: High Sierra 10.13.2 cannot find my audio device

Good news: 🙂🙂

Mac OS 10.13.4 beta version 2 seems to fix this issue so just hold out for a few weeks until the version is finalised and released to everyone or install the public beta, info on public beta available here: https://beta.apple.com/sp/betaprogram/

OK ... I share what I did to get the M-Track 2x2 recognized by my MacBook Pro 15 " mid-2012 - 2015. When I upgraded to High Sierra 10.13.5 the CoreAudio plugin was lost ... so looking in this forum I saw that I had to restart the sisatema, enter Terminal and add this command: " $ csrutil enable " and then install the M-Audio Drivers downloaded from its website.

So I did it, but it did not change anything ... I mention it because that's how I did it step by step.

But my curiosity told me to look in my system folders if I had the CoreAudio plugin installed where it should be ... and I discovered that when doing the update it was moved to the folder: Incompatible Software. So here I leave images of where I found it and where I placed it, then re-started the computer and everything is working as it should be.

You must move the CoreAudio Plugin as shown in the following image and re-start the computer and work with your M-Track 2x2 as it should be.

I hope it works for them as it does for me.

I've contacted Apple support. The only solution they gave me is to help me make an image to downgrade to 10.13.1. So don't hold your breath for a future update putting back support for this device...

try opening up ur system preferences then security and privacy then go to general and you should see an allow button near the allow apps n press that.

I've tried the beta update and it does solve the problem!

The fast track pro shows up again. Make sure to do a back up with time machine before installing, just in case

Thanks guys! :-)

Atualize o High Sierra (10.13.4) e os últimos drivers da FastTrackPro e ... funciona novamente.

q2800m wrote:

i dont think so because it worked fine with versions 10.13 and 10.13.1

Happy accident I would say. From Avid's site.

Mac Releases (click on a version # to download that installer)

1.9.5

• Dec 16, 2014
• This is the final driver release for the Fast Track Pro
• Qualified with Mac OS X 10.8.5, 10.9.5, 10.10, 10.10.1
• Note that Mac OS X 10.11 El Capitan (or later) is not compatible and will not be qualified
• Tested with Avid-qualified Apple computers (details)
• Core 2 Duo Mac users read this

As you can see, they haven't updated the drivers in just over 3 years.

Just solved this problem for my DAC !!! Perhaps not related however my DAC from Schiit Modi 2 just stopped being recognised after the 10.13.2 upgrade.

Here is how it solved - I literally switched the Modi 2 DAC OFF from the back i.e. the metal on and off switch next to where the USB cable goes in to the DAC. BOOM - It just showed up in "Sounds" in the OSX preferences and works now! 🙂

Note - I did change USB port it was plugged into in my iMac this morning and restarted. I wonder if that helped - not sure. It definitely didn't work UNTIL I switched it off and back on... I know it sounds pretty ridiculous, but I always kept my DAC ON in terms of power. So removing USB cables + restarting the iMac + different ports didn't do anything - switching the DAC itself, on / off ...just worked! No restart required....hope this helps!

Jeez, fine. How about "Apple changed the way that macOS manages class-compliant (no-driver-needed) devices, and as a result of that change, a device that many people own that used to work no longer does."

I'm not sure what your point is in arguing the semantics of this is. Yes, M-Audio dropped support for it. That stinks, but everyone already knows this. But in THIS case: The devices used to work until Apple's latest update to macOS caused it to stop working. Don't over-complicate this. Regardless, the result is the same: nobody is going to "fix" this, meaning everyone's two choices are: don't update past or rollback to 10.13.1, or buy a new audio interface.