MM4 does not use our MusicBrainz server for auto-tag. It used to have utilized Amazon in the past, but AFAIK the only way to auto-tag in MM4 is now using third party addon (from Discog)

[quote=Ludek post_id=502647 time=1668100209 user_id=7319]
FYI: It was because temporal MB server inaccesibility, tracking as https://www.ventismedia.com/mantis/view.php?id=19556 to improve the messaging.
[/quote]

Thanks for looking into this Ludek,

I am not certain I understand why MMW4 does not show a "temporal MB Server inaccessibility" whereas MMW5 does. Remember, I submitted auto-tag using both MMW4 and MMW5 at the same time / same network / same country ... several times.

Is this "error" not detected as well / or suppressed in MMW4 for example?

Is the "dialogue" between MMW4 and the server different to that from MMW5?

From a user view point the error seems to be specific to certain files and I was sort of expecting to get the same issue in both MMW4 and MMW5.

Hope this is helpful.

That is odd, because I am getting same error today for same file. Will try several times to confirm.

Also odd, if I remove the title, autotag re-finds the title in spite of also giving the error message.

Other files do not display this error.

Bear in mind that this file was successfully tagged earlier yesterday, with no error message, so it seems autotag has added something which causes it.

FYI: It was because temporal MB server inaccesibility, tracking as https://www.ventismedia.com/mantis/view.php?id=19556 to improve the messaging.

[quote=Rob_S post_id=502609 time=1668012909 user_id=112670]
Ticket #5028: "metadata lookup failure" has been successfully submitted
[/quote]
Hi Rob,

I can confirm that I still get this error with the most recent release of MMW5 - 2682 - for the files mentioned previously.

I do not get the error message with MMW4.

I checked this "simultaneously" by selecting the same file on a Windows 10 / MMW4 vs Windows 11 / MMW5.

Does not seem to have any other impact. Hope this helps.

Ticket #5028: "metadata lookup failure" has been successfully submitted

If you can reproduce, please capture this in a debug log (step 4b): https://www.mediamonkey.com/forum/viewtopic.php?f=30&t=86643

I just got this error while testing for something else....

Interestingly it was while doing a lookup on a track I had just auto-tagged a new title, but for which no image was found.

Hi Peke,

Here's the error log (ran Auto-Tag Ctrl+L several times) and associated video.

https://octoberclub-my.sharepoint.com/:u:/g/personal/ian_octoberclub_onmicrosoft_com/ERZA5IJi325CkqQsthj0WvgBeOu8BL55ujqPgxpQxtrJmg?e=cbvaFz

https://octoberclub-my.sharepoint.com/:v:/g/personal/ian_octoberclub_onmicrosoft_com/ESfIEe8dZm1PlRCSKddbXnUBZAVtUE83i8971SL5M_uhxw?e=Z0NYc5

I do not get the same error with MMW4 but will try swapping the files from my D:(MMW4) and E:(MMW5)... Essentially, they are the same file as "cloned" a while back.

OK, so instead of above, just used the Folders node to point to the "OneDrive" copy I sent previously AND my MMW4 D:\...\Music\... All 3 locations / copies give the same error! This was one a many files with this sort of error that came up when I checked "Lookup missing information via Auto-Tag (registered users only) option under Add/Rescan files to library...

It would be good to know if there is a fix.

Hi,
:( Unfortunately I can't replicate. Maybe it temp Metadata Server error. If it happen again maybe log file will show more.

Sent link in PM.

Hi,
Also If you can supply us DL Link for at least one sample track that observes error would be also valuable.

Please capture the error in a debug log (step 4b) and attach it to a Support Ticket: https://www.mediamonkey.com/forum/viewtopic.php?f=30&t=86643

This will help a developer analyze why this happens in your setup.

If this is not documented anywhere, then it is of no use. With a few thousand songs you don't have an overview.

Which build I am using is in my signature

Which Build (Help > About) are you seeing this on?