mirror of
https://github.com/advplyr/audiobookshelf.git
synced 2026-03-02 22:46:55 -05:00
[Enhancement]: Multiple books in single file #303
Labels
No labels
authentication
awaiting release
backlog
bug
chapter editor
config-issue
ebooks
encoding/embedding
enhancement
help wanted
listening sessions & progress
planned
possible plugin
progress sync
sorting/filtering/searching
unable to reproduce
upload
users & permissions
waiting
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/audiobookshelf-advplyr#303
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @tHeCh0s3n0n3 on GitHub (Apr 25, 2022).
Describe the feature/enhancement
I have a few audiobook files which contain multiple books in a single mp3 file (ex: an Omnibus). When naming the file I can't find a way to indicate that there are multiple books included in the same file.
Example:
File path is: Author Name/Series/Book 1 to 3 - Omnibus/Omnibus.mp3
While scanning, the "Book 1" part of the filename works as expected and the book gets a "#1" tag. However the other book number(s) in the same filename appear to be completely ignored. I can manually add them later though, but it's not ideal.
Enhancement:
Make the filename parser able to accept multiple books in the same file.
Suggesting file naming conventions:
@dweomer21 commented on GitHub (May 24, 2022):
I was about to write up an issue requesting this same feature!
Consider this an upvote.
@advplyr commented on GitHub (Jun 18, 2022):
How would you show the series sequence for multiple books in one?
@tHeCh0s3n0n3 commented on GitHub (Jul 11, 2022):
Not sure I understand the question, but the result I'm suggesting is something like this once it's imported:

@advplyr commented on GitHub (Jul 25, 2022):
If the title came in as
0.5-3then the scanner would have no way to know that there is a sequence for 1 and 2. Maybe there is a sequence 1.5.This seems complex with a ton of edge cases that would have to be considered. When we plan out how to allow the user to customize the path parsing then we can revisit this but for now it is not planned to support.