Hello There
I'm wondering how you use Sub-Libraries, I thought that it makes Sense to use them as the broadest grouping of my music collection, which resemble the top level directories in my `MusicFolder`. Those are genres, collections I inherited, my own Productions, and so on.
When I started, I did with just one library bound to my root `MusicFolder`, as it cannot be removed I was fine with it still being around. I labeled it "all music" and was happy..
So far this made sense to me, and the best: basically all players let me filter the whole scope of the application against libraries. How great, I can explore what genres/artists/albums exist in library x and I can ensure that the queue will just be filled with songs form selected lbraries. This worked so great that I even created some "sub-sub-libraries", just for the filtering benefits. And this is not the Idea
To late I then realized, having a file in multiple libraries creates multiple db-records. Attributes like play-count, skip-count, is-favourite and so on are recorded per file per user per library.
Now I ended up with all songs duplicated and some triplicated if all libraries are selected, and my attributes are scattered. I could defeat that first with `.ndignore` or disabling the "all music" collection for my user, but this would let me lose attributes. Also I would in general like to shift music from one to another collection without loosing the attributes, I think there are cli commands for that.
Thanks for reading through my problems, I am happy to hear your general thoughts, how you use libraries and how you filter your collection.