2016-08-03, 20:48
@Risgah: You've discovered the hard way that Artwork Downloader doesn't support artwork with the movie-name prefix which is why it's recommended not to enable the "Use local artwork" setting (this is mentioned throughout the AD thread) if you have multiple movies per folder. Unfortunately using AD in this way has hosed your library by associating multiple movies with useless artwork of the same name. Now that you've deleted this artwork you're left with multiple movies associated with non-existing local artwork.
To fix this you can use mklocal.py to remove the artwork associations from your MyVideos library that no longer exist in your local filesystem by using the "--readonly --nokeep" options.
Once you've removed the non-existent artwork associations you should use Artwork Download again, but this time with "Use local artwork" DISABLED. Now any missing artwork for movies will be associated with links to remote artwork. You can leave you library like that, using remote artwork (which may disappear at some point), but instead I would recommend you use mklocal.py again (this time without --readonly) to download the new remote artwork and create new image files using movie-name prefix filenames alongside your movies, then associate your movies with these new local artwork files (which you can then cache etc.).
Using mklocal.py to download remote artwork alongside your movies is superior to exporting artwork from your library, as the library export will export only the cached (and thus lower quality) artwork and not the original high-quality artwork which is what mklocal.py will download.
To fix this you can use mklocal.py to remove the artwork associations from your MyVideos library that no longer exist in your local filesystem by using the "--readonly --nokeep" options.
Once you've removed the non-existent artwork associations you should use Artwork Download again, but this time with "Use local artwork" DISABLED. Now any missing artwork for movies will be associated with links to remote artwork. You can leave you library like that, using remote artwork (which may disappear at some point), but instead I would recommend you use mklocal.py again (this time without --readonly) to download the new remote artwork and create new image files using movie-name prefix filenames alongside your movies, then associate your movies with these new local artwork files (which you can then cache etc.).
Using mklocal.py to download remote artwork alongside your movies is superior to exporting artwork from your library, as the library export will export only the cached (and thus lower quality) artwork and not the original high-quality artwork which is what mklocal.py will download.