Difference between revisions of "Editing Tools"

From MusicBrainz Wiki
(All relevant content of this WikiPage now exists under External Resources#Editing tools, so making this a redirect to there.)
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
There are many talented developers in the MusicBrainz community, and as a result, there are lots of ways to make the task of editing and expanding MusicBrainz data simpler and faster.
#REDIRECT [[External Resources#Editing tools]]
==For adding releases==
* [http://userscripts.org/scripts/show/36376 Discogs]
* [http://userscripts.org/scripts/show/117718 Bandcamp]
* [http://userscripts.org/scripts/show/119410 iTunes]
Userscripts generally only work under [http://getfirefox.com Firefox] with the [https://addons.mozilla.org/en-US/firefox/addon/greasemonkey/ Greasemonkey] extension. Google Chrome support can be very hit-or-miss, Opera compatibility is very sparse. Script compatibility under [http://google.com/chrome Google Chrome] is greatly increased when using the [http://www.chromeextensions.org/appearance-functioning/tampermonkey/ TamperMonkey] extension.
[https://github.com/VxJasonxV/Musicbrainz-Track-Parsers Bandcamp, Beatport, and Local File Parsers] (with great assistance comes great responsibility)
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, and require Audio::Scan, and at least Perl v5.10. The local file parsers are also currently format specific.

Latest revision as of 08:29, 23 February 2017