I’m not sure if this is a result of Classical Extras, but lately I’ve noticed that the artist’s last name is being placed before the album title on everything. (Well, as long as the artist isn’t Various Artists.)
I cannot identify where the problem lies. I’ve already ruled out the two scripts that I use, as they only set the Track number and Total Tracks number to be double-digits. And since this is a tagging issue, the File Renaming script is irrelevant. That leaves only Classical Extras. Any thoughts on where in the maze of CE settings I might be able to find the culprit?
A special advice for users of Classical Extras who want to update to Picard 2.2:
If you have not yet installed Picard 2.2, please open the Options > Plugins and update the Classical Extras plugin. The version should be 2.0.6 or later. After you have updated Classical Extras you can safely update to Picard 2.2.
If you have already installed Picard 2.2 you will be unable to open the options dialog if Classical Extras < 2.0.6 is installed. In this case follow the instructions in the following post to manually upgrade Classical Extras.
TypeError: string indices must be integers?
Hi, am new to Picard (running 2.2.1 on a Mac) and Classical Extras (great plugin - installed v2.0.6 from within Picard). When I tag albums I get lots of errors that appear like the one below - all apparently referring to the same line of code.
Am I doing something stupid or is this a known bug? Many thanks!
"Traceback (most recent call last):
File “picard/album.py”, line 404, in _finalize_loading_track
File “picard/metadata.py”, line 409, in run_track_metadata_processors
File “picard/plugin.py”, line 219, in run
File “/Users/psollich/Library/Preferences/MusicBrainz/Picard/plugins/classical_extras.zip/classical_extras/init.py”, line 4138, in add_work_info
self.ERROR = options[“log_error”]
TypeError: string indices must be integers
It looks like something changed in Picard 2.2 which has the effect of stripping all dictionaries saved as metadata - just saving a list of the keys with no values. This is fundamental to the operation of Classical Extras. I recommend that Classical Extras users do not upgrade to Picard 2.2. until this is fixed.
Hi. I’m looking to use Classical Extras to add composition dates to my classical collection, but I can’t seem to use the work_year (from the Genre’s etc. tab under Periods and dates) in my scripts to add this to other fields. This is my first venture into scripting Picard, so it’s entirely possible that’s what’s not working; any input appreciated!
# Year <- Classical Extras
This script does populate the MusicBrainz original recording date into the date field, so I know that’s working.
I will try and find time later this month to update the plugin
Edit: failed in that objective as my new pc build went awry owing to a faulty graphics card. Hopefully will get that fixed shortly and start work on this in early January.
Just starting to take a look again at the issue of Classical Extras not running properly under Picard 2.2.x, now that I have a working PC. On first inspection, it seems that most of the problems have gone away in Picard 2.3.0a1 - any clues @outsidecontext? I’ll look into it more fully next week. Until then, belated seasonal greetings to all Classical Extras users.