As a licensed user of Bliss I would like to have the ability to manage multiple libraries based on a parent directory for each library, and have rules that could be applied to all directories or selected specific directories so that I can manage different types of audio files uniquely.

The specific use case I have for this is managing Audiobooks differently from music files.

I’ve tried to address this by running multiple docker images of bliss on my computer. It works, I have multiple instances running and I change the ports so they all can run at the same time, but the license only works on one of the instances.

Ideally, I would be able to create a “library” called “Audiobooks” and another called “Music.” Each would have a distinct top level directory. Only one directory could be defined per Library, and the use of that directory would be unique (you could not use that directory for another Library.) Other Libraries could not consist of child directories of another Library.

Rules by default would be applied to all libraries. A user could change a property on a rule to indicate to which libraries the rules apply. Order execution would be most-specific last, meaning “all library” rules would run first, followed by per-library rules. This would enable users to make specific changes where needed after the broad rules run.

The use case for this would that I’d want missing info, images, tags, etc. to be applied to all. But then I’d want the file naming and reorganizing for music to be artist > album > track while I’d want the audiobooks to be album>track_artist.