Organising music by libraries

[nbpf]

(20-02-2016 16:08)xtoph Wrote:  Sure genre is a standard tag, but its values are not normalised. It is actually a mess with an infinite number of genres and their (spelling) variations.

I use MusicBrainz for tagging, so this tag is filled already, but unsuable (my point of view). I could correct it, sure, but then I would define a custom tag with a handful values, which I want to avoid

My idea was a bit different. Just like with physical media, I put albums according to the kind of music (e.g. Classical, Jazz)

I so have 2 top folders (say /Music/Jazz and /Music/Classical) bot defined in the contentDir

I though it would be a good idea to (at scan time) read the top-level folder (/Music/Jazz), extract the leaf folder (Jazz), and assign this value to a dynamic tag (let's call it Library) for all files contained in this folder. I would then have a new way of navigating my Library

I have seen such requests in the past, e.g. from people willing to have the possibility for each family member to consider only their own songs. Most of the answers are multiple instances, multiple VM's, or a refactoring, all being heavy solutions for a simple problem

Would this be a possible solution?

Apart from the fact that your approach leads to album duplication for those albums which are both "classical" and "jazz" (and tags are there exactly to avoid this and other limitations of folders as means for organising data collections): if you are happy with giving all the files in /Music/Jazz (/Music/Classical) the same value for a "genre" or "library" tag, you can do this very easily with lltag from the command line, please see http://home.gna.org/lltag/. Of course, you can also run a cron job and have lltag run once a day or once a week in the background. Best, nbpf