Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Search Terms not being honored with what.cd #2279

Closed
Morgon opened this issue Jul 11, 2015 · 1 comment
Closed

Search Terms not being honored with what.cd #2279

Morgon opened this issue Jul 11, 2015 · 1 comment

Comments

@Morgon
Copy link

Morgon commented Jul 11, 2015

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

@rembo10
Copy link
Owner

rembo10 commented Jul 13, 2015

Ah yeah you're right. what.cd was using the artist name + album name as search parameters no matter what. fixed in develop if you want to test

@rembo10 rembo10 closed this as completed Jul 13, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants