When searching for a track with magnifier via text input, Djay only returns results if the entered words are matching 100% with the actual track name. There is no tolerance, which makes searching for tracks sometimes unnecessary cumbersome.
Examples: If you look for “Y.M.C.A.”, entering “ymca” does not deliver results unless you do not enter the dots.
If you enter “coracao”, Djay does not find “Coração” as it matches not 100% due to the accent.
If you enter “Nils van” you will not find “Niels van”:
And so on…
YOUR SUGGESTION:
Implement are more flexible search results function. A good example is the search function in Apple Music, which is way more flexible
The 2 words are very different! Why do u want them to be in the search result? I know it’s frustrating for me too when I am looking for “T.O.K” and accidentally enter “TOK”.
Solution: type the word “TOK” somewhere in the comments field of the track (in your case, if you like ymca alot, type the word “ymca” in comments on that track.
i think you do not understand. If I can’t remember if that track is by an “Niels” or by na “Nils” I do not want to think about it when I am searching during a gig. I do not know if you ever played live, but I can tell you I need the time to think about other things …. same is with Y.M.C.A or tracks like “Sign O’ the times” vs. “Sign o the times”… just uneasy searching in my opinion.
No matter how “clean” in terms of id3 tags of track look, i always make it a point to run EACH thru kid3 and take a direct look; sorting out those potentially troublesome names and adding my favorite search word in the comments field:
For example, every track with “Dat” i put “That” somewhere in comments.
For those that skipped my eyes, when i find them in djay i edit immediately. In most case they’re not that many in my library anyway
magnifier via text input, Djay only returns results if the entered words are matching 100% with the actual track name. There is no tolerance, which makes searching for tracks sometimes unnecessary cumbersome.
