External Resources: Difference between revisions

From MusicBrainz Wiki
Jump to navigationJump to search
(typo)
Line 40: Line 40:
* [https://www.npmjs.com/package/music-metadata-browser music-metadata-browser] JavaScript NPM module, to parse audio tracks in the browser.
* [https://www.npmjs.com/package/music-metadata-browser music-metadata-browser] JavaScript NPM module, to parse audio tracks in the browser.


:: These metadata parser extract virtual any type of metadata from any type of audio track, including [[MusicBrainz Identifier | MusicBrain Identifiers]] or other metadata tags supported by [[MusicBrainz Picard]].
:: These metadata parser extract virtual any type of metadata from any type of audio track, including [[MusicBrainz Identifier | MusicBrainz Identifiers]] or other metadata tags supported by [[MusicBrainz Picard]].
* [https://gist.github.com/fxthomas/fd85e906e41f4e6e06f38e92a497005b vgmdb2mb.py] VGMDB to MusicBrainz import script
* [https://gist.github.com/fxthomas/fd85e906e41f4e6e06f38e92a497005b vgmdb2mb.py] VGMDB to MusicBrainz import script



Revision as of 11:45, 12 January 2021

Note: this page needs more flesh and to be linked to.

This page tries to list all tools external to MusicBrainz that make editing or viewing data more convenient. These include any programs, scripts, reports, etc from various sources.

Editing tools

User scripts / GreaseMonkey / User javascripts / UserJS

See Guides/Userscripts.

User scripts are javascripts that a user installs in one’s browser and that change the behaviour of visited website (MusicBrainz). Those scripts will add some functionalities to MusicBrainz or let the user do many repetitive things in only one click, etc.

Some user script repositories (alpha sorted):

Other known places with userscripts:

※ Here is a bitbucket/github/gitlab userscript installer (it adds green icons to INSTALL scripts directly from those repository file lists)

Parsers

These parsers are meant to be run at the command line passing in either a URL (Bandcamp release, or Beatport release), or a directory with a set of files. The local file parsers run on all files in a directory with the same extension, and are intended to output a whole release, suitable for copying / pasting into the tracklist page's Track Parser. They are written in Perl, require at least Perl v5.10 and a differing set of Perl Modules based off the particular service. The local file parsers are currently format specific.
These metadata parser extract virtual any type of metadata from any type of audio track, including MusicBrainz Identifiers or other metadata tags supported by MusicBrainz Picard.

Valuable online databases

See Other Databases.

URI Description Comments (on reliability etc...)
http://www.discogs.com/ Discogs
http://allmusic.com/ Allmusic
http://en.wikipedia.org/ Wikipedia
http://amazon.com
http://amazon.co.uk
http://amazon.fr Releases dates often wrong
http://amazon.de Often omits to mark imports as "[Import]"
http://www.metal-archives.com Encyclopaedia_Metallum
http://www.encyclopedisque.fr For French vinyls
http://www.lpdiscography.com/ Has dates, labels, and catalog numbers

About amazon's [Import] label not trustworthy, here is the smoke-proof to check whether the IMPORT is bogus or not on .fr Switch the tld to .de: http://www.amazon.de/gp/product/B00004UH7R Check what they have as a label, in this case: Label: France (Megaphon Importservice) => it comes from france, and the [Import] is on .fr is bogus.

Access MusicBrainz using external APIs

See MusicBrainz API libraries

MusicBrainz data ported to other systems

Other

Old