MacOS Sierra

No problems with Pixelmator and Sierra here; MB Air 11" mid 2012

Good to know - here, Pixelmator works as advertised on local drives, but freezes Finder when directly accessing a NAS.

EJ

Pixelmator to/from QNAP TS-269L via WiFi very smoothly.

It's most likely Synology related - it looks like any program that relies on file versioning, including numbers, pixelmator has issues with Diskstation.

Cheers,

EJ

Thanks for the warning - will wait - El Capitano sailing OK for now

Issue is definitely related to the file sharing protocol on Apple's end - I have my NAS running Apple's AFP (to allow time machine). Acting on an online tip, I connected using samba (windows file sharing) and everything seems smooth and fast again. Looks like AFP between non-apple devices is broken under Sierra. Still a bit more testing required but this looks like a good interim but not intuitive solution.

EJ

Quick update: SMB works well, provided AFP is fully disabled on the server. This prevents time machine backups on the NAS, which is not ideal, but allows use as shared drive on apple computers. Note that under SMB is more restrictive on which characters are allowed in file names.

Cheers

EJ

I also run SMB on my NAS and use NAS backup process rather than TimeMachine.

For me these two are separate systems, best left alone.

It's worth keeping in mind that Apple effectively deprecated AFP in favour of SMB2 in Mavericks (10.9). While it's still available as a fall back option, it's use is not recommended. Next year when APFS replaces the 30 year old HFS+ file system AFP will not be supported.

Vendors like Synology and QNAP, used what is effectively an AFS hack to offer 3rd party Time Machine support. This will cease to work when your system is converted to APFS.

Greg2, thanks - I won't hold my breath waiting for a solution then and stay with samba. 

Cheers

EJ

I don't think I will update as iMac is quite old a bit iffy, I want all machines on the same or equivalent OS.

Would the updated OS on iMobiles notice against the desktop?

Any ideas how I can stop being asked to upgrade on my iPhone 5s and iPad mini if I choose not to change?

Don't know, but I don't like the latest iOS update.  I let my iPhone 6 and iPad Air2 do that update, and wish I hadn't!   My main gripe?

1.  Why, oh why, did they decide to scrap swipe to unlock and change to press Home?  That's change for change's sake IMO.  Also, I've noticed it turning Siri back on for no good reason that I can see - making me turn it off again.

Won't be upgrading to Sierra unless I have to.  It's only 'advantage' seems to be Siri for the Mac, but as I HATE Siri ...   

Sierra actually fixed a random boot error with my iMac where it would boot to a black screen necessitating a reboot or login remotely. So for me it was a big improvement. However I have noticed that my Time Capsule doesn't reconnect all the time. Aside from that a few random crashes with icloud its working ok for me. I also updated the mac mini I use as a NAS with no problems at all.

Too lazy to uninstall Sierra and revert to El Capitan, I've achieved a more or less stable system by:

- not booting any programs at logon; specifically, WD's drive utility, which is required to install their 2-bay mybooks amonghst others, has not yet been updated to comply with Sierra. This caused lockups at boot, on my MBP.

- switch NAS to SMB file transfer protocol. Solves the perpetually spinning ball when trying to directly access files from Finder; however prevents Time Machine use on the NAS. A colleague of mine has actually chosen to continue to run time machine succesfully, as long as he doesn't access files directly, so it seems either-or at the moment, until Apple solves this (if ever). YMMV 

- Finder still occasionally refuses to access the NAS under SMB, in which case I force restart Finder from the apple menu. Really hope this gets sorted in 12.1

- When directly working with folders on the NAS, there is an ocassional apparent clash between Apple and Synology access rights, preventing for instance the moving of folders. Disconnecting and reconnecting the NAS solves this, temporarily. Again, hope a future update of Sierra and/or DiskStation solves this.

- For those running Audirvana+, you have probably already noticed there is no direct mode under Sierra. Apparently you can hack direct support back in - but it's the type of hack that you'd have to do every time there is an update to the OS. Without direct mode, the Mac sounds somewhat compromised compared to what I'm used to, but as I'm not running a mac music server at the moment, not too bothered myself. For now.

Cheers

EJ

Dungassin posted:

Don't know, but I don't like the latest iOS update.  I let my iPhone 6 and iPad Air2 do that update, and wish I hadn't!   My main gripe?

1.  Why, oh why, did they decide to scrap swipe to unlock and change to press Home?  That's change for change's sake IMO.  Also, I've noticed it turning Siri back on for no good reason that I can see - making me turn it off again.

Won't be upgrading to Sierra unless I have to.  It's only 'advantage' seems to be Siri for the Mac, but as I HATE Siri ...   

Found a solution to the 'press Home to login' "feature.  Go into Settings>General>Accessibility>Home Button> Switch Rest Finger to Open ON.

Then you can login just by touching the Home button and not pressing it.   That assumes you've got Fingerprint login set up.

10.12.1 seems to have resolved AFP issues that were introduced with Sierra - but haven't tested time machine yet. A benefit of AFP is much faster file transfers between NAS and the Mac. 

Cheers

EJ

And WD has updated its drive utilities

Most important thing for any of us here who is using Audirvava+ to render music - macOS Sierra breaks the Audirvana+ Direct Mode, so to make it work again you need to copy  /System/Library/Extension/IOAudioFamily.kext from El Capitan. Caution: If you want to do the copying, use rsyn -arv command line, otherwise you will make your Mac stop working soundwise.

Peter Dinh posted:

Most important for any of us here who is using Audirvava+ to render music - macOS Sierra breaks the Audirvana+ Direct Mode, so to make it again you need to copy (using rsyn -arv command line) the /System/Library/Extension/IOAudioFamily.kext from El Capitan.

Or don't update to Sierra until Damien finds a solution

Interesting. I'm happy to be with Sierra as El Capitan seemed to have an unbelievably negative impact on sound quality in my system. Don't have a clue why but I was well aware that I had lost the magic and couldn't put my finger on it. Quick update with Sierra and parity is restored. So weird.

I have noticed that I can no longer run direct mode with Audirvana+ as Peter points out but everything is sounding good so I'm not too bothered at the moment and just look forward to the fix.

Jolly interesting, Mr, Mayor W. I will probably disable the Direct Mode and see if there is a magic.