Plugin Registration Interoperability - Make a Plugin Optional?

Example: I want to scan for Lyrics as an option, not a constant.

The APISeeds Lyrics plugin is registered as a track metedata processor.


Can this be changed to register_album_action, register_track_action and be used on demand instead?

Other than just make a change and see what happens, is there anything stopping this from functioning fully?

This should work, I don’t see a reason why having this on demand wouldn’t work.

The only case I see where a metadata processor cannot directly be replaced by a manual action is when it needs some data that is only available in the original API response from the MB web service. But even this can be easily worked around with a combination of a metadata processor and manual action.


Now to figure out why:

E: 08:09:24,248 pluginmanager.plugin_error:181: Plugin 'apiseeds_lyrics_fetch'
Traceback (most recent call last):
  File "picard/", line 265, in _load_plugin_from_directory
  File "/Users/tdiaz/Library/Preferences/MusicBrainz/Picard/plugins/", line 123, in <module>
NameError: name 'register_album_action' is not defined
E: 08:09:39,824 pluginmanager.install_plugin:405: Unable to load plugin 'apiseeds_lyrics_fetch': Failed loading newly installed plugin apiseeds_lyrics_fetch
D: 08:09:39,824 pluginmanager._remove_plugin_files:309: Remove plugin files and dirs : 'apiseeds_lyrics_fetch'
D: 08:09:39,824 pluginmanager._remove_plugin_files:320: Removing file '/Users/tdiaz/Library/Preferences/MusicBrainz/Picard/plugins/'

Seems I ran into that before too, when experimenting with Plugins.

# register_track_metadata_processor(ApiseedsLyricsMetadataProcessor().process_metadata)

That should be all it takes? I also changed the name and version # slightly, and even removed the APISeeds lyrics zip that was there, but disabled.

Two things:

  1. You cannot just call register_album_action without importing it first
  2. You cannot simply pass the function that imements a metadata processor to register_album_action. Metadata processors and actions take different parameters, you have to adopt the code to this

Also see how you try to use a track metdata processor as an album action. This cries for code changes. Code meant to manipulate a single track won’t magically work for the album.

1 Like


  1. I told you I’m brute force learning this stuff. “Hmm… It’s already a plugin, it should have what it needs”… (and PyCharm hides the @import functions so I forget to look ‘up there’)
  2. I meant track action. Copied & Pasted the wrong line in.

I was just going to be thrilled to see it listed on the plugin menu first.

/me goes back to imploding things.

Traceback (most recent call last):
  File "./picard/ui/", line 517, in contextMenuEvent
    for index in range(1, len(action.MENU) + 1):
AttributeError: 'ApiseedsLyricsMetadataProcessor' object has no attribute 'MENU'
./run: line 5: 21658 Abort trap: 6           python3

Now to see why it’s causing the context menu to crash… Now lets see what else I’m missing / should be changing… Since it’s "a working plugin- there shouldn’t be -that- much I need to change.

Sorry if I’m an irritant, I’m not trying to be. I’m just still stuck in the era of “everything is a single listing of source code”.

I really have gotten a lot out of all this mucking around and like how the development version somewhat kind of feels even if just a teeny weeny little bit influenced by a couple of my impromptu changes and thoughts…


Don’t worry about it, people can choose to reply or not based on if they like the question :slight_smile:
Nice to have you here!

1 Like