- Songkong matched to musicbrains not matched to release both full#
- Songkong matched to musicbrains not matched to release both series#
Version 2.0.2: Changed layout of tabs - the order is now Artists, Works, Genres and Tag-mapping. Version 2.0.3: Fix exception when references XML file does not exist
Then the plugin will check the listed artist against the reference list of classical composers and, if there is a match, will populate the composer metadata and set the genre to classical. If Muso-specific genre processing is selected (or XML reference file is provided including classical composers) and there is no composer (because of a lack of work relationship) Make naming of movement tags consistent with Picard docs.Īdded an option to attempt to get works and movement info from title if there are no work relationships (requires title in form "work: movement"). Version 2.0.4: Fix occasional regex backtracking crash.
Songkong matched to musicbrains not matched to release both series#
Alpha test of release series tags if Picard provides series-rels with release lookup. Version 2.0.5: Add extra error trapping for circular work references. Version 2.0.6: Fixed crash on Picard 2.2. Ability to specify additional columns in Picard UI (see detailed notes at the end of the "Advanced" tab section). Version 2.0.7: Bug fixes for compatibility with Picard 2.2+. If the Options Page does not provide sufficient flexibility, users familiar with scripting can write Tagger Scripts to access the hidden variables directly. Defaults are provided for these tags which can be added to / modified / deleted according to user requirements. Tags are output depending on the choices specified by the user in the Options Page.
Songkong matched to musicbrains not matched to release both full#
Full details of these variables are given in a later section. Hidden metadata variables produced by this plugin are (mostly) prefixed with "_cwp_" or "_cea_" depending on which component of the plugin created them. Finally, an "Advanced" tab contains additional options. There are also two tabs - "Genres etc." and "Tag mapping" which may be used provided either "Artists" or "Works and parts" (or both) are run. "Works and parts" will take at least as many seconds to process as there are works to look up (owing to MusicBrainz throttling) so users who only want the extra artist information and the tag-mapping feature, but not the work details, may turn it off (e.g. It has two main components - "Artists" and "Works and parts" - which can be used independently or together. This plugin is particularly designed to assist with tagging of classical music so that player or library manager software, which can display multiple work levels, different artist types and custom tags, can have access to these details. The "Options" page (Options->Options->Plugins->Classical Extras) allows the user to determine how hidden variables are written to file tags, as well as a variety of other options. "Classical Extras" populates tags and hidden variables in Picard with information from the MusicBrainz database about the recording, artists and work(s), and of any containing works, passing up through multiple work-part levels until the top is reached. It does work with m4a files, but Picard does not write all m4a tags (see further notes for iTunes users at the end of the "works and parts tab" section). This version has only been tested with FLAC and mp3 files.
If you are using Picard 1.4.x, please choose the "1.0" branch on github and use the latest release there - also use the earlier forum thread. It only works with Picard versions 2.0 and above, NOT earlier versions. For further help, please review the forum thread or post any new questions there. There may be beta versions later than this - check my github site for newer releases. This is the documentation for version 2.0.7 of "classical_extras".
This page contains the documentation for the Classical Extras plugin for Picard.
0 kommentar(er)
