kJams by Slithy Toves Media

okay, you're asking about CASE INSENSITIVE search. NOT cyrillic, and NOT fuzzy search.
and yes i got that working too

okay so i can confirm that it is working to search for cyrillic->cyrillic (not the same as fuzzy search, but at least it works?)

oh, so you're not talking about cyrillic, you're talking about fuzzy search, so that "м" maps to "m", right?
that's a different story.
and it's not "files" either, which threw me off, it's "meta data", that includes song name, artist, album, etc.
thanks for clarifying!
i'll look more into this and ...

oh my gosh! okay, right:
eng, french, german, japanese, italian, spanish, chinese. i think that's it.
note that if you'd like a Russian translation of kJams, there are strings files that could just be easily translated.
probably an AI could do it in a few seconds?

got a dev working on THAT EXACT ISSUE!

likely fix within a month!

-dave

okay so you WERE saying that you WERE crashing on 32bit, not 64bit, right?
if you're on mac, you can just copy the text of the crash report, and send it in an email
if you're on windows, there's currently no method

are you crashing more on 64bit?
can you send crash reports?
are you on mac?

trello is best.

thanks. noted.

hmm. if you can reliably reproduce it let me know. in general, i can only really act on a bug that i can see for myself.

i think if you're using producer you're one of the 5% that gets lost in the cracks?
CDG pretty reliably never changes. UNLESS you're using producer. hmmm. well we can DETECT producer files, because kJams, you know, PRODUCES them, so ... yeah. we could reliably SKIP hashing.

okay so, maybe we take ...

note that MP3 DOES change the file data when you edit meta data, but luckily it does that at the end of the file.
so i do think that reading just the first 1k of a file is sufficient?
note this is using classic code determinism.

a better approach would be something you hinted at: audio fingerprint ...

oh! i just re-read my reply above.

i said "use bytes in files", and what I meant by that at the time was use the number of Bytes. Like if there are 2,157,329 BYTES in a file, use that number as input for the hash.

But then when I re-read it, I thought "oh that could be ambiguous, it could also ...

what would you use for the hash input?
can't use the path, or the song name/album/artist....
possibly could use bytes in files, but that's not guaranteed to be unique. some songs are zipped, some are not, eg: mp4, and byte size isn't a reliable marker for uniqueness.
don't get me wrong this is a ...