[FEATURE] Audiobook support

[Guscal]

i feel there is a lack of an all in one solution maybe stumps is that? maybe considered for the long run in a much later update

Edit by @aaronleopold to add sub-issues:

• Audiobook support phase 1: DB representation #279
• Audiobook support phase 2: scanning and metadata
• Audiobook support phase 3: playback, session persistence
• Audiobook support phase 4: UI playback and settings
• Audiobook support phase 5: Native client UI, e.g. mobile app

To be clear, I won't be making these a priority. I will try to tackle each phase in an isolated minor version. E.g. phase 1 by 0.2.0, phase 2 by 0.3.0, etc. I wouldn't expect anything usable until multiple minor versions, as my focus will remain on digital books.

[aaronleopold]

This is definitely something I've considered a few times since starting Stump, and coincidentally something that was recently chatted about on the Discord server. In general, before I would seriously consider the effort of adding audio support of any kind, I would want to reach some form of stability in what Stump currently can/aims to do with digital books. Adding too much before that point would just make development and maintenance harder IMO, and I don't want to pollute Stump with more unfinished features just yet 🙂 There are also some aspects that I would want to very clearly define before starting, since the work involved would be VERY large and I don't want to have to plan or get stuck on a question in the middle of integration more than is necessary. For example: how would the UI change, would we want a clear separation of media types or should audio and digital books be allowed in a single library, how should the DB model(s) change to balance minimizing breaking changes while facilitating an easier implementation, are there good audio metadata parsing libraries available in Rust (I don't feel like creating one myself on top of all this), etc.

TLDR; in the long run, yes, I'm open to considering it