Script set-recording-comments.user.js


The script to update massively the comments on recordings from a release is no more working.
Could you confirm if it happens to other people? It could be linked to last update with the change on loading release page.



Me too. Lots of broken and wobbly scripts at the moment caused by major changes in the way a webpage is written and displayed. Am especially missing the Mass Comments button for adding ETI to gigs.


It’s still working for me most of the time at the moment. However, on some releases it’s not showing up. The mass recording merge is completely broken now as of the new changes to MB. It’s a known new issue and is trying to be resolved.

Yes, you can still try to reload the MB release page when you need to use a release userscript that does not work correctly (like my INLINE STUFF and @Bitmap’s set recording comments).
It depends if the script is run too fast (before some MB tracklist page redraw that break it) or slow enough to run without trouble.

MASS MERGE is fixed, except for releases with many tracks (new track paging system).


Thanks a lot
Any timeline for the other scripts or it will be: “Done when it s done” :slight_smile:


Finally, I have taken over the initiative (again) to fix this userscript, which was surprisingly easy, and have submitted a PR:

I would appreciate it if some users could test the new version with different browser / userscript manager setups to verify that this is not only working for me and my (Violent)monkey :wink:


If I could work out what to install I’d give it a run around… can I get a linky for us non-gits and I’ll attempt to break if for you. Pressed loads of buttons and worked it out. Will let you know if I break it.

Edited to add: Button is back!! Woo!! and Yay!! Happily appears on a 1CD or a 10CD album without care. Quick tested a few disambigs to see if it works. Nothing exploded. Happy on Vivaldi \ Violent Monkey \ Windows.


It still doesn’t work on a 10 disc album. The mediums that are dynamically loaded will never receive comment text boxes.

1 Like

I did the test changes on a four disc album. It was more the fact the button appeared and stayed on screen was the key on the 10CD album. So no regression.

Just had a quick look and seems working as before.
Will test more when will make some edits.

Regarding the problem of multiple CDs there could have a a workaround by trying to make it work when loading directly a specific medium from a release: Release “Classic Chu Berry Columbia and Victor Sessions” by Chu Berry - MusicBrainz

1 Like

The fix has been merged this weekend and since there have been no complaints about issues with other browser setups, I would consider this as solved for “normal releases”.

Regarding the usage for medium 11+ on bigger releases I am not even sure if this had ever worked (or I never needed this script for such a medium which is collapsed by default). The trick @ulugabi mentioned should help in these cases, right now every(?) userscript which I am using seems to struggle with these dynamically loaded mediums and a thorough fix would require more work.


I use Tampermonkey on Edge and moved this script to run last and I still have to reload the page on every release page even on singles.

1 Like

The following from the script would seem to stop the script from running when when adding “/disc/6” for the workaround. It’s actually working for some people?
@exclude **/*

I can say I haven’t yet found a way to use this script for disc >5 using Firefox + Tampermonkey.

1 Like

Hi @ulugabi, very good idea, this basic work-around to load disc URL!!
I have included it in this new PR:

The previous @kellnerd document-idle fix was no longer enough for my browser.
React would still remove the button 9 times of 10.

For what it’s worth, here are the real pending pull requests (they are little bit lost among automatic pull requests).

Update (2022-02-17)

Delay script OK it fixed for me.
But the medium URL work-around was not working and was quickly fixed by @kellnerd.


I seem to be having trouble with this initially loading comments from another medium.

Ah yes of course.
The work-around is only a work-around to enable the script for all the tracks of 1 particular medium. A medium that would otherwise be ignored as being collapsed.

Right. I installed the version with the pull request included. I added ‘/disc/4’ to the URL. I clicked the button to show the comment boxes. They were already populated with the comments from another medium (medium 3, I think). The script got a little confused, and boxes were not red that should be (it thought the comment was not changed, even though it was a new comment). Still, it did seem to set the comments on all of the recordings.


Also, if I recall correctly, after setting the comments, if I loaded it the same way again, it would have the comments from another medium again, rather than the actual comments.

1 Like

Oh crap, @kellnerd, can you revert my change, urgently? But keep the timeout?
Sorry guys.

I guess a proper fix would be the better solution, so I created a PR instead:

This time I would like more people to test or review this before I will merge it :sweat_smile:

(The last time I only checked whether the script was loading any comments, but I did not verify whether these were for the correct recordings. For this PR I actually did an editing test with @ulugabi’s example release on the test server and it worked.)