You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the 'Edit Search Term' feature, it's my understanding that this customizes the query that Headphones uses to the configured engines. As far as I can tell, this is not being honored.
What's odd is that it did work once, on one album; but not on another.
In this case, the album is titled "Solarstone Presents Pure Trance", which doesn't exist on what.cd in that format (it's simply titled "Pure Trance").. the MusticBrainz title ends up matching the third release of that series.
Editing the Search Terms for "Pure Trance" should then reflect that custom search string in the logs, but it has reverted back to the MusicBrainz listing when testing it with 'Choose Specific Download'. I even put gibberish in there, and it still tries to connect me to the other album, confirming that it erroneously doesn't seem to be used.
Looking at searcher.py, I can see that only rutracker honors the Search Term setting (at least, specifically as 'usersearchterm'). How can we get the what.cd integration to do this?
When using the 'Edit Search Term' feature, it's my understanding that this customizes the query that Headphones uses to the configured engines. As far as I can tell, this is not being honored.
What's odd is that it did work once, on one album; but not on another.
In this case, the album is titled "Solarstone Presents Pure Trance", which doesn't exist on what.cd in that format (it's simply titled "Pure Trance").. the MusticBrainz title ends up matching the third release of that series.
Editing the Search Terms for "Pure Trance" should then reflect that custom search string in the logs, but it has reverted back to the MusicBrainz listing when testing it with 'Choose Specific Download'. I even put gibberish in there, and it still tries to connect me to the other album, confirming that it erroneously doesn't seem to be used.
Looking at searcher.py, I can see that only rutracker honors the Search Term setting (at least, specifically as 'usersearchterm'). How can we get the what.cd integration to do this?
Using 84a6c19
The text was updated successfully, but these errors were encountered: