FLAC files should not have ID3 tags for metadata. But some programs unfortunately have added and they can be hard to remove. FLAC metadata is properly contained in VORBIS COMMENT tags, as used by most FLAC encoder programs.
Yip, luckily I’ve not purchased anything with id3 tags in some time. Whilst e-tailers still generally do a crappy job with metadata it seems they’ve at least stopped embedding id3.
Gary, can you pls explain more about the impact on roon’s behavior if having ID3 inside flac? To be honest I’m not sure if I have ID3 inside my files. Nearly all of them ripped with dB-poweramp and subsequently cleansed by TAG (appropriate software for individual correction via iMac) and for harmonization mass changes I used media monkey (unfortunately only on PC but great for this specific task).
All over all I can’t say that I have a mayor issue, but I also from time to time see some room for meta data improvement surfing my CDs in roon.
So do you think it’s an issue for roon detecting ID3 within my files?
doubt it, not sure whether or not Roon would read them and if so whether it’d favour id3 over vorbis comments, however, I can tell you that the FLAC toolset doesn’t anticipate nor cater for it - it won’t even run an integrity test on a FLAC file with id3 headers.
That’s exactly my thought. I can somehow live with the situation without 100% formal consistency. Especially because my files have to be that robust feeding roon and sonos in parallel. In my implementation the metadata issue is close to perfect for my requirements.
I invested a lot in metadata cleansing but focused only on the most important tags for me
Album title
Album artist
album image
Song title
Song title artist
Compilation y/n
Composer (because I have a lot of classical music)
In the composer I have a home made issue: Before roon I organized my composer entries by “year name” because then I could easily see my composers in a historic sequence and composers of non classical further down could be ignored. Now I think I have an issue in roon properly feeding the “works” category because roon obviously doubts the “year name” entry in composer but as I mentioned I’ m not sure about root cause. Unfortunately at least for me it’s not 100% clear how Roon deals with which meta date fields and how I can contrive best in getting it most of it in my set up.