#musicbrainz

(wich is really really huge bits)

I know webdev is hell, but this is beyond scary

aw come on, devs are working hard on everything and doing react

not entierly sure how many working on it it is

oh I'm not blaming the devs, I'm blaming React :P

it's bitmap and reo, i tihkn maybe also yvanzo?

oh i see :D

thanks for the update though! I'll stay excited :)

i wouldnt say webdev is hell

its fine

its just .... there's probably a trillion little details

cause thats how that always goes

11:03 < dominikh> you might as well overlay two FFTs and look for visual differences :P

if they're the same duration, you can use ffmpeg to subtract one of them from the other and listen to the difference, heh

(or visualize it)

oh, I see, in scrollback, Erin mentioned a technique to do that in Audacity

ROpdebee, it works with violent monkey, same script version, same os/browser/other extensions

I tried with tampermonkey as the only extension in private tab, doesn't work

I tried disabling all my scripts in TM except yours, doesn't work

I'm stumped

I'm talking about this https://musicbrainz.org/edit/83037449

probably find out

https://ototoy.jp/_/default/p/927688 finding other sources might help

I searched on ddg for guidelines about that, the link I already posted is all I could find

thanks, I'll post the link

https://music.oricon.co.jp/php/cd/CdTop.php?cd=... here too

it's not fair tho that they could do their edit without me getting a chance to vote, and now I have to prove that my first version was correct

I'm inclined to side with accurate lengths over poorly rounded and cargo-culted ones

wait

if you go to his original edit

he links apple, deezer, and spotify

they all show 16, 23, 22, 14

which he is getting rid of

Erin: as a brief piece of chat meta, my personal opinion is that your line lengths could be a little bit longer, to avoid scrolling chat as much. especially with single word lines like "wait" :)

lol

King_DuckZ: ;P

looking at the other link he has that includes the decimals

..... i just cant find anything in this to support his conclusions

he's basically saying he would like to apply his own rounding preferences instead of the one literally /everyone/ uses

I tried to keep discussions grouped, but there are a few that overlap https://musicbrainz.org/release/416ade1e-7319-4...

well I'd appreciate if you guys could jump in and vote, at least to break the tie otherwise it's my opinion vs his

yeah I don't get it. Track 1 in iTunes is 256050 ms. how does that round to 4:17?

technically, 00-49 round down, and 50-99 round up

but thats only rounding, not just some kind of "all things must follow this rule"

even so, 256050 ms is 4 minutes and 16.05s. that doesn't round to 4:17 :P

realistically, there's nothing out there that says mathematical rounding is preferable over truncation, or something like that, or that we somehow prefer to disagree with published versions

so what this other guy is doing essentially is just saying his preference for how the fraction is resolved is greater thant he value of matching publication, which is .... false

he's voting against my other edits too https://musicbrainz.org/edit/83042086

well thats just not cool

is it true what he's saying? if so, what's the point of many releases having the 96 kHz thing in the disambiguation then?

although i would have to read that

dominikh : i think you voted no on correcting this by mistake maybe?

cause your comment indicates that you would agree with it

anyway my comment is in and i have to eat

good luck

i'll read the other when i return

Erin: I actually side with accurate rounding; though I do wish the comment and vote were indicated separately, as they were made separately

Has anyone really been far even as decided to use even go want to do look?

Erin: discussion sort of started here https://musicbrainz.org/edit/83000533 for context

IIRC both musicbrainz importing from existing data, and Picard, round instead of truncate

well if he's right then he's right, just in all releases I made based on mora.jp I copy-pasted the info from there, and I'm not going to check the millisecond duration and doing rounding by hand on each track (I don't even have the files, sometimes). I think it's best to keep the published length, picard is able to tell that 1 second difference doesn't matter anyways

but if you all agree then I'm fine with dropping this edit

well apparently we're not all agreeing :P

does Picard ignore a 1s difference, or does it round?

that I noticed, every time length is off by 1 it's not marked in orange

that's all I can say

...and he voted against this too https://musicbrainz.org/edit/83042224 /facepalm

is it true that there is no distinction between hi-res and "regular" releases?