Subsonic Forum

If you have a 'cover.jpg' file in your folder for an album, it can not be replaced through the last.fm album cover search feature. Those will download png files, and so you end up with both "cover.jpg" and "cover.png" in the folder. Subsonic isn't looking for the newest, it is looking by name, and in the priority order, cover.jpg comes first.

So it will say 'successfully downloaded', which is true, but continue to show the old cover.

Workaround is to just go into the folder and delete cover.jpg and it will find the new file on the next time you open that directory in Subsonic.

Not a big deal, just can seem surprising.

J

Hi,
I don't think that your remark is correct.
Almost all of my cover art in Subsonic is a jpg file.
When I change it by using Subsonic's cover art search, Subsonic renames the existing image to .old (like cover.jpg.old) and next copies the new image to the folder.
So changing the cover art will show the new image since the old image isn't considered an image file anymore.
I don't know why this doesn't happen in your setup.

The issue is the *suffix*. Yes, if it had to replace cover.jpg with cover.jpg, it created cover.jpg.old and moved on.

Last.fm sometimes gives .png files instead of. jpg files. THAT is the situation where the png is newer than the jpg, but Subsonic's algorithm picks cover.jpg first, not just the newest image file. Because it didn't need to replace cover.jpg (the new file was cover.png), it left it there...then continued to serve it up first.

Or if not last.fm doing it, then picking a file off another site by URL and that file happens to be a png.

Whenever I change the cover art image by using Subsonic, the current cover art picture gets renamed to .OLD.
It doesn't matter if the current coverart is BMP, JPG, PNG, JPEG or GIF. They all get renamed to .OLD.
At least: That's happens in my setup.
Even when I point to an url that has the correct cover art image in another format than the current image.

Dude I'm just saying that in THAT particular album's case, that's not what happened. the png file downloaded, the jpg file stayed unchanged (in fact, if i tried to download the png a second time, i got .png.old but the jpg remained), and i'm simply suggesting a WORKAROUND if it happens to somebody else. I'm trying to be helpful on an observed behavior, and i'd rather not be told "what you're saying happened couldn't have happened". It happened, and this is how i resolved it.

Dude, I'm just saying that in my setup the old image file always get renamed to .OLD. No matter what filetype it was en what filetype the new image file was.
So I really don't see any need for a "workaround" to a non-existing problem.

There are dozens of bugs and odd situations that people find and report here that nobody else can replicate, including the dreaded 503s. I was trying to be helpful and proactive for this one and you're telling me that because it never happened TO YOU, I should just ignore it? Sorry, I'd rather be helpful.