Doesn’t work for this release #COMPASS COMbat Providence AnalysiS System ORIGINAL SOUNDTRACK Vol.02 | DUED-1263 - VGMdb but works for others.
VGMdb.net doesn’t have an API, and vgmdb.info is very broken. I would say the userscript does more harm than good for MusicBrainz, considering how many of these imports I’ve had to fix.
1 Like
Script might need to be updated again, doesn’t seem to work as intended anymore.
Uncaught SyntaxError: JSON.parse: unexpected character at line 2 column 5 of the JSON data
parseApi moz-extension://65958e12-29a0-4ed6-88f3-af58d20de004/ Import VGMdb releases into MusicBrainz.user.js#293:584
onload moz-extension://65958e12-29a0-4ed6-88f3-af58d20de004/ Import VGMdb releases into MusicBrainz.user.js#293:577
et/b</t[We]< moz-extension://65958e12-29a0-4ed6-88f3-af58d20de004/sandbox/injected-web.js:1
HttpRequested moz-extension://65958e12-29a0-4ed6-88f3-af58d20de004/sandbox/injected-web.js:1
onHandle moz-extension://65958e12-29a0-4ed6-88f3-af58d20de004/sandbox/injected-web.js:1
Ne moz-extension://65958e12-29a0-4ed6-88f3-af58d20de004/sandbox/injected-web.js:1
Use ame instead which doesn’t depend on a third-party service:
2 Likes
I was unaware of that! Thanks for linking it. If that’s not on the wiki for useful scripts, it should be added.
2 Likes
Wow, I didn’t know them either.
@chaban already added them to the page, except the MusicBrainz Works script (search SuperSaltyGamer):
1 Like
The NAB repository isn’t loading for me, so I can’t report the issue there for now, but when it “matches” an MB release to the page, it sometimes links a completely different release.
https://vgmdb.net/album/3980
links me to
https://musicbrainz.org/release/30061cac-8b66-4ab1-8a16-a0120ff9d9f9
It’s not a big deal for me since I’ve been using a similar script made by a VGMDB editor which pulls up the barcode or the VGMDB URL, so there’s no chance of it redirecting to the wrong page.
View (blob) link instead of install (raw) link, for those who want to check it out before installing blindly. 
How many VGMdb scripts do we have, then?
Something like 3 or 4, wow.
Just two that work, I think. The Ame import script linked above, and that one.
ame searches for existing releases by catalog number and barcode
For that release there are two results:
http://musicbrainz.org/ws/2/release/?fmt=json&query=catno%3ASKR036CD
{
"created": "2024-06-24T15:04:57.001Z",
"count": 2,
"offset": 0,
"releases": [
{
"id": "30061cac-8b66-4ab1-8a16-a0120ff9d9f9",
"score": 100,
"status-id": "4e304316-386d-3409-af2e-78857eec5cfe",
"count": 1,
"title": "Visions of the Haunted",
"status": "Official",
"text-representation": {
"language": "eng",
"script": "Latn"
},
"artist-credit": [
{
"name": "Crowned in Earth",
"artist": {
"id": "743883b4-b2b0-491e-b94f-cd709975c58b",
"name": "Crowned in Earth",
"sort-name": "Crowned in Earth"
}
}
],
"release-group": {
"id": "f3b1aafc-e05e-43cc-8633-75ef5a493002",
"type-id": "f529b476-6e62-324f-b0aa-1f3e33d313fc",
"primary-type-id": "f529b476-6e62-324f-b0aa-1f3e33d313fc",
"title": "Visions of the Haunted",
"primary-type": "Album"
},
"date": "2010-05-20",
"country": "US",
"release-events": [
{
"date": "2010-05-20",
"area": {
"id": "489ce91b-6658-3307-9877-795b68554c98",
"name": "United States",
"sort-name": "United States",
"iso-3166-1-codes": [
"US"
]
}
}
],
"barcode": "884502469783",
"asin": "B003TOS84Y",
"label-info": [
{
"catalog-number": "SKR036CD",
"label": {
"id": "6bcbdc51-f2ba-4c50-8625-074d75de9093",
"name": "Shadow Kingdom Records"
}
}
],
"track-count": 5,
"media": [
{
"format": "CD",
"disc-count": 1,
"track-count": 5
}
],
"tags": [
{
"count": 1,
"name": "rock"
},
{
"count": 1,
"name": "doom metal"
},
{
"count": 1,
"name": "prog rock"
}
]
},
{
"id": "c26bddaf-9824-4dc3-8dfc-bb4aa8585b4d",
"score": 100,
"status-id": "518ffc83-5cde-34df-8627-81bff5093d92",
"count": 1,
"title": "ABANDONER",
"status": "Promotion",
"text-representation": {
"language": "eng",
"script": "Latn"
},
"artist-credit": [
{
"name": "kt2",
"artist": {
"id": "dc2e8959-bf1c-43b7-89f6-4368c3768bf6",
"name": "kt2",
"sort-name": "kt2"
}
}
],
"release-group": {
"id": "62686932-b2ec-4372-bd5a-dbdc649b95e0",
"type-id": "22a628ad-c082-3c4f-b1b6-d41665107b88",
"primary-type-id": "f529b476-6e62-324f-b0aa-1f3e33d313fc",
"title": "ABANDONER",
"primary-type": "Album",
"secondary-types": [
"Soundtrack"
],
"secondary-type-ids": [
"22a628ad-c082-3c4f-b1b6-d41665107b88"
]
},
"date": "2004-09-17",
"country": "JP",
"release-events": [
{
"date": "2004-09-17",
"area": {
"id": "2db42837-c832-3c27-b4a3-08198f75693c",
"name": "Japan",
"sort-name": "Japan",
"iso-3166-1-codes": [
"JP"
]
}
}
],
"label-info": [
{
"catalog-number": "SKR-036CD",
"label": {
"id": "28182e39-c763-4a9f-8f3e-c8b7f3b79562",
"name": "HOBIBOX"
}
}
],
"track-count": 20,
"media": [
{
"format": "CD",
"disc-count": 0,
"track-count": 20
}
]
}
]
}
The linker script by @Toad_King goes the safer route by using URL and barcode. It can also link multiple results and highlights MB results with missing VGMdb link or missing barcode:
https://vgmdb.net/album/30421
Thanks for the heads up re the working import script/ame! I will be using it occasionally.
I have also added the ‘VGMdb Musicbrainz Links’ to the userscript wiki page. If I made any mistakes please let me know.
Nice that the two scripts seem to be compatible.
1 Like
VGMdb API seems to be down for about a year now. https://vgmdb-y-young.cloud.okteto.net/ is not working either.
Is there currently a working solution allowing to query the API at all?
I’m primarily asking in the context of the MB import script. I had to put up this notice feat(vgmdb_importer): update script to handle VGMdb API unavailabilit… · murdos/musicbrainz-userscripts@dc10ad3 · GitHub since the script is defunct now, but I’m looking for ways to make it work.
Thank you!
That link resulted in a 404.
I’ve just explored that script, and it doesn’t use an API, it parses the DOM.
What’s the issue with that? VGMdb has no API yet
There’s no issue, I was just asking about an API specifically in my first message.
Is there currently a working solution allowing to query the API at all?
As I mentioned, I’m trying to fix a broken script that is relying on the API. There’s probably no point in completely rewriting that script with DOM parsing, since the script you linked already does that.
You seem to be conflating the non-existing official API and the third-party drop-in solution (vgmdb.info) which also has to scrape the site.
I wouldn’t hold my breath for it, it now requires a cookie from a VGMdb user to work.
So your options are to setup your own instance of the third-party API and feed it a cookie or use the other script.
However it seems that cookie can expire easily: