mbsubmit: Allow submitting release after initial import

[arsaboo]

Thanks @doronbehar, for the recent additions to the mbsubmit plugin #4807. Currently, the plugin only allows submission only on initial import. We should also extend the mbsubmit command to submit the release after the initial import.

Specifically, in addition to the track listing, beet mbsubmit album:"XYZ" should also give an option to Open files with Picard.

[doronbehar]

Specifically, in addition to the track listing, beet mbsubmit album:"XYZ" should also give an option to Open files with Picard.

Just to make sure I understand, are you describing a scenario that the user has imported an album's folder "as is" or via a spotify / discogs release (via the relevant plugins) and then they wish to submit it to MusicBrainz?

[arsaboo]

That is correct...the album is already imported to the beets library with any of the tag sources (e.g., Spotify) and needs to be submitted to MB.

[Kyubai]

This would help me a lot.
Currently mbsubmit is using before_choose_candidate_listener, but it would have to trigger after the candidate (spotify, deezer, etc. match) has been chosen.

Here's an example:

As you can see spotify provides the correct album info, but pressing p only prints the information from my local file.
Once I choose Apply beets will move on the the next track and I can't print the correct metadata anymore

[doronbehar]

@Kyubai are you using the latest unreleased beets? With #4807 included? I'm not sure I understand what you are trying to say about the event before_choose_candidate_listener - The menu you showed above should I think give you the prompt choice to open the files with Picard.