search

rembo10 / headphones

Automatic music downloader for SABnzbd
GNU General Public License v3.0
3.41k stars 600 forks source link

All categories provided are unsupported error for torznab #3271

Open skupjoe opened 3 years ago

skupjoe commented 3 years ago

Since recent releases of Jackett, the default torznab host categories provided by headphones are not sufficient, and you will receive this error if your indexer doesn't support the default categories passed by headphones during a search:

Error | All categories provided are unsupported in TorrentProject2: 3010,3050
dsm1212 commented 3 years ago

Not to pile on. But we really need an overhaul here. I run lidarr just for searching and use headphones for processing. Fixing the categories to be provider specific in headphones is step one, but also should send artist and album tags to the providers that support them. I despise lidarr as it's a resource pig, but it generates really good site specific queries that get matching results lists. If you look at what comes back from headphones queries it is terrible. I don't think we need the full dynamic smarts, just a way to manually configure these things per provider.

DrakeJones commented 3 years ago

I don't work for the devs or even program, but there are tons of very talented IT pros that could move this project forward in a big way, fast. And, a lot of people would would appreciate it.

rembo10 commented 2 years ago

I was doing a little testing with jackett, and I noticed a lot of results that were not categorized as Audio/Lossless or Audio/MP3, but just as Audio, which headphones isn't searching for at the moment, so from my testing, it missed like 70% of the results.

I'm not sure the best way to handle this - are you guys noticing that too though? A direct search in Jackett vs a search done in headphones?

dsm1212 commented 2 years ago

That’s part of the problem, but some servers have custom ids and some even support artist and album tag searching. If you install lidarr and do a search it gets shockingly good results back. If I look at what headphones comes back using the same servers it’s really horrible. I’m still using lidarr for searching and headphones for processing. Headphones processing is superb.

rembo10 commented 2 years ago

I think it's something that can easily be improved.... Let me have a think about how to do it. In lidarr do you have to specify the category ids for each indexer? Or is it doing it automatically? We can send a caps query before doing the search and try to parse things that way, and check if it supports the artist & album params

dsm1212 commented 2 years ago

The provider setup ui in lidarr will get the category list for that provider into a drop down. Then you multi select the categories and they get saved with the config. It detects automatically if the provider supports album/artist and sends it if they do.

rembo10 commented 2 years ago

Gotcha. Headphones chooses categories based on what kind of quality you're searching for (lossless/lossy/both), but it uses just the standard category ids, and not any site-specific ones. So i'll have to think about how to do that I guess it can check the caps when adding a new provider

dsm1212 commented 2 years ago

If you send t=caps as the command the torznab responds with a list of the caps on that provider. If that is sent to a pick list I think it is fine for the user to manually choose the entries. Even a checkbox for "supports album/artist" if it is hard to detect would be fine with me. Maybe the test button sends and if it fails the user manually unchecks it?