[Bug]: some m4b audiobooks are being imported with book title and description of "End Credits" instead of using the file's audio metadata #2706

Closed
opened 2026-04-25 00:09:43 +02:00 by adam · 9 comments
Owner

Originally created by @Neurrone on GitHub (Apr 4, 2025).

What happened?

I've seen this on 2 books now but so far, I couldn't find out what causes this.

I used the Beets-audible plugin that I wrote to organize my audiobooks. This works well except that some books when imported use "end credits" as the title and description, instead of the audio file metadata. I'm at a loss at how else to proceed to debug what's going on.

What did you expect to happen?

Books are being imported with the title and book description set to "end credits", perhaps taken from the last chapter marker of the m4b file?

Steps to reproduce the issue

Import some specific audiobooks. I am not sure how to transfer the book without violating copyright though.

Audiobookshelf version

v2.20.0

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

Nothing shows up in the logs during the import

Additional Notes

No response

Originally created by @Neurrone on GitHub (Apr 4, 2025). ### What happened? I've seen this on 2 books now but so far, I couldn't find out what causes this. I used the [Beets-audible plugin](https://github.com/Neurrone/beets-audible) that I wrote to organize my audiobooks. This works well except that some books when imported use "end credits" as the title and description, instead of the audio file metadata. I'm at a loss at how else to proceed to debug what's going on. ### What did you expect to happen? Books are being imported with the title and book description set to "end credits", perhaps taken from the last chapter marker of the m4b file? ### Steps to reproduce the issue Import some specific audiobooks. I am not sure how to transfer the book without violating copyright though. ### Audiobookshelf version v2.20.0 ### 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 ```shell Nothing shows up in the logs during the import ``` ### Additional Notes _No response_
adam added the bug label 2026-04-25 00:09:43 +02:00
adam closed this issue 2026-04-25 00:09:44 +02:00
Author
Owner

@nichwall commented on GitHub (Apr 4, 2025):

Does beets-audible modify the metadata? It sounds like your media files have bad metadata.

You can look at the file metadata ABS finds following the steps here https://www.audiobookshelf.org/guides/ffprobe

@nichwall commented on GitHub (Apr 4, 2025): Does beets-audible modify the metadata? It sounds like your media files have bad metadata. You can look at the file metadata ABS finds following the steps here https://www.audiobookshelf.org/guides/ffprobe
Author
Owner

@Neurrone commented on GitHub (Apr 4, 2025):

The probe output was the first thing that I checked, and all the fields, including the album name / book title are read correctly.

Since I'm in the process of migrating from Plex to Audiobookshelf, I'm also serving the same collection via Plex. The book appears fine on Plex.

@Neurrone commented on GitHub (Apr 4, 2025): The probe output was the first thing that I checked, and all the fields, including the album name / book title are read correctly. Since I'm in the process of migrating from Plex to Audiobookshelf, I'm also serving the same collection via Plex. The book appears fine on Plex.
Author
Owner

@nichwall commented on GitHub (Apr 4, 2025):

Can you share a screenshot of the book details page?
Have you matched against an online provider, or are you only scanning the book from your file system?
Does deleting the book from ABS and then scanning again fix it?

If you delete the book and add it again, you can look at the scan logs to see exactly what is happening for the book, which is probably easier than trying to find a specific book in a full library scan.

@nichwall commented on GitHub (Apr 4, 2025): Can you share a screenshot of the book details page? Have you matched against an online provider, or are you only scanning the book from your file system? Does deleting the book from ABS and then scanning again fix it? If you delete the book and add it again, you can look at the scan logs to see exactly what is happening for the book, which is probably easier than trying to find a specific book in a full library scan.
Author
Owner

@Neurrone commented on GitHub (Apr 4, 2025):

Have you matched against an online provider, or are you only scanning the book from your file system?

I have audible.com set as the metadata provider

Library settings page

This is the scanner tab, I'm not sure whether my audio metadata overrides lookup to audible.com.

List of scanner sources

Here is probe output for the affected book

probe output, showing that the title of the book is parsed correctly

Does deleting the book from ABS and then scanning again fix it?

I see the control to delete the book. When you say rescan, are you referring to clicking scan for the entire library?

you can look at the scan logs to see exactly what is happening for the book, which is probably easier than trying to find a specific book in a full library scan.

Where can I see these logs for this?

@Neurrone commented on GitHub (Apr 4, 2025): > Have you matched against an online provider, or are you only scanning the book from your file system? I have audible.com set as the metadata provider ![Library settings page](https://github.com/user-attachments/assets/23b18184-429d-4fa9-9eaf-f94692ae02c8) This is the scanner tab, I'm not sure whether my audio metadata overrides lookup to audible.com. ![List of scanner sources](https://github.com/user-attachments/assets/9918ec39-1c22-4117-9c8e-5d6426127e39) Here is probe output for the affected book ![probe output, showing that the title of the book is parsed correctly](https://github.com/user-attachments/assets/a6caf089-fa3b-4ac7-a825-0903e1758500) > Does deleting the book from ABS and then scanning again fix it? I see the control to delete the book. When you say rescan, are you referring to clicking scan for the entire library? > you can look at the scan logs to see exactly what is happening for the book, which is probably easier than trying to find a specific book in a full library scan. Where can I see these logs for this?
Author
Owner

@nichwall commented on GitHub (Apr 4, 2025):

Have you matched against an online provider, or are you only scanning the book from your file system?

I have audible.com set as the metadata provider

This is the scanner tab, I'm not sure whether my audio metadata overrides lookup to audible.com.

ABS does not look up any information against an online provider unless you specifically run the "match" or "quick match". This is intentionally a separate action, so this incorrect data is being set by your files somehow.

I see the control to delete the book. When you say rescan, are you referring to clicking scan for the entire library?

Yes, you would need to scan the entire library again.

you can look at the scan logs to see exactly what is happening for the book, which is probably easier than trying to find a specific book in a full library scan.

Where can I see these logs for this?

Logs are stored in /metadata/logs

@nichwall commented on GitHub (Apr 4, 2025): > > Have you matched against an online provider, or are you only scanning the book from your file system? > > I have audible.com set as the metadata provider > > This is the scanner tab, I'm not sure whether my audio metadata overrides lookup to audible.com. ABS does not look up any information against an online provider unless you specifically run the "match" or "quick match". This is intentionally a separate action, so this incorrect data is being set by your files somehow. > I see the control to delete the book. When you say rescan, are you referring to clicking scan for the entire library? Yes, you would need to scan the entire library again. > > you can look at the scan logs to see exactly what is happening for the book, which is probably easier than trying to find a specific book in a full library scan. > > Where can I see these logs for this? Logs are stored in `/metadata/logs`
Author
Owner

@Neurrone commented on GitHub (Apr 4, 2025):

After deleting the books and rescanning the library, they appear correctly.

I don't have any idea why this is happening but I'll close this issue for now. I'll take more notes when adding a new book to try to see if I can find out more.

@Neurrone commented on GitHub (Apr 4, 2025): After deleting the books and rescanning the library, they appear correctly. I don't have any idea why this is happening but I'll close this issue for now. I'll take more notes when adding a new book to try to see if I can find out more.
Author
Owner

@nichwall commented on GitHub (Apr 4, 2025):

After deleting the books and rescanning the library, they appear correctly.

I don't have any idea why this is happening but I'll close this issue for now. I'll take more notes when adding a new book to try to see if I can find out more.

Glad it's work for you. Yeah, if you can reproduce the issue that would be great, but if not then that works too.

@nichwall commented on GitHub (Apr 4, 2025): > After deleting the books and rescanning the library, they appear correctly. > > I don't have any idea why this is happening but I'll close this issue for now. I'll take more notes when adding a new book to try to see if I can find out more. Glad it's work for you. Yeah, if you can reproduce the issue that would be great, but if not then that works too.
Author
Owner

@Neurrone commented on GitHub (Apr 8, 2025):

Is there any debug logging that I can enable for books picked up by using the default settings where it watches the folder for new items? The idea is to look at that the next time I paste new books into the folder for the library. That's how I've been adding new books.

@Neurrone commented on GitHub (Apr 8, 2025): Is there any debug logging that I can enable for books picked up by using the default settings where it watches the folder for new items? The idea is to look at that the next time I paste new books into the folder for the library. That's how I've been adding new books.
Author
Owner

@nichwall commented on GitHub (Apr 8, 2025):

Is there any debug logging that I can enable for books picked up by using the default settings where it watches the folder for new items? The idea is to look at that the next time I paste new books into the folder for the library. That's how I've been adding new books.

You can enable Debug logs in the server settings.

@nichwall commented on GitHub (Apr 8, 2025): > Is there any debug logging that I can enable for books picked up by using the default settings where it watches the folder for new items? The idea is to look at that the next time I paste new books into the folder for the library. That's how I've been adding new books. You can enable Debug logs in the server settings.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#2706