More > JRiver Media Center 23 for Mac
MacOS High Sierra
Lodewijk_Ramon:
Magic_Randy, thanks for your reply to my question. I am somewhat surprised though that the MC-team didn’t test MC running on a machine with MacOS 10.13.
A question at Brian: Why skip 10.13 and wait for 10.14. We don’t know anything about 10.14. I miss a logical basis for the suggestion.
I think that I am going to upgrade after securing a full backup. I’ll keep you informed about the outcome thru this forum.
Hendrik:
--- Quote from: blgentry on September 26, 2017, 09:40:40 am ---Even so, isn't FAT32 a better choice since you can actually write to it on a Mac without using a questionable 3rd party shim?
--- End quote ---
FAT32 has serious limitations though, and noone really should be using it anymore. exFAT would be a good option as well, but support for it is quite limited among other operating systems (no clue if OSX supports it, even).
NTFS is probably the best you can do if you need to share between all three major OSes, the open-source NTFS drivers are pretty good now.
Awesome Donkey:
--- Quote from: Hendrik on September 27, 2017, 03:31:01 am ---exFAT would be a good option as well, but support for it is quite limited among other operating systems (no clue if OSX supports it, even).
--- End quote ---
Yes, macOS supports exFAT.
The NTFS-3G driver for Mac and Linux works rather well. :)
blgentry:
--- Quote from: Hendrik on September 27, 2017, 03:31:01 am ---FAT32 has serious limitations though, and noone really should be using it anymore.
--- End quote ---
What limitations give you pause? I've never had any issues with FAT32, except not being able to create files of over 4GB. For music files this isn't a problem.
--- Quote ---exFAT would be a good option as well, but support for it is quite limited among other operating systems (no clue if OSX supports it, even).
--- End quote ---
ExFAT is kind of the bastard child. It's mostly an MS focused file system. Linux and OSX both support it and I've tried it. It has odd issues with characters that are supported and seems to have a strange issue with time stamps as well. I probably will not be using it in the future. I'm probably going back to FAT32 for "portable" file systems.
--- Quote ---NTFS is probably the best you can do if you need to share between all three major OSes, the open-source NTFS drivers are pretty good now.
--- End quote ---
I find the idea abhorrent. It was never designed to be "open" in any way. Sure it's more advanced than FAT, but OSX doesn't support it natively and I'm very reluctant to load any foreign kernel drivers under OSX. For all of you guys that use Windows as your standard, perhaps this makes sense. For those of us who stay away from all MS products on purpose, using NTFS is a step in the wrong direction. I think we have both shown our biases now. :)
Brian.
Awesome Donkey:
Actually, macOS *does* support NTFS natively. By default it can read NTFS volumes, and via the Terminal and fstab you *can* enable read/write for NTFS volumes without needing third-party drivers. But it's a bit of a PITA to set up, it's considered experimental/unstable and it's easier to do it with third-party drivers (which can also be faster than the native support), e.g. NTFS-3G.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version