As a long term Apple user, I’ve seen a lot happen with Apple’s services division over the past 20 years. When they work, they bring me great joy and they are absolutely worth the money. But when they don’t, they are a bigger pain in the arse than South Western Railways and Network Rail.
Having moved over to the 16″ MacBook Pro, one of the first things I did before the move was:
- Create a current, up-to-date Time Machine backup
- Copy all data – including Apple Photos and Apple Music/TV to a separate hard drive and copy them back over manually
iCloudy with a chance of rain
When the new machine was running, I copied all my data back over. The first problem was that because I use iCloud Photo Library, Apple immediately enables it even if you don’t want to use it (a bug, perhaps?) – creating a Photos library catalogue. About 99% of having copied the data from the separate hard drive to the Photos directory on the new Mac terminated and told me there was already data there, and then terminated the transfer.
So I thought I’d give Apple the benefit of the doubt and download all my photos and videos stored in iCloud Photo Library (around ~130Gb) and start a new catalogue from scratch. It did work, but it takes forever for the Apple Photos app in macOS Catalina to do its stuff before downloading can happen. It took about 3-4 hours in total to download 10,443 photos and 463 videos. Speaking of iCloud Photo Library – Apple had better start considering offering a 4Tb tier. I’m nowhere near that level yet, but as storage becomes cheaper on MacBook Pros, iMacs and Mac Pros, and as the cameras improve on iPhones, people will start putting everything in iCloud. Obviously I back everything up religiously to Time Machine, Backblaze, Google Drive and separate hard drives, but as we’ve just discovered – it doesn’t always work out the way you think it does. At least I can access all the old photos from the backups manually.
What is interesting to note is that with macOS Catalina’s Photos app, Apple has made some internal restructuring to the package contents of the catalogue. No longer is there a masters directory containing your original files and filenames, but a directory called originals which contain the original files. But with Apple-encoded filenames. Original filenames appear to be stored as metadata within an internal, locally-stored Apple database.
Apple Music is just as buggy as iTunes
With regards to Apple Music, I originally didn’t have any problems copying that across. The only real issue is that the artwork to albums and playlists was missing. I tried everything I could to try and get them back through the Apple Music app on Catalina, but no joy. The closest I got was to nuke everything in the Music directory and copy back over from the Time Machine backup. They seemed to work – except that every single file was available to download through iCloud. Downloading only doubled the amount of space being used by macOS.
So I completely deleted my Music directory again and tried to get Apple Music to start afresh. Except it didn’t. It picked up my account details and some album artwork straight away. And iCloud Errors galore.
At one point, Apple Music got REALLY confused.
So I did a bit of digging around. There aren’t many articles about Apple Music on Catalina and how to fix problems. But this is how I “fixed” mine – where “fixed” was to get Apple Music to start from scratch – newly created directory, no files downloaded, all music stored in iCloud – then start to download music as an when needed. Over 56,000 tracks is a bit much.
I hate Windows registry, but Apple’s Library can just as bad…
Having closed Apple Music and deleted the Music subdirectory from within the Music directory in my home directory, I opened a terminal, I navigated to
and nuked any files or directories that mention iTunes or Music in their file/directory names. This gets rid of any caches built up by Apple Music/iTunes. So it should forget anything you’ve done so far. But this isn’t enough. I then changed to:
and nuked any files or directories that mention iTunes or Music in the file/directory names. From there I fired up Apple Music and was greeted by the Apple Music welcome screen. And everything worked as expected from that point onwards. I downloaded my playlist music just fine, along with a number of albums. All good. And everything has been fine for the past 24 hours.
More internal local changes
Again, with macOS Catalina, Apple has re-arranged the internal file structure for Apple Music. My backups had an iTunes directory with all the media stored in there, and a Music directory which had a single package file within it. When starting Apple Music anew, there is a Music subdirectory containing the same package, followed by a media directory.
Within the Media subdirectory, you can see that (when arranged alphabetically) Apple Music files are stored separately from purchased/uploaded music.
When attempting to get things working from backup, it seemed Apple Music was completely confused. I’ve got to say, Apple, that you’ve made a right pig’s ear of this and I’m not happy. When I’ve set-up Apple Music on my work Mac, it was fine because I hadn’t any existing files. But if I had brought them in, I’m sure I’d suffer similar problems.
What is the point of backups if they don’t work properly – especially if the issue is being caused by bugs or changes made by the same company you’ve bought the hardware AND software from?
macOS Catalina – a steaming pile of horse poop
Regardless of whether its new hardware or existing hardware, the macOS Catalina experience has been awful. My work Mac Mini (2018) was bricked by the update and required a logic board replacement. The 2018 MacBook Pro was fine, but clearly the backups I’ve been making haven’t been suitable for transferring to a new machine – or even to the same machine because of all the changes between Mojave and Catalina.
A while back, I spoke to some people from a VERY big international games company, and the problems they were having with Catalina were numerous. Don’t forget that Catalina drops support for 32-bit apps. And many of them are games.
There are so many game titles which are all 32-bit, and not compatible with macOS Catalina, making Steam for macOS pretty redundant right now. At least there’s Apple Arcade, right?
I do love my 16″ MacBook Pro, but I want to see Apple seriously step up their services/macOS game because right now it’s simply not good enough.