How to use Ultralite under Monterey

[Vladimir L'empathik]

Hi,
I'm new to motunation. I'm French and my English is pretty bad, so sorry if I can't make myself understood.

I have a problem for a few weeks and can't find a solution anywhere else. You're my last chance!

Here it is:
I've had an early version of the Ultralite (Firewire only) for quite a few years. It's old but perfectly functional because it's always been maintained.
Until now, it worked perfectly under Mac OS 10.
I hadn't used it for two or three years because I didn't have a powerful enough computer.

I now have a 2014 Intel-based MacBook Pro running Monterey (12.7.6), with Thunderbolt 2 ports.
And I'm working on a project again with audio recording and MIDI controls.
I'd like to run AbletonLive.
I did some research beforehand, and it seemed like it would work, but I can't seem to get it to work.

Since my MacBook doesn't have a FireWire port, I ordered a Belkin dock with a FireWire port (not so easy to find).
When I connect it to the MacBook, the FireWire connection appears in my system report, up to 800MB/s.
So far, so good.
The drivers for my Ultralite stop at OS 10, but I read somewhere (I can't remember where) that it could work, under Monterey, with the Ultralite mk3 Hybrid drivers.
I downloaded and installed them, but they don't recognize my Ultralite.
Unable to update the firmware.
Unable to use it.

Does anyone have any leads or solutions? I also read somewhere that it could be related to the dock and that it would be better to use Apple Thunderbolt to FireWire cables. Someone who is knowledgeable about computers and sound assured me that it would work with the dock. Could that be the problem? Please help me, I'm going crazy.

For clarification, I'm a musician, not a computer scientist, so please use terms I can understand.

Furthermore, my activities don't allow me (yet) to buy new equipment, especially since this one is, in theory, perfectly functional.

Thanks

[mikehalloran]

2011–2012 were the only years that Macs had both Firewire and Thunderbolt ports.

For a 2014, you must have an Apple Firewire to Thunderbolt adapter MD464ZM/A — this plugs into your MacBook Pro. It's discontinued by Apple but available on the used market. Prices are all over the map.

FW400–800 can be a simple adapter or cable.

This is the driver you will need from MOTU on the 828mk3 Hybrid site

Driver
MOTU Audio Installer Mac v89555 | Oct. 13, 2021
Supports macOS 14, macOS 13, macOS 12, macOS 11

Depending on your macOS, there are different instructions for installing MOTU drivers here:

https://motu.com/techsupport/technotes/ ... igh-sierra

You want the ones for macOS 10.13 High Sierra - macOS 12 Monterey.

You may also have to reset your unit to factory default
https://motu.com/techsupport/technotes/ ... m%20reset.

[Vladimir L'empathik]

Hi,
I took a long time to reply, but I had some issues and had to revert to OS 11, which is more stable for my laptop.

But I tried it under OS 12 with the same result.

So I bought the MD464ZM/A Thunderbolt FireWire adapter, which has become rare and expensive.
To avoid using the Belkin dock.
I followed the instructions for the Motu drivers, as per your link. I also reset my Ultralite to factory settings.
Nothing worked.

I tried the drivers for the 828mk3 Hybrid, then the drivers for the Ultralite mk3 Hybrid, as I read on another forum. I also realized they're the same driver.
Nothing works.

When I launch the Audio Setup file, I get a page that says "launch Motu Audio Setup when hardware becomes available."

I checked my Firewire connection; it's fine.

I have the impression that the problem lies with the driver, which isn't adapted for this Firewire-only device.

Are there other drivers that might work?
Why doesn't Motu update its drivers for newer OSes (and it's not very new!)
Does anyone have any other ideas?...

This is really annoying...
Thanks in advance.

Vlas

[mikehalloran]

The MOTU Audio Installer for the 828mk3 Hybrid is the correct driver and it works. The problem is installing it and there can be many steps beginning with Big Sur. In addition, you have to reset your unit to factory defaults which some don’t think is necessary—but it is.

I’ve been working on a page that explains this a bit better in my spare time but I’ve been tied up lately. As other time-dependent tasks get done, I expect to get back to it and done in a few days.

[Vladimir L'empathik]

Hi,
It's been a while since my last message.
I've been very busy and have more or less given up on getting my Ultralite working.
But I'm coming back to this story because there are a few things I still don't understand.

I did factory reset the Ultralite following the procedure. It's fine.

But unfortunately, the 828mk3 driver still didn't work.

I thought that, since I had previously installed the Ultralite mk3 driver, there might be some files left on my MacBook that were preventing the 828mk3 from installing properly.
So I searched for these files using easyfind.
Sure enough, there were plenty of .kext files and others. I was able to delete some of them using Terminal.

But there are still some, including MOTUFireWireAudio.kext files, which I can't delete.

Apparently, I don't have the necessary permissions. I don't understand because I normally have all the permissions to work on my MacBook.
Is Apple blocking work on system files to avoid problems?
After some research, I tried deleting them by logging in as root, but they no longer appear.
I don't understand anything anymore, please help me.

Thank you.

[mikehalloran]

Hi,
It's been a while since my last message.
I've been very busy and have more or less given up on getting my Ultralite working.
But I'm coming back to this story because there are a few things I still don't understand.

I did factory reset the Ultralite following the procedure. It's fine.

But unfortunately, the 828mk3 driver still didn't work.

I thought that, since I had previously installed the Ultralite mk3 driver, there might be some files left on my MacBook that were preventing the 828mk3 from installing properly.
So I searched for these files using easyfind.
Sure enough, there were plenty of .kext files and others. I was able to delete some of them using Terminal.

\\ But there are still some, including MOTUFireWireAudio.kext files, which I can't delete.

Apparently, I don't have the necessary permissions. I don't understand because I normally have all the permissions to work on my MacBook.
Is Apple blocking work on system files to avoid problems?
After some research, I tried deleting them by logging in as root, but they no longer appear.
I don't understand anything anymore, please help me.

Thank you.

This is a root file and can be the problem. It can’t be running until after the drivers have loaded correctly and purging is the best way.

You can use FindAnyFile to delete these by holding the Option key, then entering your Admin password when asked. FAF can be downloaded for eval from the developer or purchased from the App Store. It’s what Finder/Find always should have been.

The other way is to boot into the Recovery partition and disable SIP. FAF is faster.

[Vladimir L'empathik]

I downloaded FAF.
I followed your instructions: delete with option, enter the password.
It still doesn't work.
Still the same result.

EasyFind found exactly the same files.
Exactly the same problem.

I've already tried disabling SIP. That doesn't work either because, as I said, when I go to the recovery partition, my files don't appear.
It seems the real problem is the way my MacBook was modified.

Any other ideas or should I just give up?