· Differences in search results based on the search method
Tell us about your home network
· Wifi Network
When an artist’s name is displayed in Japanese, entering the search term directly in English into the list view yields no results (e.g., entering “EARTH” produces no change on the screen).
However, if I enter “earth” into the filter, the Japanese entry “アース、ウィンド&ファイア” (Earth, Wind & Fire) appears.
Is this intended behavior?
Does this discrepancy arise because direct text searches look for the Japanese text currently displayed, whereas filter searches query the underlying data in English?
Not intended, no. Search and the filter should agree here, but they do not.
Your explanation is close but not quite it. The filter matches against the Japanese name and the original name together, which is why earth finds アース、ウィンド&ファイア there. Search holds both names as well, so it is not only looking at the text on screen. Why it returns nothing for EARTH is what we are checking.
Two tests would narrow this down for us. In search rather than the filter, please could you try:
Hi @vadim, thanks for the reply. Here are the results:
The Japanese name: アース
I couldn’t input Japanese characters at all, nor could I copy and paste them.
The full original name: Earth, Wind & Fire
I could only enter uppercase letters; I was unable to input spaces, commas (“,”), or ampersands (“&”). The screen didn’t change, either.
Incidentally, when I entered “MILESDAVIS,” it simply took me to the English entry “Michael Francis” rather than the Japanese entry “マイスル・デイビス” (Miles Davis).
It appears that the search function works for artists listed in English but not for those listed in Japanese.
For reference, here is how the macOS Music app (formerly iTunes) behaves:
1. Spaces can be entered and are recognized.
Typing “MILES” jumps to “Miles Davis.”
Typing “MILES DAVIS” jumps to “Miles Davis.”
Typing “MILESDAVIS” inexplicably jumps to “Milt Jackson.”
2. Japanese characters cannot be entered.
3. Copy & paste is not possible.
4. Entered characters are not displayed; Roon, on the other hand, displays the characters you type, which looks cool.
Thanks for laying out the search behavior so clearly.
What you are describing does sound like expected behavior on Roon’s side, but we are going to double check with the team to make sure we can clarify it properly. That comparison with the macOS Music app is helpful context, and we appreciate you taking the time to spell out the differences.
A quick update: we have passed this to R&D, and it is waiting for review. We do not have timeframes for this at the moment. R&D works through many priorities, and if anything changes we will update this thread.
