-
Notifications
You must be signed in to change notification settings - Fork 495
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]: webp covers (either in folder structure or embedded in files) make the metadata embedder and the m4b conversion tool fail #3379
Comments
My suggestion would be to detect the usage of .webp covers and simply skipping the embed step for them as a quick bypass solution. Longer term, maybe change the ABS interface so that .webp covers are not accepted to be set in the first place (and a notice is given to the user that they should please use a png or jpg file instead) |
I'll take a look. I'm pretty sure it's easily fixable. |
I didn't dig too deeply into this, but it looks like webp isn't supported in a mp4 container. What I can do is to convert the input webp into jpeg or png on-the-fly and embed that into the file. Is that an acceptable solution? |
If that's possible I think that would be the best possible solution as it achieves the desired result (an embedded cover) and does what the user expects (embedding a cover that worked in ABS without a warning message) |
Fixed in v2.13.4. |
What happened?
When you use a .webp image as a cover, it will show correctly on the ABS GUI - however, the metadata manager cannot embed or modify it in files (which also means that m4b conversions fail due to the embed being a step in the process)
What did you expect to happen?
.webp working the same as .png or .jpg files - or at least failing gracefully with a clear error message (auto conversion would be perfect of course)
Steps to reproduce the issue
Audiobookshelf version
v2.12.3
How are you running audiobookshelf?
Windows Tray App
What OS is your Audiobookshelf server hosted from?
Windows
If the issue is being seen in the UI, what browsers are you seeing the problem on?
None
Logs
Additional Notes
No response
The text was updated successfully, but these errors were encountered: