I have a lot of audiobooks in my library and navigating them has become a major issue for me with MM5. In MM4 I used "Magic Nodes" and a naming scheme (series - position - title) to organize series together. Some of my books are single files (mp3, m4b, etc.) while others are split on chapter, disc, or track boundaries.
Ideally I would like a mechanism to track multi-hierarchical series information (i.e. a books might be in a series that is part of a larger series, and might be in multiple separate series (see the Discworld reading order
https://en.wikipedia.org/wiki/Discworld ... opped).jpg to get an Idea) embedded in files, however I get that there is not a widely accepted standard for this so an intermediate step may be best.
I see a few options, but am more than open to alternatives.
1 - Use a tag or tags available in most audio formatas to map to use the existing "series" subnode
2 - Use an existing or custom tag or tags to encode series information and expose in either the existing "series" subnode or a new subnode.
3 - Add a mechanism for users to define a custom tree of subnodes and populate it either via rules or manually. (similar to playlists or "magic nodes" depending on how it is done)
I have a lot of audiobooks in my library and navigating them has become a major issue for me with MM5. In MM4 I used "Magic Nodes" and a naming scheme (series - position - title) to organize series together. Some of my books are single files (mp3, m4b, etc.) while others are split on chapter, disc, or track boundaries.
Ideally I would like a mechanism to track multi-hierarchical series information (i.e. a books might be in a series that is part of a larger series, and might be in multiple separate series (see the Discworld reading order [url]https://en.wikipedia.org/wiki/Discworld#/media/File:Discworld_Reading_Order_Guide_3.0_(cropped).jpg[/url] to get an Idea) embedded in files, however I get that there is not a widely accepted standard for this so an intermediate step may be best.
I see a few options, but am more than open to alternatives.
1 - Use a tag or tags available in most audio formatas to map to use the existing "series" subnode
2 - Use an existing or custom tag or tags to encode series information and expose in either the existing "series" subnode or a new subnode.
3 - Add a mechanism for users to define a custom tree of subnodes and populate it either via rules or manually. (similar to playlists or "magic nodes" depending on how it is done)