User:VxJasonxV/Parsers Aplenty: Difference between revisions
No edit summary |
|||
| Line 1: | Line 1: | ||
There are many talented developers in the |
There are many talented developers in the MusicBrainz community, and as a result, there are lots of ways to make the task of retrieving release information and loading it into MusicBrainz much simpler. |
||
==Userscripts== |
==Userscripts== |
||
| Line 9: | Line 9: | ||
* [http://userscripts.org/scripts/show/119410 iTunes] |
* [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. Chrome support can be very hit-or-miss. Script compatibility under [http://google.com/chrome Chrome] is greatly increased when using the [http://www.chromeextensions.org/appearance-functioning/tampermonkey/ TamperMonkey] extension. |
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. |
||
==Parsers== |
==Parsers== |
||
[https://github.com/VxJasonxV/Musicbrainz-Track-Parsers Bandcamp |
[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. |
|||
[https://github.com/VxJasonxV/Musicbrainz-Track-Parsers Beatport Parser] |
|||
[https://github.com/VxJasonxV/Musicbrainz-Track-Parsers Local File Parser] (with great assistance comes great responsibility) |
|||
Latest revision as of 20:58, 12 February 2012
There are many talented developers in the MusicBrainz community, and as a result, there are lots of ways to make the task of retrieving release information and loading it into MusicBrainz much simpler.
Userscripts
Userscripts generally only work under Firefox with the Greasemonkey extension. Google Chrome support can be very hit-or-miss, Opera compatibility is very sparse. Script compatibility under Google Chrome is greatly increased when using the TamperMonkey extension.
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.
