Skip to content
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

[Bug]: Individual Chapter Files without Leading Zeroes Sorted Incorrectly #3381

Closed
CaptainLexington opened this issue Sep 5, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@CaptainLexington
Copy link

CaptainLexington commented Sep 5, 2024

What happened?

Most audiobooks with separate MP3 files have leading zeroes in their part number, but if they don't, ABS can sort them wrong when importing them:
image

What did you expect to happen?

The chapters should be sorted in numerical order, probably Natural Sort.

Steps to reproduce the issue

  1. Import more than 10 sequentially-numbered files without leading zeroes on the part numbers.

Audiobookshelf version

2.12.3

How are you running audiobookshelf?

Docker

What OS is your Audiobookshelf server hosted from?

Linux

If the issue is being seen in the UI, what browsers are you seeing the problem on?

None

Logs

No response

Additional Notes

I understand I could rename the files, but that seems like a lot of work considering they come this way from the publisher.

@CaptainLexington CaptainLexington added the bug Something isn't working label Sep 5, 2024
@advplyr
Copy link
Owner

advplyr commented Sep 5, 2024

Those aren't leading zeros though that is a 0 with a hyphen

@CaptainLexington
Copy link
Author

Right, I said there aren't leading zeroes. I have since seen other files sorted by natural sort, without weird interposing hyphens, but this does seem like incorrect behavior regardless.

@advplyr
Copy link
Owner

advplyr commented Sep 5, 2024

If you press "Manage Tracks" button you will see what Abs is pulling for the track number and disc number if applicable.

This doesn't have to do with not having leading zeros, it has to do with there being a 0 in the filename before the other number.

@advplyr advplyr closed this as not planned Won't fix, can't repro, duplicate, stale Sep 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants