Error:Metadata Lookup (invalid mbid.) / Error: Metadata lookup (undefined)
Moderator: Gurus
-
- Posts: 539
- Joined: Fri Dec 27, 2019 4:41 pm
Error:Metadata Lookup (invalid mbid.) / Error: Metadata lookup (undefined)
Whilst using Auto-Tag, I get these errors for a particular track(s) / file(s).
Do I need to worry about this?
How might I clear / fix?
Ref:
E:\Music\Armin Van Buuren\Universal Religion 2008
E:\Music\Aslan\The French Legion\
Do I need to worry about this?
How might I clear / fix?
Ref:
E:\Music\Armin Van Buuren\Universal Religion 2008
E:\Music\Aslan\The French Legion\
Ian Taylor
Re: Error:Metadata Lookup (invalid mbid.) / Error: Metadata lookup (undefined)
I can also confirm. I get the error message every now and then.
WiFi Syncing
MM Gold 5.1.0.2813 auf Windows 10 Pro 64 Bit "portable Installation"
MM Android 2.0.0.1099 Pro auf folgenden Geräten
Samsung S23 Ultra / Tablet: Samsung Galaxy Tab S8 Ultra
MM Gold 5.1.0.2813 auf Windows 10 Pro 64 Bit "portable Installation"
MM Android 2.0.0.1099 Pro auf folgenden Geräten
Samsung S23 Ultra / Tablet: Samsung Galaxy Tab S8 Ultra
Re: Error:Metadata Lookup (invalid mbid.) / Error: Metadata lookup (undefined)
Which Build (Help > About) are you seeing this on?
Download MediaMonkey | License
Help: Knowledge Base | MediaMonkey for Windows 5 | MediaMonkey for Android
Lowlander (MediaMonkey user since 2003)
Help: Knowledge Base | MediaMonkey for Windows 5 | MediaMonkey for Android
Lowlander (MediaMonkey user since 2003)
Re: Error:Metadata Lookup (invalid mbid.) / Error: Metadata lookup (undefined)
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 I am using is in my signature
WiFi Syncing
MM Gold 5.1.0.2813 auf Windows 10 Pro 64 Bit "portable Installation"
MM Android 2.0.0.1099 Pro auf folgenden Geräten
Samsung S23 Ultra / Tablet: Samsung Galaxy Tab S8 Ultra
MM Gold 5.1.0.2813 auf Windows 10 Pro 64 Bit "portable Installation"
MM Android 2.0.0.1099 Pro auf folgenden Geräten
Samsung S23 Ultra / Tablet: Samsung Galaxy Tab S8 Ultra
Re: Error:Metadata Lookup (invalid mbid.) / Error: Metadata lookup (undefined)
Please capture the error in a debug log (step 4b) and attach it to a Support Ticket: viewtopic.php?f=30&t=86643
This will help a developer analyze why this happens in your setup.
This will help a developer analyze why this happens in your setup.
Download MediaMonkey | License
Help: Knowledge Base | MediaMonkey for Windows 5 | MediaMonkey for Android
Lowlander (MediaMonkey user since 2003)
Help: Knowledge Base | MediaMonkey for Windows 5 | MediaMonkey for Android
Lowlander (MediaMonkey user since 2003)
Re: Error:Metadata Lookup (invalid mbid.) / Error: Metadata lookup (undefined)
Hi,
Also If you can supply us DL Link for at least one sample track that observes error would be also valuable.
Also If you can supply us DL Link for at least one sample track that observes error would be also valuable.
Best regards,
Peke
MediaMonkey Team lead QA/Tech Support guru
Admin of Free MediaMonkey addon Site HappyMonkeying
How to attach PICTURE/SCREENSHOTS to forum posts
Peke
MediaMonkey Team lead QA/Tech Support guru
Admin of Free MediaMonkey addon Site HappyMonkeying
How to attach PICTURE/SCREENSHOTS to forum posts
-
- Posts: 539
- Joined: Fri Dec 27, 2019 4:41 pm
Re: Error:Metadata Lookup (invalid mbid.) / Error: Metadata lookup (undefined)
Sent link in PM.
Ian Taylor
Re: Error:Metadata Lookup (invalid mbid.) / Error: Metadata lookup (undefined)
Hi,
Unfortunately I can't replicate. Maybe it temp Metadata Server error. If it happen again maybe log file will show more.
Unfortunately I can't replicate. Maybe it temp Metadata Server error. If it happen again maybe log file will show more.
Best regards,
Peke
MediaMonkey Team lead QA/Tech Support guru
Admin of Free MediaMonkey addon Site HappyMonkeying
How to attach PICTURE/SCREENSHOTS to forum posts
Peke
MediaMonkey Team lead QA/Tech Support guru
Admin of Free MediaMonkey addon Site HappyMonkeying
How to attach PICTURE/SCREENSHOTS to forum posts
-
- Posts: 539
- Joined: Fri Dec 27, 2019 4:41 pm
Re: Error:Metadata Lookup (invalid mbid.) / Error: Metadata lookup (undefined)
Hi Peke,
Here's the error log (ran Auto-Tag Ctrl+L several times) and associated video.
https://octoberclub-my.sharepoint.com/: ... g?e=cbvaFz
https://octoberclub-my.sharepoint.com/: ... w?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.
Here's the error log (ran Auto-Tag Ctrl+L several times) and associated video.
https://octoberclub-my.sharepoint.com/: ... g?e=cbvaFz
https://octoberclub-my.sharepoint.com/: ... w?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.
Ian Taylor
Re: Error:Metadata Lookup (invalid mbid.) / Error: Metadata lookup (undefined)
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.
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.
Using 5.1 LATEST alpha or beta build on Windows 10, HP laptop, managing 13k tracks
Re: Error:Metadata Lookup (invalid mbid.) / Error: Metadata lookup (undefined)
If you can reproduce, please capture this in a debug log (step 4b): https://www.mediamonkey.com/forum/viewt ... 30&t=86643
Download MediaMonkey | License
Help: Knowledge Base | MediaMonkey for Windows 5 | MediaMonkey for Android
Lowlander (MediaMonkey user since 2003)
Help: Knowledge Base | MediaMonkey for Windows 5 | MediaMonkey for Android
Lowlander (MediaMonkey user since 2003)
Re: Error:Metadata Lookup (invalid mbid.) / Error: Metadata lookup (undefined)
Ticket #5028: "metadata lookup failure" has been successfully submitted
Using 5.1 LATEST alpha or beta build on Windows 10, HP laptop, managing 13k tracks
-
- Posts: 539
- Joined: Fri Dec 27, 2019 4:41 pm
Re: Error:Metadata Lookup (invalid mbid.) / Error: Metadata lookup (undefined)
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.
Ian Taylor
Re: Error:Metadata Lookup (invalid mbid.) / Error: Metadata lookup (undefined)
FYI: It was because temporal MB server inaccesibility, tracking as https://www.ventismedia.com/mantis/view.php?id=19556 to improve the messaging.
Re: Error:Metadata Lookup (invalid mbid.) / Error: Metadata lookup (undefined)
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.
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.
Using 5.1 LATEST alpha or beta build on Windows 10, HP laptop, managing 13k tracks