Mac OS X Sierra upgrade prob: AppleMIDIUSBDriver.plugin causes kernel panic

Started by mooncaine, January 24, 2017, 12:51:27 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

mooncaine

Not sure if I can trouble you for help with this (any ideas welcome), but I do, at least, want to spread the word that this is happening, in case you can avoid it happening to you.

I updated a Mac Pro directly from Yosemite to Sierra a few months ago. Since then (I think?), I've been unable to use several MIDI programs, esp. Audio MIDI Setup. I only noticed this a couple weeks ago.

Through trial and error, I narrowed the cause down to one file, AppleMIDIUSBDriver.plugin, that I found in /Systems/Library/Extensions. If I remove it, no crashes. If I put back the one from a backup, same result (it's probably from Yosemite, but in any case it's the only backup of the file that I've got, dated 2014).

It seemed to be crashing just because the MIDI devices window in Audio MIDI Setup was open, last time it worked without crashing, so when the app restarted, it tried to open the MIDI window again, and... instant kernel panic.

If I leave either version of the file AppleMIDIUSBDriver.plugin in place, I get instant kernel panic, but If I remove it, no panics, but also (presumably) no MIDI over USB. For this video editing machine, that's not a huge problem, but I do need a solution eventually.

admin

It's for this specific reason why Apple Support specifies many older Mac Pros are not compatible beyond Yosemite.

My 2008 MacPro still runs Snow Leopard and is not compatible with newer versions of OSX
http://www.everymac.com/systems/by_capability/maximum-macos-supported.html


vtgearhead


mooncaine

admsustaniac, thanks for that link. It'll be a good reference in the future, too.

My Mac Pro (the first generation of Darth Vader Wastebaskets) is listed as 'current' so I'm still considering this a bug that should have a fix. Still looking for that fix. For all I know, I have a corrupt file or two on my system causing this. Don't know yet.

Thanks!

gumtown

I updated my virtual machine of mac Yosemite to Sierra,
after the forever download, then the install, all good so far,
then the reboot.. .. .. .. .. .. .. .. .. .. .. ..  :(
It never restarted,
so I had to wipe it and start with a fresh Sierra image, and a new download of xcode developer tools, USB midi drivers, and such..
Free "GR-55 FloorBoard" editor software from https://sourceforge.net/projects/grfloorboard/

mooncaine

I saw a report today from another user who says he gets this crash, too, even after a 'clean install' of Sierra.

https://discussions.apple.com/message/31331602

Elantric

IMHO you have two choices

* Choose to remain productive and use an older version of OSX that actually works with your Audio  / MIDI gear

or

* Choose to obey Apple's update policy's and use the latest version of macOS  - because you prefer using Siri, Apple Pay, Apple Watch more than creating music

http://www.macworld.co.uk/review/mac-software/mac-os-x-el-capitan-vs-macos-sierra-comparison-review-3642607/

In 2017, the current regime in charge at Apple has placed the needs of content creators as a  lower priority, with many bugs, new zipper noise in your audio path when dragging  / resizing apps, more security and conflicts with third party USB driver installation problems, etc.

https://www.sweetwater.com/sweetcare/articles/sierra-mac-os-10-12-compatibility-information/
QuoteIK Multimedia posted the following information regarding compatibility with macOS Sierra in their forum:


Note that it is never recommended to update to a new OS during its first days of release. Especially if you use your computer for important music (or other) work, are mid-project, and a myriad of other reasons."

gumtown

From my experience of Sierra, (to me) it seems that the priority of midi (and possibly audio) threads in the operating system have been relegated a lower priority.
Most of the time, midi data is in real-time, but as the system needs to check on other things (like what the apple watch is up to, and other important things), midi data is stalled and becomes non-real time.
It seems that applications which require real time midi/audio are now going to have to be designed to wait until the data is available, while waiting for display desktop 3D effects are finished being rendered, which is either going to cause audio dropouts, application lags, or application crashes on audio related aps.
Free "GR-55 FloorBoard" editor software from https://sourceforge.net/projects/grfloorboard/

mooncaine

Sadly, in the case of 'my' Macs, they don't belong to me, they belong to an employer. If they say it's gotta be updated, I gotta do it. It's their choice, not mine. I completely agree with your advice about choosing whether or not to update the OS.