A 2:!5 AcoustID fingerprint shouldn't be assigned to a 2:31 track, should it?
*2:33
*2:15
( luks hawke_ )
function1
seems you guys don't have much interest in acoustid for anything other than identification of poorly named files, e.g. track01.wav
so who cares? but i try to be a purist
Freso: also, on that edit, would you vote it down? or just cite wiki for proper AC's
oh, already applied
nikki doesn't see how identification of poorly named files and matching acoustids correctly are incompatible
reosarevok joined the channel
nikki: didnt mean they were. did i phrase that oddly? just thought that acoustid/bad filename matching was the _only_ reason acoustid's are really of interest
noobie joined the channel
nikki
it sounded like you think it doesn't matter if the times don't match, when I think times matter, because if the times are different, the match isn't that good
but I have no idea about freso's case, since I don't know the track
function1
i guess i cant comment on the quality of the match
i would vote no, but if there is a match that makes positive id, then it doesnt matter i suppose
function1: for what it's worth, if the only problem with that edit is the feats, I wouldn't vote no (re-adding the release would be a lot more work than just fixing the artist credits)
function1
yeah those open edits do just that
oh, but yeah in the future no 'no' vote
okay
ijabz_ joined the channel
adding a related work is difficult when there are already works established with the same name. especially when [traditional].
virtually impossible unless you have one of the other recordings to compare it too
jherm joined the channel
g-ram joined the channel
Freso
function1: Thank you.
function1: Re: "n't have much interest in acoustid for anything other than identification of poorly named files" - if the 2:15 fingerprint wrongly matches a 2:31 Recording, it should be fixed, or it won't be able to properly identify "poorly named files".
function1
yep
Freso
function1: I believe the algorithm have some time different limit inherent to it which does some sort of time/length something. But luks would be the one to know.
reosarevok
I think it has a max of 10s
Freso
In which case it shouldn't link 2:15 to a 2:33. :)