-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Overdrive Chapter Metadata #24
Comments
I'm not sure if this is the same issue you were having, but the repo did offer a way to add customized chapters as a second step in the conversion & merge process. However, this didn't work for me in practice because (I think) there was a typo in the formatting of the command to apply new chapters. I just submitted a PR that fixes this issue so that at least you could apply a custom chapter list as second step in your conversion process to get them set correctly. (if you found another way to do this since the time of your original post, I'd be interested as this is a part of my process I'm trying to improve as well). What I'm doing now is...
It's not the most efficient process, but it does work. |
I love this docker and the automated workflow you have put together. The only thing I am struggling with is the Chapter Metadata.
m4b-tool has the capability to read the Overdrive Metadata, but even after removing "--use-filenames-as-chapters --no-chapter-reindexing" from line 109 of the auto-m4b-tool.sh file in the container, it still ignores/removes all chapters and only uses the filenames. I know that m4b-tool had issues in the past reading them, but i pulled the latest version and ran it on the same file and it picked up ok.
I also tried the beets-audible, but was not having much luck finding matches with chapter data so I figured I would fall back to the chapter data that was in the file all along.
Any help you could offer would be appreciated!
EDIT 1/19/23
I confirmed the issue again by following these steps:
Aftermath.chapters.txt
The text was updated successfully, but these errors were encountered: