HAHA - you try telling my OCD that. 
Thanks for listening. I am in no rush.
1 Like
Yes, in fact, I never see my yellow marks as errors but as interesting bits.
But you’re right it would be more useful to highlight potential errors, indeed, instead of flooding the display with fancy blinking lights.
I see that MBS is warning when there is 15 seconds or more of difference between two recording lengths.
I think I should change the script to display 15+ seconds diff as errors (red) and 5+ seconds (a third of error) as .name-variation (current light marks).
Here is the initial ticket, implementing automatic recording times.
Thanks very much for your insight, I never noticed this one in 7 years!
I should change the script to check more than 25 tracks! 
Disc ID set milliseconds to track length, but these are never shown in MBS (only in web service / API).
They are revealed by the userscript! 
BTW, your STAY example shows that all tracks that have a Disc ID, are exactly 4:05.333 same as recording computed length. 
4 Likes
Thanks @jesus2099 - I’ll read this closer in the morning when the brain can process it better.
The “15 seconds or more” warning from MBS is a bit random. I would have thought a percentage error would make more sense. Maybe I am just editing long Recordings 
5 seconds really isn’t much of a difference when it is common to fade a track out on a bootleg.
For me both of these times are too short would just flood too much noise into the userscript and I’d be back trying to work out how to mute it.
The ticket that says “average recording times” isn’t what I observe. I’ve see it take the time of one, and ignore the other. (but too tired to find that example now and it is OT)
Glad I could spot that “check more than 25 tracks” would be useful.
The milliseconds being revealed was added by a userscript, but no idea which one. Is it this one? That is very useful to telling CDs with discIDs and Vinyl apart. Often I find Vinyl with typos (or a typo on the cover art)
Something is broken on my Stay example as I am missing all my milliseconds on those tracks. Still visible on Embryo. Eh? Yeah - too late for my head to solve those now and very OT.
2 Likes
Exactly my thought, it was only after expanding the hidden comments that I saw the final decision was to use the median track length, not the average 
2 Likes
Since the last update my inline stuff has broken on Opera + Tampermonkey
can I roll this back to previous version.
trying a fresh install on firefox + Violentmonkey
doesn’t at all, gives
“Error loading dependencies.” (infact most your scripts do)
Thanks for the hard work @jesus2099
1 Like
Did a bit more digging
Greasemonkey reports
User script download failed
null at https://cdn.jsdelivr.net/gh/jesus2099/konami-command@ab3d205ab8a9897ac3ef23075fda26bed07ca342/lib/COOL-BUBBLES.js?v=2016.6.1.1310
null at https://cdn.jsdelivr.net/gh/jesus2099/konami-command@4fa74ddc55ec51927562f6e9d7215e2b43b1120b/lib/SUPER.js?v=2018.3.14
I think it’s a DNS issue
FYI
1 Like
You don’t have access to https://cdn.jsdelivr.net with your browser, now?
These URL are necessary as long as I stay in greasyfork but I plan to leave both Greasyfork and Openuserjs sooner or later.
If you cannot access these URL, you can (re)install the scripts from GitHub and then replace (in the // @require lines):
https://cdn.jsdelivr.net/gh/jesus2099/konami-command@
by:
https://github.com/jesus2099/konami-command/raw/
1 Like
jsdelivr.net is skcetchy for me, sometime works, sometimes not
currently getting “ERR_CONNECTION_REFUSED” on Opera (Chrome)
Thinking my ip might be blocked,I have even tried various vpn across the globe.
Earlier on worked and the scripts installed and are currently working now.
Thanks, sorry for the bother.
1 Like
I’m very embarrassed to say but it was all my fault!
Not sure why, but I had block on the site in my hosts file, I’ve now comment it out
127.0.0.1 cdn.jsdelivr.net
so now all is good, feel such a fool.
Please accept my sincere apologies.
5 Likes
Just a heads up to say I know this script is currently broken.
And also I intend to stop using cdn.jsdelivr.net soon.
4 Likes
AcoustIDs and ISRCs not working for me. But it is working 2 days ago. Is it related to last server update?
2 Likes
Yes it must be that.
I had a bug report for beta server some days ago, beta version might have been released to production (MBS), now.
I don’t remember exactly but I remember I have a good track of fixing it, thanks to @Bitmap discussion.
Workaround to run this script near the end of my userscript list worked for me (mobile and PC), but it didn’t work for Alfge and redactedscribe.
So I have now added quick workaround in the code, as @ROpdebee suggested, until the real fix, that I have no time to do in the very near time.
2 Likes
I will work again on this script bug, because the work-arounds are still not enough for some releases like this one, and others too, as seen below:
Did this script stop working recently? Mine hasn’t worked in at least 4-5 days. I understand it could take some time to fix, but wanted to know if it’s broken for others as well.
1 Like
Can you give me a URL and tell me what you expected and what’s not showing up?
It’s quite random until I fix the last linked bug, though…
1 Like
I primarily rely on the script to easily view/click ISRCs and AcoustIDs from the release page. Here’s an example release where the recordings have ISRCs and AcoustIDs attached, Release “Freddie” by Freddie Gibbs - MusicBrainz. Today it looks like this:
I’m used to the ISRCs and AcoustIDs showing up “in line” underneath track titles. I could only find one old screenshot of a single track on a release depicting this, but I think you know what I’m saying 
1 Like
It works for me.
Did you click ISRC and AcoustID show button in the sidebar?
Android Kiwi Browser with Violentmonkey
Did you try the clumsy workaround (move the script at the end of the script list)?
1 Like
I do not see the object in the sidebar. I’m running Chrome (Version 114.0.5735.135 (Official Build) (64-bit)) with Violentmonkey. Troubleshooting:
- Move script to last in violentmonkey > no change
- Disable all other scripts (16) running on release page > no change
- Uninstall and reinstall script > no change
- Try on different PC (Chrome) > works as expected
- Try in incognito mode on original browser > works as expected
- Clear browser cached files and images > still not working
- Close and re-open Chrome > still not working
Unfortunately I think I need to clear my cookies and site data for musicbrainz.org.
The culprit is the Dark Reader extension (Dark Reader - Chrome Web Store). Disabling the extension allows the script to function as expected. Unfortunately it’s my primary way to modify the MusicBrainz UI to prevent it from blinding me with brightness. Guess I’ll find workarounds. If anyone has suggestions for another ‘dark mode’ extension please do tell
Thank you @jesus2099 for your kind support and all of your scripting efforts which make us way more productive around here.
I guess the most natural things would be user stylesheet installed in Stylus extension.
I guess it should already exist, somewhere.
2 Likes