I’ve noticed recently that there seems to be an edge case that might be getting handled incorrectly when searching for a particular track in Plexamp. Specifically in cases when searching for tracks where the title is a complete match (or has a matching prefix) to the album title.
For example:
I have the following album: “Fire of Unknown Origin” by Blue Öyster Cult, which also contains a track by the same name.
- When searching for that titular track, only the album shows up unless a complete match is found. (Note how there are no track matches)
- With a complete text match the track will show up.
- I have another track from a different album called “Fire of Unknown Origin (original version)” that doesn’t show up in the above case. But if I add an additional constraint to the search string so that the “Fire of Unknown Origin” album no longer shows up, this specific track will show up as expected (even with a partial match).
Additional cases are also broken, for example:
- Directly pasting a partial search string for the “original version” track will result in no matches at all.
Even with a more strict string.
- Adding additional characters to the above case won’t trigger any matches
…until you add the trailing parenthesis (pasting this complete search string will also yield the track as expected)
- In some cases typing a stricter search string still yields the album instead of the track that we’re expecting.
- Of course adding the closing parenthesis results in correct results like before.
- Deleting the end of the string with Backspace keeps the correct results
- This remains the case until the leading parenthesis is deleted
It seems to me that parenthesis in the search string are causing some strange behavior in the searching logic. I’m not sure if the initial query is pulled from the server and then filtered client side (this would certainly explain why pasting a search string directly has it’s own set of issues) but that seems to be the case at least.
