MediaMonkey forum

No idea, sorry. I've added it to my list to investigate though.

Thanks for the update. I didn't see your post go to the next page and was beginning to feel left out. I appreciate your response. Please let me know if your investigation becomes fruitful as this script will do wonders for my organization.

Thanks again!

Groovy script. Build it and they will come!

Since this script is strictly for utility (cleaning up the library art tags) and the data has no permanent value in the track tag, I don't want to alter the file and file's timestamp for it. Besides relying on timestamps for library maintenance and harddrive backups, unnecessarily altering a track file increases the odds (slim as that may be) that the file gets corrupted. Album art resolution is already stored in the Album Art tag and thus this script really should only be writing to the MM database. If the database gets corrupted for some other reason and you lose the temporary album art resolution data generated by this script, no big deal because you have to re-run it anyway, whenever you're editing album art.

Summary: I suggest storing this "resolution" data in the MM databse only WITHOUT having to disable the MM options "Update tags when editing properties" and "Modify timestamp when updating properties", as those are indespensible options that I don't what to forget to re-enable. And the script should finish much quicker if it's not writing to each of the track files.

PatMcQ wrote:Summary: I suggest storing this "resolution" data in the MM databse only WITHOUT having to disable the MM options "Update tags when editing properties" and "Modify timestamp when updating properties", as those are indespensible options that I don't what to forget to re-enable. And the script should finish much quicker if it's not writing to each of the track files.

The script should respect the setting "Modify timestamp when updating properties" from MM4. I don't want to set it for every add-on or script separately.
I would vote +1 for the option:
a) Write to MM.DB and track
b) Write to MM.DB only

At the moment the way the script works is that it updates the database for each track individually as it loops through, and then also adds the changed tracks to a list. At the end of the loop, the script calls "UpdateAll" on the list, which is what uses your settings to determine whether or not to update the files as well. I could easily add an option in to not call this final "UpdateAll".

In the meantime you could easily comment out the line, which is line 385, by adding an apostrophe at the front...

New version (1.6) is now available to download from my website. Changes includes...

- Added option to only store to database
- Fixed "Width x Height" not working with other options

There seems to be an issue with your site at the moment.

Yes, there is. My host are currently working to resolve it. Hopefully it'll be back up soon!

It's baaack!

Am a little confuse in how this scripts works....
can you tell me how it work step by step
I got it to go in MM but just not sure how to get my covers all the same size...

This script doesn't change your covers. It "only" calculate the size (height, width) and write the numbers to a custom field in the format you choose. It does not adjust the cover itself in any way.

Think I may have found a bug...
If you have "don't populate tracks without cover art" checked, the script will only work with "Width x Height" and "Total; W x H".
With much trepidation, I rolled up my sleeves and delved into the code (it's my first time working with MM scripting). The problem seems to be line 316 which reads:
This should probably be either or even Checking for "act" is superfluous, you can rely on "cnt" (and therefore "res") even in Cases 7 and 8.

Thanks, I'll take a look and fix this in the next version.

New version (1.7) is now available to download from my website. I have fixed the "Don't populate..." option not working in some modes.

I am having a problem I don't understand. I select all files and Tools->Scripts->Calculate cover size

In the window I set Count. Then after complete most look correct but here is an example of one that really isn't right. The count is 50100 but in actuality there are no images. So ... why would this happen?