I’m not a proponent of proprietary formats. Proprietary tags in HTML were a Bad Thing™ which took MS a particularly long time to get rid of.
Although Apple at least allowed MP3s to be played on their devices, like MS with WMA, they insisted on having their own version (and then charging CD-quality prices for it). The same goes for CD-quality music. Instead of allowing FLAC to be played natively on iPods, Apple had to have ALAC, which seems to be so little different from FLAC as to be pointless.
In recent news, it seems that FLAC might have a foot in the door with iOS 11,
but whether it turns out that iTunes will play FLAC files is quite another matter.
A few days ago, about six months late, I found that FLAC 1.3.2 had been released, and duly downloaded a copy to use with Exact Audio Copy. But having been around in the days when DOS was the OS, I couldn’t help but have a go with this new version of FLAC from the command line.
I had to work out how to do certain things in Powershell, which are no longer intuitive (oh for the days when file and directory names could be no more than eight characters), and used it to test the Linde-Consort’s album of trio sonatas by Bach and Handel, and to convert it to wav. I was hoping I might be able to fix some problems which were obviously issue with an aging CD.
When I woke up this morning, I had a realisation that I can convert FLAC to wav, and then wav to ALAC, thus meaning that my iPod Touch is not largely redundant as I continue to focus on CD-quality music.
I’ve been re-ripping my CDs to ALAC anyway, and can, say, convert rips from my old CDs as well.
Admittedly, there may be a program which will do such conversions without the intermediate step of reconstituting wav files, but I’ve usually assumed that such programs are for Macs, not PCs.