Hi, I am also seeing very odd things with searching for tracks in plexamp. I’m just using regular search, not Sonic Adventure.
To try and work out what was going on, I created a new plex installation with a minimal library. Hopefully this rules out any issues with database corruption.
The test library initially just contained all albums for Queen (14 albums, 267 tracks). Searching for tracks seemed to generally work OK.
Example - search for the word ‘friend’ - 3 tracks are show with the > available to drill down and see all 7 tracks that match (eg. ‘You’re my best friend’).
Example 2 - search for ‘Flash’. The ‘Flash Gordon’ album is found, and the track ‘Flash’ from another album. There are a bunch of tracks on the album that should also match, but aren’t shown in the Tracks section - this may be how it’s supposed to work (I disagree, but it sort of makes sense).
Next, I added another album ‘Viva la Vida or Death and All His Friends’, by Coldplay.
Now what happens if we repeat the search for ‘friend’ …
Now I get the newly added Coldplay album, and 3 of the Queen tracks. But there is no ‘>’ indicating the existence of more tracks. This is a big problem.
My testing suggests that whenever a search matches an album (or possibly an artist), not just tracks, then the ‘Tracks’ section of the search results are unreliable.
This makes it very hard to use plexamp to search for tracks - when the ‘>’ is missing, it gives the impression that there are no more matching tracks. So I might think the track I am looking for (eg. ‘You’re my best friend’) doesn’t exist.
I hope this simple example shows the problem, and helps the devs track down what the issue is.
