
- #M audio fast track ultra 8r how to
- #M audio fast track ultra 8r install
- #M audio fast track ultra 8r 64 Bit
- #M audio fast track ultra 8r drivers
- #M audio fast track ultra 8r driver
Sorry for the Noob questions, I'm afraid I'll mess things up.
#M audio fast track ultra 8r install
I'll post further tests results Edited Februby oliveiroĭoes your method also work without a working Yosemite install (also for 'reversing other kexts')? Which tab/function of KCPM did you use? I don't use any USB CardReader, Wifi Dongle or MassDrive which might be affected by IOUSBFamily.kext replacement, you'll have to do your own tests. The only problem I noticed is SystemProfiler not showing USB devices. Older versions of some of these kexts are included inside IOUSBFamily.kext/Contents/Plugins/, but others are not, which can affect some USB devices.įor now, all my USB devices work properly (Usb Webcam, Usb Keys, Usb Midi controllers and keyboards), of course the FastTrackUltra works as intended, and kernel caches rebuild properly. Then I repaired permissions, rebuilt caches with KCPM, and rebooted.

I simply renamed these 11 files : *.kext -> *.bak ( you can also copy them to a safe folder, and then delete them from /System/Library/Extensions) Inside AppleUSBTopCaseDriver.kext/Contents/Plugins/: Inside AppleStorageDrivers.kext/Contents/Plugins/ : There's been quite a lot of changes between ElCapitan and Yosemite in USB management.Īnd Kernel Caches could not rebuild until I backed up the following : I have the advantage of a dual boot config, with Yosemite and ElCapitan on the same drive, so I usually make modifications on the Elcapitan system from a booted Yosemite, with KCPM utility.īe also aware that replacing the IOUSBFamily kext breaks some dependencies, some other usb devices might not work until you reverse other kexts (for instance, I needed AppleUsbEthernet.kext to be reversed to Yosemite's version for my Webcam to work). Their purpose is to maintain proper permissions on the files, if you do it manually, it will copy the files with user permissions, which is not good. I backed up, then removed ElCapitan kexts ( IOUSBFamily.kext and IOUSBHostFamily.kext), then I use KCPM utility to copy Yosemite version (only IOUSBFamily.kext) to ElCapitan /Sytem/Library/Extensions/, I guess any other Kext Utility or Wizard compatible with ElCapitan will do.
#M audio fast track ultra 8r how to
On a genuine Mac, you'll have to disable SIP (I don't know how to do this) I'm on a hackintosh (OsX on a PC), and SIP is already disabled, which enables modification of system files (in System/Library/Extensions). (copy the kexts to the folder of your choice, most of the time I simply rename them *.kext to *.bak) I'll keep on testing but I have other hardware problems, and have to find time to fix this.Īlways do backups of the system files you replace. Don't do this on your main system, unless you know exactly what you're doing. WARNING: this is "work in progress", this workaround requires system files modification. To answer the request of a few users who pm'ed me for detailed information :

Or if you encounter problems, a complete USB stack reversing to Yosemite's at post 24 Hope this helps.See updated workaround at post 10 + 61 (only for Midi ports) It shouldnt be necessary to change the key name itself.
#M audio fast track ultra 8r driver
HKEY_LOCAL_MACHINE\SOFTWARE\ASIO\M-Audio Fast Track Ultra ASIO (64-bit) I havent tried it but I'm assuming that changing the string description of the driver stored under that key will be sufficient to allow it to load. Anyway for users of earlier versions of SONAR you should be able to work around this problem by renaming the driver string in the registry to something smaller than 32 characters. It blues screened immediately after installing the driver even before i launched SONAR :) Seemed ok after the reboot. The newest driver wasn't particularly stable on the machine I tried it on. I worked around it in our code and indeed the driver loads and works fine after that. The 32 bit driver string is shorter and so doesnt run into this problem.
#M audio fast track ultra 8r 64 Bit
Since the 64 bit driver string for the fast track exceeds 32 characters the string comparison fails and SONAR never sees the device.
#M audio fast track ultra 8r drivers
The code that tries to open the drivers compares the driver name string with 32 character string. The problem is caused by a bug in the ASIO sdk.


I tried this and indeed the X64 drivers do not show up in SONAR.
