This repository has been archived by the owner on Jul 29, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 38
Audiobooks #148
Labels
Comments
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 For a package, this means:
This is more of a UX question than a technical one:
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The text was updated successfully, but these errors were encountered: