MOTUnation.com

I think this was important enough to make a new topic.

DP users might want to hold off on installing High Sierra. I wrote a contact of mine at MOTU about High Sierra and got this response:

Testing is still ongoing but it appears that there is an issue with the auth file getting deleted (this can happen when the computer is restarted) in 10.13. If this user doesn't regularly shut down the computer, they might not be seeing this. Users should update to the new OS at their own risk until we release an official statement.

Emphasis above is mine. So if it was me... I wouldn't do it until there's an official okay from MOTU. Or... unless I have a disc image of my boot drive and am prepared to restore. (And I don't know how the new disc formatting of the boot drives might affect this).

Thanks, James! Good to know. I had no plans to go to HS immediately anyway...I always wait
at least three to six months before upgrading to a new OS.

David Polich wrote:Thanks, James! Good to know. I had no plans to go to HS immediately anyway...I always wait
at least three to six months before upgrading to a new OS.

And you are thus wise, David Polich.

James Steele wrote:... Or... unless I have a disc image of my boot drive and am prepared to restore. (And I don't know how the new disc formatting of the boot drives might affect this).

Easy.

Have a recent Time Machine backup.

Turn Time Machine off before upgrading the OS.

Have an 8G USB drive formatted as a Sierra install drive. I can post instructions for doing it in Terminal again, the only way this should be done.

After upgrading to 10.13, make sure that Time Machine remains off till you know it’s going to work out.

If the 10.13 upgrade doesn’t work out...

Insert the USB Sierra installer thumb drive. Shut down your Mac.

Option-boot into the USB Sierra thumb drive

Run Disk Utility from the thumb drive and reformat your drive.

Run the Sierra installer

Restore your user settings, files and applications from Time Machine.

Reboot, reenable Time Machine.

It is likely that High Sierra will break a lot of plugins.

HS finally carries through on the threat to remove the deprecated MacOS ComponentManager. Why do you care? Because CM is how a host gets a list of all the AudioUnits available on the system.

There's a new mechanism (of which I am not totally up to speed) but expect to get a LOT of emails about updating your plugs for HS over the next year because there have been a ton of problems with old plugs and the new mechanism. The CoreAudio list has had a few developers posting problems dealing with the transition.

SixStringGeek wrote:It is likely that High Sierra will break a lot of plugins.

HS finally carries through on the threat to remove the deprecated MacOS ComponentManager. Why do you care? Because CM is how a host gets a list of all the AudioUnits available on the system.

There's a new mechanism (of which I am not totally up to speed) but expect to get a LOT of emails about updating your plugs for HS over the next year because there have been a ton of problems with old plugs and the new mechanism. The CoreAudio list has had a few developers posting problems dealing with the transition.

Really? I’ve not had problems except for older 32 bit plugs with a Carbon GUI. 32Lives has been the wrapper. OS 10.13 has dropped Carbon altogether. SoundRadix is saying that, if you are still using any of those, don’t go to High Sierra which makes sense. I don’t see how they’ll get around this.

If you have those plugs in an old project, you will still hear them but you will be unable to access the GUI (as it was before I bought 32Lives). I confirmed this today. In my case, I have replacement plugs and VIs if I have to revisit these old projects.

So 32Lives falls into the obsolete bin for me. Oh well, those plugs weren’t going to work at all once OS 10.14 arrives next year if Apple makes good on finally dropping 32 bit support, originally rumored to happen with Yosemite.

SixStringGeek wrote:It is likely that High Sierra will break a lot of plugins....
There's a new mechanism (of which I am not totally up to speed) but expect to get a LOT of emails about updating your plugs for HS over the next year because there have been a ton of problems with old plugs and the new mechanism. The CoreAudio list has had a few developers posting problems dealing with the transition.

I'm using Waves, Steven Slate, UAD2, Antares, Eiosis, Tonebridge and many other processing plugs, and VIs by NI, Spectrasonics, Plogue and a ton others I can't remember.

They all show up and operate fully under 10.13. So, if a bunch of devs are complaining about HS, then they are developing software I guess I'm not all that excited about or aware of.

Well that's the buzz in the dev world.

I'm still installing software and swapping CD ROM's after total loss of all my SSD's.

Its not like I can try it but I'm staying on Sierra....probably for the life of the machine.

Also I just got an email from Korg about the legacy collection plugs having updates to deal with HS. So there's that.

Back in the '90's, music tech guru Craig Anderton advised:

"..it's best to use 'trailing-edge technology".

Seems even more applicable to todays' scene!

Finally, an OS release we can all reject. Lol

As an owner of a studio computer for which High Sierra will almost certainly be the last Apple-supported OS, I fully intend to take my Mac there once we get to a .2 or .3 release. Benefits of primary importance will likely be security-related.

Of course, if strange and undesirable High Sierra issues arise in the interim, I will keep the studio machine running Sierra.

IF I can run Adobe CS 5 and 6, DP and Finale, I'll upgrade. All deal breakers for me.Word? Meh...

MIDI Life Crisis wrote:IF I can run Adobe CS 5 and 6, DP and Finale, I'll upgrade. All deal breakers for me.Word? Meh...

Point taken.

artfarm1 wrote:Back in the '90's, music tech guru Craig Anderton advised:

"..it's best to use 'trailing-edge technology".

Seems even more applicable to todays' scene!

That's pretty funny coming from a guy who was a early adopter of every tech, every software update, every new product category. And no, it wasn't just his job... he was that guy before became famous for it.

I never buy into this approach to the tools we use, and neither did Craig. You just have to be prepared to go back to the previous state of your start-up disk, and then do that if the update doesn't work.

Gravity Jim wrote:I never buy into this approach to the tools we use, and neither did Craig. You just have to be prepared to go back to the previous state of your start-up disk, and then do that if the update doesn't work.

I generally agree, but see no reason to rest my butt on the bleeding edge when my current setup is working great. Cowardly as it may be, I will allow you and others like you to beta test for me, please be assured with tremendous appreciation and respect!

If possible (i.e. respecting MLC's concerns about Adobe CS), it is clearly wise to stay at least current enough that security updates are still being provided by Apple.

The irksome thing is when an update seems to be working perfectly, and does so for a week until you go to use the one thing you forgot to test and it f's up. And you are back n troubleshooting mode.