[SOLVED] Cover images not loaded for all albums

[Nutul]

@Nutul@Tim Curtis @TheOldPresbyope

I did a quick research and found the tool eyed3, which seems to be the swiss army knife for ID3 editing on the command line

Updating to 2.4:
eyed3 --to-v2.4

And also getting rid of iTunes specific entries in the comment sectiongoes easily with:
eyed3 --remove-all-comments 

So the sun will shine again soon  \o/

Cheers,
Andrea

Andrea,

yes, that's one of the tools that will do the job.

find . -iname "*.mp3" -exec eye3d --remove-all-comments --to-v2.4 "{}" \;

provided you are on a Linux machine, the command above should migrate all your mp3 files to v2.4 and remove the unwanted comments.

It looks like I rejoiced too early. I have converted the entire mp3 collection to ID3 v2.4 and deleted all the unnecessary comment entries, but after a new import (cache and meta data definitely cleared) the same cover images are again not loaded.

When I compare the files with eyed3d whose album art is displayed and those whose album art is not, I can't spot any difference. Maybe I will look into it with ffmpeg again later which provides some more detailed information in the logs.

A workaround would probably be to extract the image from a file and save it in the album directory, but that's certainly not a nice solution.

Hi,

the problem could be that the thumbnails already exist (folder and file names haven't changed, right?), so if you go to "m" => Configure => Library, then scroll down to "Thumbnail Generator" section and hit the "Regenerate" button, once it's finished you should be fine with all the thumbnails re-generated from the embedded pictures again.

Another way to check the image can be read is to actually play the file: in the Now-Playing and Screensaver view the image is shown (while it may not in the playing queue and the albums list, until, as said, you re-generate the thumbnails).

Hey,

hitting the "regenerate thumbnails" button was of course my first action. Then I cleared all files in /var/local/www/thbimages (not sure if I memorized the path correctly) and restarted the cache generation. When none of it worked, out of desperation, I wrote a fresh Moode image to the Raspi SD, since I'm not 100% familar with the Moode file structure yet, and I was wondering if there may is some other cache living in some other place or in a database. But still no success.

Andrea

Hi Andrea,

two things:

1. if you are accessing moOde UI through a browser, try clearing the browser's cache
2. send over a file still not working as expected (possibly the same) so that I can have another look at it