Search fails to find songs

[JimGilliland]

Is there a tweak to the search algorithm that will change the way it finds songs? In my large library of music, searching often brings up long lists of songs that don't match the search term, but fails to find the ones that do match.

SubSearchCO.JPG

CO1.JPG

CO2.JPG

CO3.JPG

[JimGilliland]

No replies, so I guess there is no obvious fix. Has anyone else seen this behavior? I'm running 5.2.1, but it's been behaving this way for several versions now. I get the same result whether I use the web interface, the Android Subsonic client, or Jamstash, so it seems to be in the search engine itself. I know the engine is Lucene, but I have no idea how to tweak its settings. Does anyone? Or is it something internal to Subsonic that readily can't be accessed?

My guess is that the search parameters are just being overly inclusive, and that the matching results would eventually turn up if I could go far enough down the list. The first result listed contains the string "on" in the artist, album, and song field. The next one has it in just two of the fields. The rest all have the string "on" somewhere in the song title. These results seem to go in artist order, starting with 3 Fox Drive, then continuing through the "A"s. It's as if the search looks only for the string "on" and ignores the "Carry" part completely.

Any thoughts?

[degan6]

Not unless you know Java, Subsonic is open source so you could go find the class the controls search and change it yourself...

http://sourceforge.net/p/subsonic/code/HEAD/tree/

[JimGilliland]

Thanks for the pointer. I haven't done any Java coding in years, but it's worth a look - this shouldn't be a particularly difficult change. I'm just amazed that no one else has noticed this, but I guess my music library is larger than most.

[john_es]

You aren't the only one. I've posted a few times without any sort of reply that would go towards solving this. Just surprised that this doesn't get brought up more often.