{"id":44717,"date":"2024-09-04T15:15:19","date_gmt":"2024-09-04T19:15:19","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=44717"},"modified":"2024-09-04T15:20:24","modified_gmt":"2024-09-04T19:20:24","slug":"apples-magic-sound-file-renaming","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2024\/09\/04\/apples-magic-sound-file-renaming\/","title":{"rendered":"Apple’s Magic Sound File Renaming"},"content":{"rendered":"

Shamino<\/a>:<\/p>\n

\n

For those who are unaware, in macOS 11 (aka “Big Sur”), Apple changed all of the standard system sounds [names].<\/p>\n

[…]<\/p>\n

The interesting thing is that if you go to look for the actual sound files (in \/System\/Library\/Sounds<\/tt>), you’ll find that the filenames are the same as the old names.<\/p>\n

[…]<\/p>\n

There is a application extension, \/System\/Library\/ExtensionKit\/Extensions\/Sound.appex<\/tt> on my (macOS 14 \"Sonoma<\/a>\") system. It is apparently a Quick Look<\/a> plugin, but looking inside its package, I found a mapping table named AlertSounds.loctable<\/tt>. And this file is a binary property list file with a changed file extension. Dumping the contents of the file reveals the mapping. And not just one, but a big array of localized mappings[…]<\/p>\n<\/blockquote>\n

“Basso” is now “Mezzo,” and “Sosumi” is now “Sonumi.” These are not just renamings; the sounds themselves are different, sometimes very different, as in “Purr” becoming “Pluck.”<\/p>\n

I don’t really understand why they chose to maintain “compatibility” by changing the meanings of existing sound files, instead of adding the new sounds under new names (and perhaps hiding or deemphasizing the legacy ones, as they do with desktop pictures).<\/p>\n\n

Previously:<\/p>\n