Flac naming convention.
Reply #3 – 2012-08-09 10:15:59
In the even tags get screwed up [...] I obviously wouldn't re-rip anything but it would seem there might be advantages to having each file with all pertinent info IN the file name. File and folder names are limited in their length, so one cannot store all meta data therein. Assume you would 'backup' some tags into the file/folder name, you will probably loose information in case of restore. Because file/folder names allow only limited letters/symbols (or you likely run into trouble if you use exotic symbols and are going to share your files via different operating systems and/or file systems). Moreover, one will probably change tags from time to time (constantly, I would say, think of error correction, ratings, playback statistics, additional information, whatsoever). I don't want to change file/folder names too, because this often messes up playlists etc. And it is just inconvenient. By that, one has to do a real backup of the metadata and/or the collection itself. Discussion on that does not fit here, IMHO, it can be found anywhere online ... Just one hint: you can export metadata, only, and save it from time to time at a save location. Nevertheless, I take care of a proper naming scheme and a hierarchically structure. I think my scheme is not so special to post all the details, I will just give one example for regular albums$left(%album artist%,1)\%album artist%\%album%\%track% = %artist% = %title%.flac After ripping I sanitize the folder/file name (e.g. remove all special chars) and then the file/folder name will _never_ change again, regardless of tags. I use the equal sign ('=') to separate different fields in the file name, because it's very seldom found inside the content of a tag field and by my knowledge it's compatible with a wide range of operating systems.