Digidesign Mbox 2 Mini and El Capitan

MBOX 2 lights up but does not connect in 10.11.1.

Console has the following error, I'm sure it's due to the new security restrictions in El Capitan. I could try running with it disabled but at this point I've got Yosemite installed on an external disk..

10/21/15 8:29:24.438 PM MIDIServer[423]: Error loading /Library/Audio/MIDI Drivers/DigiDioMidiDriver.plugin/Contents/MacOS/DigiDioMidiDriver: dlopen(/Library/Audio/MIDI Drivers/DigiDioMidiDriver.plugin/Contents/MacOS/DigiDioMidiDriver, 262): Library not loaded: @executable_path/../Frameworks/DigiPlatformSupport.framework/Versions/A/DigiPla tformSupport

Referenced from: /Library/Audio/MIDI Drivers/DigiDioMidiDriver.plugin/Contents/MacOS/DigiDioMidiDriver

Reason: unsafe use of @executable_path in /Library/Audio/MIDI Drivers/DigiDioMidiDriver.plugin/Contents/MacOS/DigiDioMidiDriver with restricted binary

Any update on this? I'm really getting nervous as I have not seen any response from Apple and this was working fine before the upgrade. I'm totally hosed because I didn't activate time machine until after the upgrade (have a brand new iMac). Several projects underway and now am completely stuck.

My experience was that MBOX is still non operational with 10.11.1. It lights up but is not recognized.

My *personal opinion* is that Avid will have to provide an updated driver to make it work with the security changes Apple implemented in El Capitan.

However, MBOX 2 is technically no longer supported by Avid / DigiDesign as it is pretty old, so I would not hold my breath waiting.. They do seem to be aware of the issue though so you never know..

My suggestion if you want to get back to work is to go back to Yosemite via backup (if you have one) or install it on a separate disk. I just installed it on an external USB 3.0 disk and am running that way..

Good luck.

I can confirm that.

My Mbox 2 is neither recognized by 10.11.1.

I am really surprised by Apple, this is not the kind of customer care they've always delivered.

Luca

Hi

I wish I had found this thread before I upgraded to El Capitan last night... My Mbox 3 is no longer recognized by the system, of course. It´s not a disaster but I feel a bit stupid for not having doublechecked that things would work after the upgrade. Figured that El Capitan has been out long enough to have Avid fixed the drivers... but no.

/J

It's not really Apple at fault. There are plenty of audio interfaces that work just fine with El Capitan because the manufacturers use the native OS functions to connect their devices. Avid (and some others) wrote their own bespoke audio interface drivers, and it is this software that is incompatible with El Capitan.

Like you I am frustrated with myself for blindly updating to El Capitan, and my MBox 2 is non-functional as a result. I am not holding my breath for an update from Avid because the hardware is pretty old now, and it's really not Apple's problem to fix.

However, I also have Surface Pro 3 running Windows 10, and I am pleased to say that the MBox and Pro Tools 8 LE work perfectly on that so for now I have switched from Apple to Microsoft!

Ric F wrote:

It's not really Apple at fault. There are plenty of audio interfaces that work just fine with El Capitan because the manufacturers use the native OS functions to connect their devices. Avid (and some others) wrote their own bespoke audio interface drivers, and it is this software that is incompatible with El Capitan.

This statement is (mostly) incorrect, it is companies who write their own drivers, (MOTU and RME), that have the most efficient, best performing audio interfaces. Apple's system drivers either change or are modified with every Operating System upgrade, including incremental upgrades so you never know what you're getting. Many of the USB devices that have failed do use Apple's system drivers. (personal opinion) Because USB uses the computers CPU to manage data transfer it is never the most stable audio interface. System drivers are constantly being changed to follow new standards, every upgrade is a crapshoot.

Generally speaking, professionals who rely on performance and stability seldom upgrade a perfectly running system, many here still use Logic 9.8.1 on hardware running Snow Leopard. What's more important, stability and performance or running the supposed latest and greatest (inefficient) OS?

It might be worth it for MBox2 users to check out this USB driver.

http://www.ploytec.com/

I have been keeping up with this problem for awhile now and I think I found a workaround.

I am on OS 10.11.2 currently. If you uninstall all of your Mbox drivers, the speakers will work. Just go to Applications > Utilities > Audio MIDI Setup and the Mbox should show up in there.

Plug and play

Hi g-d-d-m, I did what you suggested but the device wont appear in the audio midi setup.

Do you have pro tools installed?

Anything you installed for the plug and play functionality?

Thank you,

Hey Francisco

I made sure I uninstalled all of the Avid mBox drivers, etc.

I do not have Pro Tools installed. I didn't install anything else that might connect it.

Hope that helps.

Are you able to connect an instrument / microphone to the mbox and use it for recording?

Still not working in 10.11.3.

I´m very disappointed from Apple!

I have been able to use my MBox 2 with El Capitan 10.11.4 by disabling System Integrity Protection as referred to here;

https://developer.apple.com/library/mac/documentation/Security/Conceptual/System _Integrity_Protection_Guide/ConfiguringSystemIntegrityProtection/ConfiguringSyst emIntegrityProtection.html#//apple_ref/doc/uid/TP40016462-CH5-SW1

It involved booting into recovery mode and running a command in the terminal to disable low level system security checks. You might prefer not to do this.

The terminal command is;

$ csrutil disable

I'm only using the MIDI-in functionality on my MBox and can't vouch for other things.

Can't believe it works (but not at all)! Thank you so much for the solution. Yes it's really make my mbox2 starting well under El Capitan 10.11.4, all leds now lights correctly as they should, mbox2 is now showing in Audio Midi setup as a midi device, but... It still not displayed as an audio device : (

So we're almost close and maybe next solution will bring this great interface back to live.