22
submitted 9 months ago* (last edited 9 months ago) by ProtecyaTec@lemmy.world to c/selfhosted@lemmy.world

I've started working with Media Servers recently and am starting to get acustom to Jellyfin. I'm using Book Lib Connect and AAX Audio Converter to download and convert my purchased Audiobooks.

I would like my Audiobooks to retain chapters, but I'm not sure the export I'm getting from the above is fully compatible with Jellyfin. Here's what I've tried so far:

Audiobooks

  • Author
    • Book
      • (01) Opening Credits.m4b
      • (02) Chapter 1.m4b
      • etc.
      • Book.txt
      • metadata.json
      • chapters.json

I also have the full m4b file and the aax file in an ignored folder at the top of the book.

Book.txt contains the author, title, narrator, publish year, description, duration. Separated by new lines.

metadata.json contains specific information like purchase date, product #, author #, SKU.

chapters.json contains the actual chapter titles. chapter length, start offset.

Any ideas on how I can get Jellyfin to read the json files? Do I need to write a conversion script into some other file type? Maybe Jellyfin isn't the right software for Audiobooks?

I'm open to ideas, suggestions, or any other advice.

you are viewing a single comment's thread
view the rest of the comments
[-] singularity@lemmy.ml 8 points 9 months ago

I agree. This is the best choice for audio books.

[-] vbatts@lemmy.ml 6 points 9 months ago

Big agree. I tried to make jellyfin acceptable for a while and life with audiobookshelf is just so good. https://github.com/advplyr/audiobookshelf

this post was submitted on 03 Feb 2024
22 points (92.3% liked)

Selfhosted

40199 readers
246 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS