u/Plane_Chard_9658

Revisiting old iPod audiobook workflows reminded me how many tiny format decisions are baked into this.

Music is easy enough. Audiobooks get weird:

- MP3 chapters often show up as music tracks

- M4B works better as an audiobook, but only when the metadata is right

- cover art sometimes vanishes depending on how it was embedded

- one long file is easier to resume, chapters are nicer to navigate

- splitting back into MP3 chapters is still useful for some old devices and car stereos

- the same file can behave differently in Apple Books, iTunes/Music, Rockbox, or whatever else

My process is tag editing, ffmpeg, and copying the file to the device to see what it actually looks like. It mostly works. There really should be a more direct "prepare this as an audiobook" path.

How are you preparing audiobooks for an iPod these days?

- one big M4B?

- one MP3 per chapter?

- MP3 album with track numbers?

- Rockbox-specific setup?

- some other tagging workflow?

Disclosure: I am building a free tool for DRM-free audiobook files that can build a chaptered M4B, fix cover and metadata, and split M4B back to MP3 chapters when an older player needs that. No link yet. I want to know what old-device users actually need before the first version ships.

What format gives you the least trouble on your iPod?

A small but stubborn audiobook problem keeps biting me.

Sometimes I have a book as a folder of audio files: ripped CDs, public-domain downloads, old MP3 chapters, or a long recording someone split into pieces. It plays. In an audiobook app it still feels wrong:

- the player treats it like a music album

- chapters are just filenames

- cover art is missing or different in every app

- author and narrator metadata sit in the wrong fields

- progress and resume behavior depends on the app

- moving it between Apple Books, BookPlayer, Plex, or Audiobookshelf surfaces a different problem each time

Conversion is rarely the hard part. The hard part is making the result behave like a book.

I do this with ffmpeg and a tag editor. They work. It still turns into a little craft project every time: sort files, merge, add chapters, embed a cover, fix title and author, open it in a player, find one thing wrong, start again.

Does anyone else here actually deal with this, or do most listeners just live with folders of MP3s?

Disclosure up front: I am building a free tool around exactly this workflow. DRM-free files only. MP3, M4A, etc. into a chaptered M4B, plus cover, metadata, and an export the player will not argue with. No link yet, since I am trying to confirm this is a real shared pain before I overbuild it.

What is the part that annoys you most when you turn loose audio files into a usable audiobook?

Moving a personal audiobook collection into Audiobookshelf, and the same annoying step keeps tripping me up before files ever reach the server.

Audiobookshelf is fine. The pain is everything I do to make a folder of audio actually look like a book in the library:

• MP3 folders that should be one book
• M4B files with no usable chapters
• covers that show in one player but vanish in another
• series and book number missing or inconsistent
• empty narrator fields
• chapter names like "Track 01" instead of real titles

Right now I bounce between ffmpeg, a tag editor, the occasional m4b-tool command, and a lot of squinting at the player to see if anything stuck. It works. It also feels like way too many steps for something that boils down to "make this behave like a proper audiobook before I import it."

Is the pre-import cleanup common around here, or is my library just messier than most?

How do you handle it today?

1. m4b-tool?
2. mp3tag, kid3, MusicBrainz Picard?
3. ffmpeg scripts?
4. Audiobookshelf's own metadata tools after import?
5. something else?

Full disclosure, I am building a free tool around this cleanup workflow. DRM-free audio in, chaptered M4B out, cover and metadata fixed before import. No launch link, no signup. Mostly I want to know what actually hurts for people maintaining their own libraries.

If you could fix one part of the pre-import workflow, what would it be?