You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a library of many m4b's and after upgrading audiobookshelf to a newer version, the covers of newly added m4b files don't show up, although I ensured that the files contain a valid cover.
What did you expect to happen?
I would have expected the covers to show up as normal.
Steps to reproduce the issue
Add the attached file to your audio book folder and wait for it to be scanned. input.zip
This problem might be related to #1063 and #2885 - but is very specific to m4b files with embedded cover. I found out that the problem is possibly a wrong ffmpeg extraction command in:
What happened?
I have a library of many m4b's and after upgrading audiobookshelf to a newer version, the covers of newly added m4b files don't show up, although I ensured that the files contain a valid cover.
What did you expect to happen?
I would have expected the covers to show up as normal.
Steps to reproduce the issue
Add the attached file to your audio book folder and wait for it to be scanned.
input.zip
This problem might be related to #1063 and #2885 - but is very specific to
m4b
files with embedded cover. I found out that the problem is possibly a wrongffmpeg
extraction command in:audiobookshelf/server/utils/ffmpegHelpers.js
Line 56 in 190a100
which results in
This command extracts a FULLY BLACK cover for
m4b
files.Possible solution
The corrected command that works and extracts the cover as expected would be:
or in code
but I'm not sure, that this is the place the problem occurs.
Audiobookshelf version
2.17.4
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?
Chrome
Logs
No errors in log files
Additional Notes
Suggested solution should fix the problem.
The text was updated successfully, but these errors were encountered: