From time to time there are some bad matches like HDTV detected as BluRay and so on. Sonarr will annoyingly keep snatching those releases and the I have to continue deleting them from nzbget. There will always be cases where either Sonarr will miss certain aspects of the download or the user will have preferences that other may not have.
I would like the ability to set up ignore keywords so when there is an unwanted release there is a simple way to ignore it and prevent future issues with the same keyword. Manual snatching is not an option for whole season as it is tedious. Ideally I would like to specify keywords and possibly other parameters like file size and set a priority.
There is a similar yet very basic feature in CouchPotato that is great for eliminating for example non-scene groups and posters.
You could mark the release as failed via Sonarr’s history to blacklist it (when something does sneak through).
You can ignore by keyword on on Indexer Settings in Sonarr (its an advanced setting), it will apply to all releases. We have a feature that will be going into develop in the near future that will allow you to restrict things on a particular tag (a tag will be applied to one or more series), so you can fine tune things more, but other parameters will not be taken into account. A white list of keywords will also be added at that time (one or more words that must be present).
You can restrict file sizes for individual qualities on the Quality Settings page.
The problem with that is you have to do that to every episode, that’s a lot of blacklisting for several seasons…
You can ignore by keyword on on Indexer Settings in Sonarr (its an advanced setting), it will apply to all releases.
Do you mean “Release Restrictions”? If so maybe the name needs to be changes as I had no idea this could be used for keywords, in fact I didn’t know what it was for at all
Good to hear about the upcoming features, sounds like it would be enough to solve this issue completely.
Did you look at the description? Its not the best description, but it should help convey what it does. Of course when you’re skimming settings and looking for a particular phrase/word (dare I say a keyword), then its not likely to jump out at you. Its moot, but changing the name could be done, but it comes down to what each person is expecting to see, which is impossible to gauge and will conflict with what people are expecting.
Prime example of naming things, is Drone Factory, its a terrible name and doesn’t describe what it does (the description attempts to), after trying 5 or 6 different names (including almost verbatim what SB used), it became apparent that people won’t read the description if they make an assumption to what a field does, they would put in a bunch of different things and go unexpected results. The name change was to hopefully get people to read the description because we can put the actual text there instead of a short name for it.
Since things are changing and this is being removed (it will be moved to the new restriction system) we’re not going to change anything, but we’ll give some more thought into how we name the new system.
“Manual Download Folder”
Tooltip: Optional folder to place manually downloaded files in. This directory will be periodically scanned by sonarr for new files to import.
Ehhh, not sure if I like it myself now that I’ve written it. Then again, it sounds like enough of a chore to scare people into using the super-mega-awesome Completed Download Handling
Sorry for the thread derailment. Carry on. I wasn’t here.
You are right the point is moot since it will be changing soon and it’s also not very useful as it is anyways. Keywords should be specific to quality(s) or quality categories to be useful as I realized when I wanted to add a keyword. As long as the new keyword feature allows quality specific keywords it’s all good.
As far as descriptions go it should be more detailed and even have a link to a full wiki page that explains exactly how it operates with examples. The reason I didn’t see the restrictions options for what it was is probably because of the type/shape of the input box. In general restriction options should have the word keyword and comma-separated somewhere to be clear at least to me.
