If I checked this setting:
I wouldn’t get a new coverart:
Yes, because the newer one has a resolution of only 373x377 pixels whereas your existing one is 500x500.
Activating the option “Never replace cover images with smaller ones” would prevent that smaller cover images would be used.
Or what exactly is not working as expected for you?
Picard downloaded the current cover with the artist’s face, and I want it saved.
That option silently prevents this. I don’t even know how many files in my library have this problem.
As long as the existing image is of higher resolution than the one you want, that option is going to do exactly what it says – prevent replacing the higher-res image with a lower-res one.
Your options are:
- Turn off that setting, so Picard can replace the image
- Delete the image you don’t want from the track, then let Picard do its thing
- Find a higher-resolution copy of the image you want elsewhere, and upload it to MB
- Manually download the image you want (without using Picard)
4 Likes
I know all this. 
But how do I do it for 16,000 files?
Or maybe this.
Use the OpenCV or Pillow libraries to compare covers?
If coverart_old is similar to coverart_new, then “Disallow smaller cover.”
If coverart_new is completely different, then “Replace.”
I don’t know how to do it without turning off that setting and letting Picard process 16,000 files. Maybe there’s a plugin that can help?
What do you think?
Maybe it’s worth writing this into Picard’s code?
If coverart_old is similar to coverart_new, then “Disallow smaller cover.”
If coverart_new is completely different, then “Replace.”
How is Picard to determine whether the cover art is similar or completely different? I can tell you that I won’t be adding that code.
1 Like
Don’t add, but there are OpenCV or Pillow libraries.
Yeah, but that’s yet another library to include and maintain for a rather niche requirement. My point is that I’m not convinced it should be added to the Picard base code (even using a third-party library). If you want the other developers to consider it, you should add a ticket.
3 Likes
IMHO this is not a niche requirement. Many people may be affected by this and not even know it.
You’re entitled to your opinion, as am I. As I stated earlier, this is not something that I will be adding to Picard.
Bob Those two lines of “code” are just a mockup. I’m forced to write a plugin. That’s another piece of knowledge. Thanks.
This is way outside my expertise.