Fast Track Pro on macOS High Sierra

[meireles]

I'm having problems with M-Audio "Fast Track Pro" (MacOs High Sierra), giving up the interface and AVID. I don't believe that commercially a company can do this with their customers ... Disrespect!

[ronyb]

Same issue here. fast track pro not recognized by my Mac since i ve updated to high Sierra. No new driver released since 2014!! Please help!! I've got important recording to do.

[minicus]

Hi friends, I've got a lot of help before, now it's time to give it back.... ;-)

I found a (temporary) solution for the issue.....!!

I copied some files of the mbox-driver (with has been updated for sierra) into the 1.9.5. driver of my fast tracks pro files, tryied some combinations..... and magic!!!! It works, it works for recording, track values etc etc.... I attach my patched files with this instruction:

1. install the included mbox-driver
2. install the included fasttracks pro-driver
3. delete like written on the folder
4. exchange/drag like written on the folder

Good luck!! - Minicus

[minicus]

..... here the files

http://www54.zippyshare.com/v/2IODoMMM/file.html

[brdeveloper]

Originally Posted by minicus

..... here the files

http://www54.zippyshare.com/v/2IODoMMM/file.html

Hi... did you get the control panel applet working? Moreover, can you sample at 48KHz/24-bit instead of 44.1KHz/16-bit from the default class-compliant driver from Apple?

P.S.: I wonder if the same procedure would make FTP working on El Capitan at 48KHz/24-bit.

[minicus]

Of course it can not be a proper connection, since I mixed one with the other but i.e. in Logic it functions with 16bit or 24 bit, no probl. but in the pref-pane it shows device not connected but you can change the bit-rate....!! At least you can use it.... recordings are same quality!! Dont know for other Interfaces but I think that Avid has a basic pref for all similar interfaces and the mbox looked pretty similar....

greetings - minicus

[minicus]

B.t.w., maybe the steps written are a bit confusing, i.e. you have to change the automatically installed extensions with the one I patched... that's all! There are two of them, one in the OS/System/Library/Extensions and one in the OS/Library/Extensions - change the installed fastrack-extensions with the ones in the called "exchange Folder"..... to avoid to have a prefpane and exts of the mbox-install just delete these... only these! ;-) - good luck! M.

[brdeveloper]

Originally Posted by minicus

B.t.w., maybe the steps written are a bit confusing, i.e. you have to change the automatically installed extensions with the one I patched... that's all! There are two of them, one in the OS/System/Library/Extensions and one in the OS/Library/Extensions - change the installed fastrack-extensions with the ones in the called "exchange Folder"..... to avoid to have a prefpane and exts of the mbox-install just delete these... only these! ;-) - good luck! M.

One more question... I would like to reproduce your procedure from scratch... how did you extract that M-AudioFastTrackPro.kext? Have you altered some header or is it a kext file from another driver version?

[brdeveloper]

Just adding to the discussion. I did your procedure on El Capitan. After the first restart I got a pretty high latency, so I decided disabling kext signing (Command+R to enter recovery mode, then typing

csrutil disable

in the console). After the next restart I was getting low latency, but I suspect that Reaper is reporting the actual sample rate wrong.

That is, I've set Reaper to ask for 48KHz and then I recorded a short bass line, and finally switched to the built-in output. If everything went fine, I should hear my recording at the same pitch, but no, I got the built-in output playing the recorded track at a faster speed (higher pitch).

Next test: asked 44.1KHz sample rate when recording through the FTP, then I switched to the built-in output. Now I'm getting the same pitch.

Conclusion: I'm only getting 44.1KHz sampling.

[rasjani]

Tried to follow up the instructions but same results as previously - plugin FTP and console shows that the kext can be loaded because it doesnt pass the validation..