High Sierra 10.13.2 cannot find my audio device

I have the same problem with my (just bought) M-Audio Keystation mini 32. The driver for this keyboard should automatically be updated when you'll download the latest version of MacOS. But since MacOS 10.13.2 this keyboard doesn't work anymore. It recognises the keyboard, but there's no signal. So maybe when this bug in MacOS is fixed (please Apple!), your device i working again and you don't need to buy a new keyboard?

I gave up and bought a Focusrite Scarlett Solo instead. It replaced everything wire by wire and works fine. It was hard to find something that has RCA outputs to headphone amp and monitors. But this one gets the job done. And it doesn’t need a power brick for 48 volt mics. High power USB port is enough. Apparently has more sensitive instrument inputs too.

https://us.focusrite.com/usb-audio-interfaces/scarlett-solo

I have the same problem and I do not see why I buy a new interface!! Apple what the **** is going on? Why you do not solve this problem? Why we can not use our m-audio interfaces? I'am a student. I do not have any money to buy a new interface from one day to an other!! I makes me angry. I do not understand this. Sole it!! now!

Hi @dougjam2

1. You should contact Apple Support to see if there any solution there. At least, let them know about this problem.

2. Then you may want to contact Avid Company Support, who made M-Audio Fast Track, see if they have solution there. At least let them know about this problem.

3. Then, buy a new audio interface other than M-Audio.

I have restored my system to the previous OS. It took all day, but it was worth it. I am using Yosemite again. When I bought my Mac Mini, I was advised by the sales person to buy an external disk and run Time Machine. It was good advise, since the restore went smoothly using my Time Machine backup. It is such a relief to have it functioning again.

Thanks for the suggestions.

I tried this for several reboots and each time I got to the point of seeing the "allow" button, it disappeared after a second or two, before I could unlock it and click on "allow". Very frustrating!

As I said before, I have restored my system to the previous OS (Yosemite) using Time Machine and it is a relief to have it functioning again.

Hey Man,

I had the same problem with my Fast Track Pro. After updating to 10.13.2 I wasn't able to use it anymore. Although I did this and it has fixed the problem. I had the Sierra High 10.13.1 installer and I simply re-installed this version. By doing this I just downgraded my OSX version from .2 to .1 and upon restarting I got my card working again.

Hope that you still have the installation somewhere around because if you do then this is your solution!

Cheers,

Herc

One of last updates from Apple make this !@#$. I arrived in studio with my band to play, open my project and boom .... what? Where is my Fast Track Pro ? Try all drivers without success. Remove all drivers and anything about maudio in my system files. No No no.. so frustrating. Macbook Pro 13 Early 2015, Mac OSX 10.13.2 ... device not connected.

It's clearly a Apple Issue (I believe), because it's working perfectly some weeks ago.

😟

Ok, so there's a new "supplementary" version of 10.13.2 released today, looks like a security thing. I'm guessing it doesn't bring back the FastTrack Pro support, but I'm going to wait before installing this time (in case even the MIDI aspects of the FTP are removed, as I'm still using those). Can anyone confirm whether the new update brings back FTP visibility or makes it worse? Thanks. (Would also love to go back to 10.13.1 but I don't have the installer or a TimeMachine backup that would help.)

Hey Man,

I had the same problem with my Fast Track Pro. I had the Sierra High 10.13.1 installer and I simply re-installed this version. By doing this I just downgraded my OSX version from .2 to .1 and upon restarting I got my card working again.

Hope that you still have the installation somewhere around because if you do then this is your solution!

Cheers,

Herc

Release notes of 10.13.2 was :

• Improves compatibility with certain third-party USB audio devices.

end not remove compatibility with certain third-party USB audio devices. 🙂

Maybe the apple forget that it produce very expansive device 😟

This is an extremely frustrating development. As a musician whose income relies on the use of this device, the prospect of it being unusable — despite working perfectly prior to the update — is unacceptable and doesn’t inspire faith in Apple.

I know it’s a niche case, but I’d like an explanation for WHY it no longer works — and whether we can expect an update in the near future or if we should bite the bullet and purchase a new audio interface.

I’ve been checking this thread every day for the last couple of weeks in the hopes that a new fix surfaces. No luck yet. Might be time to buy a new device, even though it feels like a ridiculous thing to do.

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!

Looks like 10.13.3 has just been released. Just wondered if anyone has tried it yet, and whether it makes things any better or any worse with the FastTrack Pro issue? (Apple Engineering may or may not have looked at this. The manager I spoke to acknowledged it wasn't particularly good that 10.13.2 was supposed to improve 3rd party USB audio compatibility but apparently did the opposite for the FTP, and said it might be something that may be addressed in future releases.)

FYI, if you read the entire thread, you'll see that the FTP was working fine on 10.13.1 without any special drivers. With 10.13.2 that was no longer the case, and now a lot of music producers here aren't particularly happy.