Doesn't like something about the names of this book's files #44

Closed
opened 2026-04-24 22:57:01 +02:00 by adam · 7 comments
Owner

Originally created by @Merijeek on GitHub (Oct 4, 2021).

image

It's only catching the second filename, but it thinks it's the last file:

image

But we've definitely got the fill list:

image

(it keeps going)

Originally created by @Merijeek on GitHub (Oct 4, 2021). ![image](https://user-images.githubusercontent.com/65377425/135780273-acd59f7f-4eeb-4805-977f-8b35f9d16bdd.png) It's only catching the second filename, but it thinks it's the last file: ![image](https://user-images.githubusercontent.com/65377425/135780327-06790ae5-5137-4a32-8260-c113e972b502.png) But we've definitely got the fill list: ![image](https://user-images.githubusercontent.com/65377425/135780350-2b9cca84-72a7-4ebc-bfb5-f23fd47f96d5.png) (it keeps going)
adam closed this issue 2026-04-24 22:57:01 +02:00
Author
Owner

@advplyr commented on GitHub (Oct 4, 2021):

Unfortunately I haven't come up with a good way to parse out the track # from the filename, so it looks for the first number (that is not part of the title) and uses that as the track #.
It sees a whole bunch of files with track # 1, then track # 2, and it is calling them duplicate tracks.

It prefers to use the track number metadata in the audio file, but in your case those must not be set properly.

This is why I setup the manage tracks section though, so you can drag them into the correct orders, press save, and it will remove the duplicate errors.

@advplyr commented on GitHub (Oct 4, 2021): Unfortunately I haven't come up with a good way to parse out the track # from the filename, so it looks for the first number (that is not part of the title) and uses that as the track #. It sees a whole bunch of files with track # 1, then track # 2, and it is calling them duplicate tracks. It prefers to use the track number metadata in the audio file, but in your case those must not be set properly. This is why I setup the manage tracks section though, so you can drag them into the correct orders, press save, and it will remove the duplicate errors.
Author
Owner

@Merijeek commented on GitHub (Oct 4, 2021):

I didn't know about that. All I did was drag it to the right spot, and poof, all good.

@Merijeek commented on GitHub (Oct 4, 2021): I didn't know about that. All I did was drag it to the right spot, and poof, all good.
Author
Owner

@Merijeek commented on GitHub (Oct 4, 2021):

Well, I was going to tell you that you should just close this, but now I'm seeing this for a different book.

I've tried rescanning, as well as deleting and readding. It keeps saying there's missing pieces on this one:

image

image

I've also deleted the included .nfo, just in case, No love.

@Merijeek commented on GitHub (Oct 4, 2021): Well, I was going to tell you that you should just close this, but now I'm seeing this for a different book. I've tried rescanning, as well as deleting and readding. It keeps saying there's missing pieces on this one: ![image](https://user-images.githubusercontent.com/65377425/135895326-a19ab2f1-9252-462f-b02f-3474331b1be8.png) ![image](https://user-images.githubusercontent.com/65377425/135895393-eedd904e-a56d-433e-a47e-01b87b87a2ec.png) I've also deleted the included .nfo, just in case, No love.
Author
Owner

@Merijeek commented on GitHub (Oct 4, 2021):

Oh hell, cancel it. I had two folders, one of which was incomplete.

BUT, that does show a place for screwups. It might be worthwhile (maybe under dev settings) to show the actual path to a book somewhere. If that were on the page I'd have probably spotted it more quickly.

@Merijeek commented on GitHub (Oct 4, 2021): Oh hell, cancel it. I had two folders, one of which was incomplete. BUT, that does show a place for screwups. It might be worthwhile (maybe under dev settings) to show the actual path to a book somewhere. If that were on the page I'd have probably spotted it more quickly.
Author
Owner

@advplyr commented on GitHub (Oct 4, 2021):

Agree on adding the path. There is definitely room for improvement on the wording for error alerts. The manage tracks table is also messy.
If you think of any ways to re-organize that or handle it differently let me know. Also lacking documentation on track numbering and reordering.

@advplyr commented on GitHub (Oct 4, 2021): Agree on adding the path. There is definitely room for improvement on the wording for error alerts. The manage tracks table is also messy. If you think of any ways to re-organize that or handle it differently let me know. Also lacking documentation on track numbering and reordering.
Author
Owner

@Merijeek commented on GitHub (Oct 4, 2021):

I think the manage tracks is fine (apart from lack of documentation). About
all I can think to improve it is maybe a checkbox for toggling showing the
full path.

On Mon, Oct 4, 2021 at 11:39 AM advplyr @.***> wrote:

Agree on adding the path. There is definitely room for improvement on the
wording for error alerts. The manage tracks table is also messy.
If you think of any ways to re-organize that or handle it differently let
me know. Also lacking documentation on track numbering and reordering.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/advplyr/audiobookshelf/issues/79#issuecomment-933751857,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APSZJEKAZW65Y6VCGAL6NKDUFHYFVANCNFSM5FIHL2HQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

@Merijeek commented on GitHub (Oct 4, 2021): I think the manage tracks is fine (apart from lack of documentation). About all I can think to improve it is maybe a checkbox for toggling showing the full path. On Mon, Oct 4, 2021 at 11:39 AM advplyr ***@***.***> wrote: > Agree on adding the path. There is definitely room for improvement on the > wording for error alerts. The manage tracks table is also messy. > If you think of any ways to re-organize that or handle it differently let > me know. Also lacking documentation on track numbering and reordering. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/advplyr/audiobookshelf/issues/79#issuecomment-933751857>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/APSZJEKAZW65Y6VCGAL6NKDUFHYFVANCNFSM5FIHL2HQ> > . > Triage notifications on the go with GitHub Mobile for iOS > <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> > or Android > <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. > >
Author
Owner

@advplyr commented on GitHub (Oct 7, 2021):

In v1.4.1 you can now toggled on/off "Full Path" on track & file tables.

I'm not thrilled with the look of the toggle button there, but that can be smoothed out later.

image

@advplyr commented on GitHub (Oct 7, 2021): In [v1.4.1](https://github.com/advplyr/audiobookshelf/releases/tag/v1.4.1) you can now toggled on/off "Full Path" on track & file tables. I'm not thrilled with the look of the toggle button there, but that can be smoothed out later. ![image](https://user-images.githubusercontent.com/67830747/136309970-5be5f52d-a79b-4d73-b862-c2e8a0dce52c.png)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#44