Audiobooks

[llemeurfr]

Develop a parser and navigator for audio publications and update the test app accordingly.

Audio publications are imported as zipped files containing a RWPM + cover + audio files (mp3, aac or Opus).
The manifest has a type property = audiobook
The manifest needs few processing before it is exposed by the streamer (media url maybe adjusted).
The navigator takes the form of an audio player, showing the cover, with simple user actions (play pause, next / prev track, jump +- 10 sc).
An optional ToC is usable to jump to different locations.

chapters vs tracks: to be discussed; tracks may not follow chapters. If the ToC exists, it would be sensible to implement a next / prev chapter rather than track.

[HadrienGardeur]

It's worth referencing the Audiobook profile in this context: https://readium.org/webpub-manifest/extensions/audiobook

For a manifest, most of the parsing should already be covered, except maybe duration and alternate in readingOrder.

For a package, this means:

• detecting that the package is an audiobook
• parsing the manifest at the well-know location (manifest.json)
• handling LCP (there won't be a separate encryption.xml file, everything should be directly in the manifest)

chapters vs tracks: to be discussed; tracks may not follow chapters. If the ToC exists, it would be sensible to implement a next / prev chapter rather than track.

This is more of a UX question than a technical one:

• will the test app include buttons to do this?
• what's the behavior at a system level?
• if a TOC is present, should those buttons skip between chapters (if possible at a system level) rather than tracks?