Version 2.0 of my plugin for Picard - “Classical Extras” is now available as a beta release. This is basically a re-engineered and enhanced version specifically for use with Picard 2.0.x.
A brief summary of what it does:
Classical Extras provides tagging enhancements for artists/performers and, in particular, utilises MB’s hierarchy of works to provide work/movement tags.
All options are set through a user interface in Picard options->plugins. While it is designed to cater for the complexities of classical music tagging, it may also be useful for other music which has more than just basic song/artist/album data.
The options screen provides five tabs for users to control the tags produced:
1. Artists: Options as to whether artist tags will contain standard MB names, aliases or as-credited names.
Ability to include and annotate names for specialist roles (chorus master, arranger, lyricist etc.).
Ability to read lyrics tags on the file which has been loaded and assign them to track and album levels if required.
(Note: Picard will not normally process incoming file tags).
2. Tag mapping: in some ways, this is a simple substitute for some of Picard’s scripting capability. The main advantage is that the plugin will remember what tag mapping you use for each release (or even track).
3. Works and parts: The plugin will build a hierarchy of works and parts (e.g. Work -> Part -> Movement or Opera -> Act -> Number) based on the works in MusicBrainz’s database. These can then be displayed in tags in a variety of ways according to user preferences. Furthermore partial recordings, medleys, arrangements and collections of works are all handled according to user choices. There is a processing overhead for this at present because MusicBrainz limits look-ups to one per second.
4. Genres etc.: Options are available to customise the source and display of information relating to genres, instruments, keys, work dates and periods. Additional capabilities are provided for users of Muso (or others who provide the relevant XML files) to use pre-existing databases of classical genres, classical composers and classical periods.
5. Advanced: Various options to control the detailed processing of the above.
All user options can be saved on a per-album (or even per-track) basis so that tweaks can be used to deal with inconsistencies in the MusicBrainz data (e.g. include English titles from the track listing where the MusicBrainz works are in the composer’s language and/or script).
Also existing file tags can be processed (not possible in native Picard).
A slight health warning: classical music tagging is quite a complicated matter, so the plugin necessarily has a large number of options which may initially be daunting; it is important to fully read the the comprehensive documentation in the “readme” file. Once you have determined the options which fit your requirements and
music software ecosystem, however, it does very much streamline otherwise complex tagging (assuming the data is in MusicBrainz ) For more context on how to use it, see my website.
Get the zip file to install the plugin here. If there are any questions (after reading the readme) or issues, please post to this thread.