Feature Request - Back cover text feature
spammy1337 opened this issue · comments
I would love to see a feature that presents a brief text about each audiobook, like the backside of many physical books but in a digital format.
Perhaps just "scroll" the album art sideways to flip to "backside info"-pane that presents the formatted info in a nice and easily readable manner.
That way the user could read a brief about each audio book before listening, somewhat analogous to the plex movie trailers feature.
I would assume a separate text-file could be used for each audiobook, perhaps a fixed name, "Chronicle_about.txt", placed in the specific audiobook folder.
Such text files would be stored in each audiobook folder, pretty much the same way as album art is managed today, while being created and maintained by the user.
If the file isnt there, then just keep Chronicle's current presentation, no warning or nothing, this extra text file should be completely optional!
I have little knowledge of what exactly the plex server is providing in terms of file access, if its possible to read the suggested text file thru plex, but i would very much want a central solution that works for all clients, even if it means a extra "audiobook-data"-folder in the plex webserver-folder. :)
There are many ways to markup such text file, both to properly format the output as well as highlight specific "variables", like author and so on, so not all of each text file must be only "backside-text".
Other useful nuggets of data might be metadata like collections, author & co-authors, the name of the voice actor reading it and so on, and they could also be used for the library browsing experience, like listing only books by specific voice actors or only specific genre.
This feature request is quite massive and will not be a simple patch, but i do think its a "killer feature" that would make Chronicle stand out more from all those other audiobook-players. :)
Chronicle supports using the "review" field in Plex to include a text description about the book. See screenshot below- does this support what you're imagining?
