README states: "It should work seamlessly on any single file or multi-file book under a single book folder" and that multibook = true is only needed for "older, multibook collections." My case is a single real book split into 34 sequentially-numbered chapter mp3 files in one folder — exactly the scenario the docs say should work by default (multibook=0 in my config, as documented).
Instead, booktree processed each chapter file as its own separate "book," searching Audible using each chapter's individual filename/title rather than grouping the folder into one book search.
Environment
- Image:
myxdvz/booktree:latest (pulled July 2026)
- Config flags:
multibook: 0 (default, per docs this should be correct for this case)
Folder structure
The Devil Wears Scrubs/
├── The Devil Wears Scrubs - 001 - Chapter 1.mp3
├── The Devil Wears Scrubs - 002 - Chapter 2.mp3
├── ... (34 total chapter files)
├── The Devil Wears Scrubs-Cover.jpg
Observed Behavior
Verbose log shows each chapter processed independently, e.g.:
Processing: The Devil Wears Scrubs...
Searching Audible for
asin:
title:The Devil Wears Scrubs 004 Chapter 4
authors:"Freida McFadden/Gabra Zackman"
...
Found 0 Audible match(es)
Resulting log file contains 34 separate rows, all with book: The Devil Wears Scrubs, each independently failing to match (0 MAM, 0 Audible) because the search title includes the per-chapter suffix (004 Chapter 4) rather than just the book title.
Expected Behavior
Per README, this folder structure (multi-file book, single folder, multibook=0) should be grouped into one book-level search using the folder/base title, not searched per individual chapter file.
Additional note
Author field also has a delimiter issue in this same file's metadata ("Freida McFadden/Gabra Zackman" — slash-delimited, likely narrator misattributed into author field) — separate concern, mentioning in case it's relevant to how the grouping/parsing logic reads this folder's files.
README states: "It should work seamlessly on any single file or multi-file book under a single book folder" and that
multibook = trueis only needed for "older, multibook collections." My case is a single real book split into 34 sequentially-numbered chapter mp3 files in one folder — exactly the scenario the docs say should work by default (multibook=0 in my config, as documented).Instead, booktree processed each chapter file as its own separate "book," searching Audible using each chapter's individual filename/title rather than grouping the folder into one book search.
Environment
myxdvz/booktree:latest(pulled July 2026)multibook: 0(default, per docs this should be correct for this case)Folder structure
The Devil Wears Scrubs/
├── The Devil Wears Scrubs - 001 - Chapter 1.mp3
├── The Devil Wears Scrubs - 002 - Chapter 2.mp3
├── ... (34 total chapter files)
├── The Devil Wears Scrubs-Cover.jpg
Observed Behavior
Verbose log shows each chapter processed independently, e.g.:
Processing: The Devil Wears Scrubs...
Searching Audible for
asin:
title:The Devil Wears Scrubs 004 Chapter 4
authors:"Freida McFadden/Gabra Zackman"
...
Found 0 Audible match(es)
Resulting log file contains 34 separate rows, all with
book: The Devil Wears Scrubs, each independently failing to match (0 MAM, 0 Audible) because the search title includes the per-chapter suffix (004 Chapter 4) rather than just the book title.Expected Behavior
Per README, this folder structure (multi-file book, single folder, multibook=0) should be grouped into one book-level search using the folder/base title, not searched per individual chapter file.
Additional note
Author field also has a delimiter issue in this same file's metadata (
"Freida McFadden/Gabra Zackman"— slash-delimited, likely narrator misattributed into author field) — separate concern, mentioning in case it's relevant to how the grouping/parsing logic reads this folder's files.