Classical Extras 2.0

MusicBrainz Picard
, ,
89

It’s a options page below the Plugins option. You have to expand the tree view on the left:

grafik

There is one additional thing to know: After activating the plugin the options dialog must be closed and reopened again in order for the plugin options to be available.

We (Picard developers) are aware that this is very user unfriendly. We would like to have two things:

  1. Have the options available immediately after activating the plugin
  2. Allow opening the options from inside the plugin list

There is a ticket for this already, but so far nobody has worked on this.

5 Likes
90

Oh Boy!!

Thanks a lot @outsidecontext!

91

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.)

For a simple example, here’s what Picard shows when I run the World of Warcraft: Taverns of Azeroth soundtrack through Picard:

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?

92

Arkenstone is listed as the composer. You probably have ‘Name album as "Composer Last Name(s): Album Name’ checked in the ‘Other artist options’ box on the Artists tab.

4 Likes
93

Bulls-eye. I’m sorry to have bothered you with such a trivial matter and I thank you greatly for taking the time to help me. That speaks volumes about you as a developer. :smiley:

1 Like
94

A special advice for users of Classical Extras who want to update to Picard 2.2:

  1. 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.

  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.

5 Likes
95

Quick side note: If you don’t see an upgrade button for Classical Extras, click the “Reload List of Plugins” to the bottom-right of the plugin list. That should make the upgrade button appear.

3 Likes
96

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

97

I think this error may have been introduced by the new options code in v2.0.6. I will take a look. Perhaps @outsidecontext can help as well?

98

Please note that the error reported above causes Classical Extras to fail in adding all the extra metadata, so do not use it until a fix is reported.

99

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.

1 Like
100

I’m about to install an older version of Picard to try out CE. Do you recommend going as far back as 2.0?

101

No. As mentioned above CE is not compatible with Picard 2.2, you should use the latest version before that which is 2.1.3

102

Ah, ok, thanks. I was confused by MetaTunes reply to you a bit further up noting that the error was introduced with v2.0.6.

103

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!

$if($startswith(%genre%,"Classical"),
  # Year <- Classical Extras
  $set(date,$if2(%work_year%,%originaldate%))
)

This script does populate the MusicBrainz original recording date into the date field, so I know that’s working.

104

I believe that should work.
If you do a simple test using only this script:

$set(atest,%work_year%)

And disable all other scripts and plugins, does it write the ‘atest’ tag properly?
And, did you make sure you are using Picard 2.1.3 or older?

105

Downgrading to 2.1.3 worked; hadn’t read back up the thread. Thanks.

106

I will try and find time later this month to update the plugin :sweat_smile:
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.

1 Like
107

Thanks for the update. Enjoy the December month without being distracted by computer graphics :wink:

108

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.