@Billy_Yank and @jesus2099 the example I am working on here is extreme. We are talking huge “audio drama” set of disks. Twenty Five CDs with average 20 tracks on each disk. Many of those tracks are multiple parts so multiple speechmarks opening and closing.
The example above is part of that larger box set. So we also have this as separate releases. And that is where the hiccups start as some of those separate releases have had the speechmarks done, but others haven’t.
Yeah, I can see how with search and replace and messing with various rules I can try and catch the speechmarks - but this is complicated by the Unicode need of different quotes for opening and closing. And then as we have quotes in quotes (see track six above) there is going to be quite a weird rule that needs constructing.
Copy and Paste will be similarly messy as I’ll need to have a staging post in Notepad++ where I clean up anything I move. Though that is going to be the least complex to do I think.
I’ll work something out. I came here hoping for a “magic button” as I assumed I wasn’t the only person who has seen this occur. There must be many places where a recording appears on multiple releases. I’ve often had to manually go through multiple copies of the same to propagate a correction back up from the recording to all the separate releases.
@culinko Reading your ticket I think you get my point exactly. As someone else said on the ticket, it is something that needs to be visual and show you all the tracks about to be changed. And it must get hidden behind some kind of advanced\expert mode as that could cause utter chaos for new users!
Propagating corrections like this could be made simpler. And if it was simpler, I’d do even more of them.
According to your image and using the appropriate MB terminology:
The recording name is correct as well as 3 track names.
Remain 7 track names with typewriter apostrophes.
So what you would like is “Update all tracks” (from recording).
For those who came across some releases that would completely freeze their browser, an INLINE STUFF performance bug has been fixed today, and it should no longer happen.
Thanks to @Mitch2323 for suggesting an important clue on how to fix this old bug:
When I open up a five CD set with 20 tracks on each disk that is at least 100 AcoustID items being pulled from somewhere. Just curious if this is coming via that API? I may toggle these off on my screen if they are as I rarely look at those numbers or interact with them.
Hello again nice INLINE STUFF userscript. Very handy. Thanks again for your time saving and error spotting abilities.
BUT there is a new update that clashes a bit with what I work on. Can I disable single features of the addon?
Look at the confusion caused by the attempt to spot Recording length errors. These are combinations of bootlegs, vinyl and reissues in here. Everything is marked as “not equal” which is misleading and odd.
Can we adjust the error range of this check? Or even better, just disable it?
INLINE STUFF is great, so I don’t want to disable the whole Userscript. Just remove this feature as bootlegs just are not that accurate. Thanks.
I’ve also never understood which time is getting chosen to be the set time up there in the corner as it matches none of the releases on the page. Even if the slack was a couple of seconds either way would help.
Okay, now you have confused my Maths OCD. Why is this Recording not being flagged like the one above? The Recordings towards the bottom are three seconds out… does it only do the first dozen?
For me, a perfect solution would be a 10% margin of error. I am trying to read and understand the script and it seems to work on exact matches. Don’t think I even see that when working with only CDs from the same manufacturing plant.
Or am I making this break because I have a script that displays thousandths of a second for CDs? (I am investigating and updating this post as I learn more…)
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 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).
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.
5 seconds really isn’t much of a difference when it is common to fade a track out on a bootleg.