MOTUnation.com

nk_e wrote:I feel less annoyed.

I still feel for ya, nk_e.

nk_e wrote:Here is an article on how to turn SIP on and off.

http://www.macnn.com/articles/15/10/21/ ... ou.130954/

Good info in here and a helpful perspective. I feel less annoyed.

Thanks. I think this might be the key to getting the old AlphaTrack USB driver working under El Cap. That's the deal killer for me right now.

HCMarkus wrote:The "Computer as an Appliance" is an approach with which I concur, especially in a recording studio. When DP works perfectly under a computer's OS, "upgrading" that OS for the sake of functionality that has nothing to do with DAW workflow is fraught with potential perils.

Which is why I'm still on Mavericks.

As for Apple, Yosemite will probably be the end of the line for me if they continue to go the direction of locking down my computers. Of course the problem is Windows 10 seems to be going down a similar path, so we might have some rather bleak choices in a few years.

Just an update. I did a clean install of El Cap (10.11.1) on a test partition and after much hair pulling, it seems I figured out a process to get AlphaTrack working—at least as you can see from the graphic below, it is now recognized. The installer doesn't work, it involves manually copying components to the proper location, as well as a special way to install the FrontierDesignAlphaTrack.kext file.

I did disable SIP prior to working out this procedure. I'm not sure it is necessary. I'm going to try to repeat this with SIP enabled. If that doesn't work, with any luck SIP can be re-enabled AFTER successful install. I hope to follow up with specific instructions soon.

EDIT: I should hasten to add that I have not yet confirmed that it will work with DP 9.01 and the 64-bit control surface bundle, but I'm very optimistic.

It depends where that .kxt file is located. You might get lucky. That would be nice.

mikehalloran wrote:It depends where that .kxt file is located. You might get lucky. That would be nice.

Yep. By way of follow-up, the AlphaTrack driver will not load if I re-enable SIP so I have to leave it off. I'm prepared to do that though as I don't load suspect software on my studio Mac. What bugs me is from what I gather these kexts have to be signed by current developers that belong to the Apple Developer program. So if a company goes out of business like Frontier and it's developer account lapses or whatever, a seemingly functional driver just won't work. I wish Apple had some sort of provision for reputable legacy developers if this is all the issue is.

I also found the latest beta 3 MOTU MIDI drivers for El Cap seem to work with my USB MTP/AV and MIDI data is being properly routed out the correct cables, etc.

MIDI Life Crisis wrote:What is stopping the mfg( developing a compatible driver? If the device is discontinued, I'd look to the mfg to make it compatible again.:

I've asked that question a couple of times directly to makers. The answer is sometimes that there is no money in it for them. The other answer is that some functions can be burned into the hardware or put in a driver. It can be cheaper to do the former but they take the risk of becoming obsolete. I don't know whether either applies here but I'd note that motu appears to have planned well, and their recent hybrid versions seem to have read the writing on the wall.

Interesting. This FireWire support issue may explain why after installing El Cap, I might have had some glitches last night with my Liquid Mix, which has been working with 32 Lives. It settled down now but I'm keeping an eye on it.

billf wrote:Yosemite will probably be the end of the line for me if they continue to go the direction of locking down my computers. Of course the problem is Windows 10 seems to be going down a similar path, so we might have some rather bleak choices in a few years.

So...DP for linux? They could probably salvage much of the UI code using GnuStep.

Based on what people are saying, it sounds like RME Firewire devices should be OK too.

When I upgraded to the Fireface UCX though, I went USB right away, as they also write their own USB drivers and the specs are so close on that model to the Firewire performance. I haven't regretted the move but did consider switching back to Firewire at one point, then noticed those drivers don't seem to be upgraded as often and that you have to be connected via USB to do the Firewire updates anyway, amongst other things that make it clear where RME thinks things are headed. All power to them for doing such a robust job of both for so long now though.