by trixmoto » Wed Aug 07, 2013 4:00 pm
This script is not checking to see which tracks do not have any artwork, it's checking for tracks which do have artwork, but the tags are pointing to an external image which does not exist. In other words, it's checking for broken artwork links. This is why it has to loop through all the tracks, in order to check all the artwork.
Looking at the script, it may be possible to improve the performance by only looping through tracks which have artwork, but I'd have to re-check the database structure, as I can't remember what is available off the top of my head.
This script doesn't update any information in the database, it just stores the report in location memory, which is why it has to start again if MM is closed. Again, it could be modified to create a new table in the database, or something like that, so that the report persists. The problem with that is that it could become out of date, so you'd need to remember to run the report again for it to be accurate.
This script is not checking to see which tracks do not have any artwork, it's checking for tracks which do have artwork, but the tags are pointing to an external image which does not exist. In other words, it's checking for broken artwork links. This is why it has to loop through all the tracks, in order to check all the artwork.
Looking at the script, it may be possible to improve the performance by only looping through tracks which have artwork, but I'd have to re-check the database structure, as I can't remember what is available off the top of my head.
This script doesn't update any information in the database, it just stores the report in location memory, which is why it has to start again if MM is closed. Again, it could be modified to create a new table in the database, or something like that, so that the report persists. The problem with that is that it could become out of date, so you'd need to remember to run the report again for it to be accurate.