On the issue of portability of music purchased from the iTunes Store, reader Hanno zur Loye writes in:
I read the article by Christopher Breen (“How to deal with two Apple IDs, well, kind of”) and I was hopeful and confused at this statement of “…if we’re talking only about music you’ve purchased from the iTunes Store in the last several years, that’s not a problem as music is no longer protected and can be played with either ID.”
I just realized that due to a change in email addresses, I have two Apple IDs and have purchased music on both and apps only on the later one, since that came with the iPhone that runs on the new email address. I just tried to listen to purchased music and it won’t let me play it unless I sign in on the Apple ID that purchased it. So it seems that the music is protected? Or am I doing something wrong.
I suspect you’re a long-time iTunes Store consumer because this is something that should only arise if you purchased music before 2009. Music sold from iTunes Store’s inception through 2007 was all protected by Apple’s DRM (digital rights management) encryption. Some labels began allowing Apple to sell without DRM in 2007, while the entire music catalog was converted in 2009.
Dave Price writes in with a quirk of Photos related to exporting images he’s edited:
In the new Mac Photos app, I found that the only way to export photos and keep the original date that the photo was shot is to export the original. So after carefully cropping and adjusting the many editing options, how can I export the edited photo without losing the creation date?
It’s a strange omission from Photos for OS X, though you could think of it as philosophical in nature: Apple only exports a newly created version, rather than one that’s the original, modified. That’s probably too existential for software, however.
Sarah Amundsen has a very reasonable query about movies:
I want to download French language movies on iTunes, but will be forced to create another Apple ID for this. I am concerned that I will potentially lose my previous iTunes (music and movies) bought under my original ID, or will have other problems. Can you advise how people do this? It is completely inflexible that Apple seem to assume that people don’t travel and don’t want content in >1 language!
This is one of those peculiar situations in which we live in a fully interlinked global economy with a worldwide super-fast computer network, and yet old-fashioned licensing agreements, cartels, and other rules prevent such simple things as offering easy and legitimate payment for media created or sold outside our home country.
Nelis van Nahuijs wants to jumpstart security but has a question about transitioning:
After reading your article about strong and/or unique passwords, I wonder if you have some advice to make a transition to 1Password? What is going to happen with all the passwords I’ve already in place? I use iCloud passwords a lot; should I stop with that practice, and what happens with these passwords after switching to 1Password?
I have a refurbished 27ʺ iMac. I tried to install Adobe Creative Cloud on it and I got the error code that it could not be installed on a case-sensitive drive. So I backed everything up using Time Machine and an external hard drive and formated the drive to Mac OS Extended (Journaled). But when I restored using Time Machine it went back to Mac OS Extended (case-sensitive, Journaled). How do I make this computer non-case-sensitive?
You are not the only person to encounter this, but how frustrating when you weren’t the one who caused the problem. Case sensitivity is an option in formatting, because Unix and Unix-similar operating systems always allowed case sensitivity. That is, they could distinguish between files that were “spelled” identically, but used a different mix of upper-case and lower-case letters. In case-sensitive filesystems, file.txt, FILE.TXT, and File.txt are all unique names.
Each version of OS X in recent years has been more efficient and often sheds space after installation rather than demanding more. However, Thom Vagt found the opposite: an upgrade led to less reported remaining space.
On my late 2013 model MBP which was running Yosemite 10.10.5, my available disk space went from 230GB of free space to 183GB. I have run disk utility and it tells me all is fine with the SSD 1TB disk.
I’ve seen similar problems at times with my various Macs, and so have many users. You should pinpoint where the free-space reporting error is first, however.