Userscript to add and import voice actor credits

Discussion and support thread for my new userscript:

Voice Actor Credits

Install Source

  • Simplifies the addition of “spoken vocals” relationships (at release level) by providing a pre-filled dialogue in the relationship editor.
  • Imports voice actor credits from linked Discogs pages.
  • Automatically matches artists whose Discogs pages are linked to MB (unlinked artists can be selected from the already opened inline search).
  • Caches Discogs to MBID mappings (to reduce API calls) and collects mappings for freshly matched artists (which were chosen by the user)
  • Shows links to seed artist edit pages with the Discogs URLs for these new matches.
5 Likes

That “install” button doesn’t do anything on my Greasmonkey \ Vivaldi setup. Source is also a duff button. Can you supply linkies?

1 Like

Sorry for that, I had explicitly copied these image links from my README on GitHub to be sure to make no mistakes, but I forgot that these are relative links :joy:
They should work now, I have converted them into absolute links. Thanks for the hint.

1 Like

My browser monkey says it works now. I am a good tester who can break anything. :joy:

image

…thank you soooooooo much :grin:

1 Like

It’s been a long time since I had announced any new userscript features in this thread, so I’m going to do that today:

Parse voice actor credits from text

In addition to importing voice actors from Discogs, you can also parse them from almost any text source now. Actually, this feature has been available for months, but I haven’t seen anyone (besides me) using it yet.
Below are a few example lines which work out of the box:

Sherlock Holmes: Clive Merrison
Narrator - John Doe
Women at the Station	Jane Doe

Using the advanced configuration option Credit separator, the parser can deal with any kind of separator, as long as each line contains the name of the actor and the name of their role. Actors and roles can also be in reverse order, simply hold SHIFT while clicking the button to swap them.

Once you’ve matched an artist entity for a given artist name the first time, the script remembers that and will no longer ask you to select an artist again. That probably sounds familiar to the users of my copyright parser script, both scripts share the same mapping cache and the UI:

Support for the new releationship editor

For those who are/were already testing the new React relationship editor on the beta server, I’ve released a new version (of the userscript) today which also supports the beta server (in addition to the old relationship editor on the regular production servers). The new code is basically an almost complete rewrite as a lot of internals of the new relationship editor work differently, so feel free to test it.

Without the help of @Bitmap, who has implemented almost all the “userscript backdoors” in MBS for which I had asked (e.g. exposing the functions to create relationship dialogs), porting the userscript would not have been possible at all. Thanks a lot!

4 Likes

Hi @kellnerd

Is it possible to extend this script for importing other release level relationships from Discogs … as the basic functionality seems to be there already ?

I used to use the following userscript from mattgoldspink - https://github.com/mattgoldspink/musicbrainz-userscripts/blob/feature_fix_always_render_button/import-relationships-from-discogs.user.js
but unfortunately he didn’t react on pull requests (see Pull requests · mattgoldspink/musicbrainz-userscripts · GitHub) and nowadays (probably because of the new react based UI) it doesn’t work anymore … actually it sometimes loads (I have now idea what triggers it) when using “Edit Relationships” on a release, but then displays the following error “Could find Add Relationship button for #release-rels [data-click=“openAddDialog”]” and does nothing as can be seen from the following screenshot

Maybe this is easy to fix but all this .js script stuff is way behind my horizon … :frowning:

1 Like

Sure, supporting more relationship types (be it from Discogs or from text input) has been on my wishlist right from the start:

Unfortunately I didn’t have enough time to continue working on this idea during the last year. Maybe I will get there by the end of 2023, but I can’t promise it.

2 Likes