Firewire Driver Download

[Nickie Koskinen]

Appledropping on-going development for FireWire devices that were supported with the Core Audio driver standard is a catastrophe for a lot of struggling musicians who need to both keep up to date on security updates that come with new OS releases, and continue to utilise their hard earned investments in very expensive and still pristine audio devices that have been reduced to e-waste by Apple's seemingly tone-deaf ignorance in the cries for on-going support.

Probably not the first time you gurus have had someone make the logical leap leading to a request for something like this, but I was wondering if it might be somehow possible of shoe-horning the code used in previous versions of Mac OS that allowed the Mac to speak with the audio features of such devices to run inside the Ventura version of the OS.

AppleFWAudio.kext was removed from Ventura. I took a Mac that still has Monterey, took AppleFWAudio.kext, and modified it slightly so it would install on Ventura. The installation process is the same as installing any third party kernel extension, so you'll have to grant permission in System Settings once prompted.

The google drive link below is a download of the installer package I made. I suggest using the free Suspicious Package application developed by Mothers Ruin Software to inspect this installer package, so you know that it does what I'm telling you it does.

Regarding matt9's hack, well, we all really appreciate it man. Does it work for everybody that tried it? I'm thinking about upgrading to Ventura to try this also, I have a perfectly working RME Fireface 400 interface. But not sure how an eventual downgrade would work or if I would need to actually reinstall everything from scratch..

If you have any familiarity with the 'underground collective who builds Mac clones using regular PC parts' - you may have heard of an app called Kext Wizard. It's used to do just exactly this sort of thing (properly install kexts & then rebuilds permissions).

I am in the same boat...Maybe Apple is more sensitive for security risks. And this decision does introduce a risk caused by an Apple decision.Very often a seemingly more secure, but in reality more complicated technology completely removes security in the real world. People need to get work done, if security measures are in the way, they bypass them.This is a perfect example, it should be reported as a security flaw! Maybe they are willing to listen to that aspect...

Hoping Apple will reply, or even notice, a few requests among the millions received daily, may be a tad optimistic.However, how would we go about creating petition, or some kind of group poll, that they might react too?What would be the best format to accomplish this in?

Unfortunately doesn't work with my Motu Traveler v1 on M2 pro Mac mini. I tried installing with Kext Wizard and pacifist after disabling SIP and it never shows up after multiple restarts and accepting extensions in system settings.

Have been playing around with getting this to work this afternoon. I'm on a Mac Mini M2 PRO + Ventura 13.2. I wasn't able to make the installer work, unfortunately. So I used 'Suspicious Package' to extract the AppleFWAudio.kext file from the installer. I've dabbled for years in the Tonymacx86.com world, so I am somewhat used to doing this sort of thing.

...but nothing shows up in the Sound System Settings option. I have another audio interface now that is my primary interface, but I could sure use the extra input channels with doing a bigger session & need more than 8 channels of input (other interface has 8 mic pre's).

I have managed to get this working on an M2 2023 MacBookPro. I'm using an Apogee Ensemble Firewire and it is now detected and works, mostly. I had to use kmutil myself to get the kernel extension to load. The script in the package didn't work so I just grabbed the files from it using Suspicious Package, disabled SIP, modified my Startup Security Utility settings and then ran kmutil in the terminal.

However, I have been having problems with my system crashing at random intervals when using the ensemble. I'm going to keep tinkering and see if I can figure out a work around. Any assistance folks can provide would be greatly appreciated. I noticed a similar situation for folks here: eyetvforum.com/index.php?/topic/305278-incompatibility-with-macos-13-ventura-beta/My console reports: Library not loaded: /System/Library/Frameworks/FWAUserLib.framework/Versions/A/FWAUserLib

Thanks Apple ??? You now disabled this ability in Ventura 13.4 ??? I have no words.... Now I'm getting error message that this Kext cannot be loaded. Once I'm clicking on "Allow" button, I'm getting to the loop where I need restart computer.

Hey! Need help from you guys. Im got a Mac Mini M2 Pro, with ventura installed, i have a Mackie Onyx 1640i, Firewire audio interface. With the help of this post, i was able to make Ventura recognise the audio interface in the System Report, on the firewire devices, but it doesnt appear on Audio Midi Setup, System Sound or in Ableton Live. I followed all steps from this post, minus the "kmutil" command, it always give me an error. Anyone can help me please? I need this audio interface to work...thanks in advance

Windows 10 Pro and RME UFX. I have been updating my drivers as they become available. I thought the old drivers would be overwritten, but, when I looked in Programs & Features recently, they were not. I tried to remove them from P&F using Uninstall, but I get a large error window saying something to the effect that the driver's uninstaller can't be found. I did manage to uninstall a few of them, but not all, by first uninstalling the most current driver, then deleting the UFX in Device Manager, rebooting and allowing Windows to assign the next driver "in line" so to speak, rinse and repeat. This worked for a few of the newer drivers, but not all.

Thats true that there is no need, but I agree that those markings of older installations are really annoying. They tend to pile up with old Windows installations.

Maybe messing with the registry would help. I haven't tried that.

That post you referenced is from 2013. I can't delete those entries on Windows 10 Pro , I get a message window stating that the uninstallers are not available when I go to Programs & Features and try to uninstall from there. Is there somewhere else I'm supposed to delete them from?

I do not have this problem under Windows 10, although I never deleted these entries (that I also had under Windows 7). The reason might be that I delete all audio devices, including the currently not active ones (!), from time to time (cleaning up the computer for quicker opening of the Sound panel). Not sure if that is the reason, though. You should not waste time with these entries, they do no harm at all.

Help! I urgently need to uninstall/cleanup all the RME drivers and try a fresh installation from scratch, because on my main DAW under WIN 10 Professional, the Fireface isn't working anymore. On my laptop (Windows 8.1) it's working like a charm, so it is not a hardware issue. I was able to uninstall an entry called "RME Fireface" in Windows under "Apps & features", using the Uninstall button. But there are 8 entries whose name begins with "Windows driver package - RME Fireface ...". When I try to uninstall one of those, I get the long error message mentioned in this thread.

RME support seems to be letting me down. After a half-hearted reaction (asking for information that was already given in my original request) I didn't hear from them for more than 2 days already. Here's my current problem:

After updating my DAW from Windows 7 to 10, my Fireface UFX was still operable but not entirely stable. During a Loopback recording the signal which I was recording changed to a loud hiss. That was under Firewire. So I thought it would be best to update to the latest drivers and firmware, which is what I did. All seemed to go well and I got messages saying that it was successful. But as a result, the USB driver isn't visible anymore. Neither in the Windows Sound Settings nor in Cubase I can select it. The Firewire driver on the other hand can be selected, but when I do so, no sound is played back and the whole system is slowed down severely. I repeated the uninstall-reinstall cycle several times, but each time with the same result.

You can only see a RME WDM driver in Windows Sound if you created WDM devices ...

You changed the driver from firewire to usb ?

Its a different driver so you need to create WDM devices again I would guess.

You didn't tell which drivers you have installed now, you wouldnt be the 1st who picket the wrong ones.

So could you kindly detail which drivers you installed (name of the file which contains the version number).

What you did there is a major release upgrade from an old Win7 to a new Win10.

If this is an important PC for you or your business, then you need to plan an upgrade with more care.

In a good case of luck this can be easy, but there is no guarantee for that.

I had written a long post with my latest findings, but when I pressed the Preview button, I lost everything apparently due to some malfunction of the forum page. There was a message saying that I didn't have the right to use this function. But I was logged in.

"RME Fireface UFX" appears in Device Manager when switched on.

Connected via Firewire, Device status is shown as "working properly", although it doesn't produce any sound.

Connected via USB, Device status says:

"Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)

Object Name not found."

Right before checking this I had done yet another installation of the USB driver which ended once more with a message saying that "The drivers were successfully installed on this computer"

> There was a message saying that I didn't have the right to use this function. But I was logged in.

Try to completely logout and re-login.

I also had a rights issue not being able to visit "Neue Beitrge", which could be solved by this.

3a8082e126