Auto-m4b

Auto-m4b is a Docker container that automates audiobook format conversion by watching a designated folder for new files, converting multi-track MP3 books into…

  • Media Applications
  • Media Servers
  • Tools & Utilities
Auto-m4b is a Docker container that automates audiobook format conversion by watching a designated folder for new files, converting multi-track MP3 books into single chapterized M4B files, and moving the results to an output folder. It serves as the automated bridge between audiobook acquisition and metadata tagging, integrating with the beets-audible plugin to tag and organise converted books via the Audible API. Built on the m4b-tool framework, it supports MP3, M4B, M4A, and OGG input formats for homelab users building an automated audiobook pipeline.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

35/100 Low

Maintained
0last commit 870 days ago
Popular
52399 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data
Security check
85no serious findings, CI

Based on 4 of 5 factors.

Availability: platform listings confirmed today, links checked 45 days ago

GitHub stars
399
Open issues
35
Last commit
2024-07-04
Activity
stale

Checked 19 days ago - source: GitHub (seanap/auto-m4b)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Folder setup The container expects untagged audiobooks (MP3, M4B, M4A, OGG) to be placed in a 'recentlyadded' folder. It monitors that folder every five minutes, converts multi-file MP3 books into chapterized M4B files, and saves them to an 'untagged' output folder ready for downstream tagging. source

Fetched 38 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How should files be organized before auto-m4b converts them?

Create one folder per book, usually named after the book, and put multiple properly named MP3 files in it. auto-m4b watches for these folders of multiple part files.

Which folders does auto-m4b watch and write to?

It watches a /recentlyadded folder and saves converted chapterized M4B books to an /untagged folder. That output folder is intended for the beets-audible plugin to tag and organize the books.

Will a single MP3 audiobook get multiple chapters?

No, chapters are based on the MP3 tracks. A single MP3 file becomes a single M4B file with one chapter, and poor file names can produce poor chapter names.

Can auto-m4b be used in a download pipeline with SABnzbd and Readarr?

Yes, an Unraid user describes using it in a Readarr and SABnzbd pipeline to convert downloaded audiobooks into single-file M4B files.

Answers sourced from forums.unraid.net, github.com, www.reddit.com

Community

Collected 53 days ago - public community threads