2160 - This time, the process went on until the end and please with a progress bar!

But while I wanted to intervene on one or the other of the tracks:
ID ECA547D4
Access violation at address 6C81B05A in module "f_MP4.dll''

and unfortunately I couldn't validate this long operation
then restart

Just open unsynchronized tags view in new tab .

The progress bar is a good thing.
This operation cannot be done in the background as in mm4. Is that necessary?
However for a large base I could never complete this process with mm5 without any error message and without being able to close properly.

You're right we can add some progress as it can take some time to finish (it need to load tags of all tracks and compare with DB).

EDIT: progress will be in next build

mm5 2158 (200000 tracks)

Aafter 15 mm it's impossible to stop the process.
i think this process do not work for big dbb.
During the operation the processor was around 20 à 25 %.
There is no indication of the progression.

A few months ago, I had already mentioned the problems of the "out-of-date tags" and "update tags" functions and their use of important resources (disk, memory and processor). The situation has not improved.
It seems to me that these processes replace "unsynchronised tags" and "synchronised".
If the first one reaches the end of its work, slowly it must be said, the second freezes inevitably when there are several thousand tracks.

I also confess that I don't fully understand this function, because sometimes in mm4, the corrected tags reappear.
And after a synchronization made in mm4, we still have to redo the operations in mm5 with the imported base.

Thanks for your attention