MediaMonkey forum

Just updated to 5.0.0.2291.
I selected 208 files to auto-tag.
It preloaded and updated the first 100 files but did not give me the option to tag & save, only skip and continue.
Repeated with 8 files, same issue.

Why can I not save the updates?

Please disregard. i did not realize I had to Select the files to correct.
All is good

I assumed that AUTO meant it was AUTOMATIC.
It is going to be a pain if i need to accept every 100 songs or so when processing 10k+.
Will this behavior be corrected for the full release?

It's a safeguard to prevent accidental tagging as this can't be undone. So. it's a better safe than sorry setting.

Can i suggest an override option?
As I said processing 6k files 100 at a time makes this way less desirable.
I do not want to keep returning to my pc every 1/2 hr to proceed.
That would take 18 hrs to complete!

The 100 limit won't change, it's there by design: https://www.mediamonkey.com/wiki/WebHel ... g_Auto-Tag

Macro Toolworks has a free version that can be used to automate auto tag. You set a pixel test on the yellow status bar as a trigger. The macro itself has 2 mouse clicks, the title checkbox to select all the items the other to select tag and continue.

Batch size of 100 is fine. However, It would be nice if there was an option to move to the next batch of 100 recursively without a third party macro, for those processing large libraries.

You really should verify the results before having them applied to your files.

Is there an option to suppress the need of manually clicking Tag & Continue after 100 tracks batch processed?

The process at the moment is as following:
1. I need to wait for 100 tracks to be processed
2. then select the checkbox next to Title, to select all/confirm
3. then click Tag & Continue.
4. then wait another 4/5 mins to do 1. 2. and 3. again

This is cumbersome when doing 4000+ tracks.
I want to review when processing is done, instead of the need of manually interveining in between.

I've looked into the Options but I can't find a way to suppress it.

No, this limit is programmed in to reduce load on servers.