I'd love to get some good statistics on which errors ppl get and how they resolve are too stupid to deal with such an option? Really? What kind of an answer is that? It's not wise to turn a blind eye to them and just randomly try other releases. Most of these 'errors' are sonarr saying it encountered an problem that it doesn't know whether it's safe to proceed with anything. It would likely be safe to blacklist these automatically.
#SONARR POST PROCESSING 1080P#
It was originally added to prevent import loops due to a release title saying 1080p and the file being 720p. Would you want sonarr to try the other 10 releases and eventually find out it can't deal with any of those either?įile with exact same filesize already exists Making any assumption about this release or any other for that episode is questionable. If this happens then there is potentially a serious misnumbering/parsing issue. Hopefully we can come up with a solution for that particular issue.Įpisode number mismatch in filename/nzb-title Again not a bad release, and chances are that alternative downloads would end up the same.īest ppl can do is document the situation and report them to us. It's practically always a problem with the parser, either a limitation which we can't fix, or something we can improve. This is one of the cases were we absolutely wouldn't want to automatically try another release. In the off-chance that there is in fact a fake release, there are some good usenet client pp-scripts that check for fakes and deal with them there.
#SONARR POST PROCESSING RAR#
Or rar files, which is a different matter entirely. And thus likely leads to good releases being thrown away.
#SONARR POST PROCESSING MANUAL#
However, in most cases nzbs/torrents that are marked for manual processing need to be deleted anyway and (considering the intent of the software) an option for COMPLETE automation should perhaps not only be there but it should maybe also be the default.ĩ0% of the time that's some misconfiguration that would prevent any file from being imported.
I realize that users may miss out on some episodes because some nzbs/torrents can be imported correctly with manual interaction. If this option is activated, Sonarr should blacklist and replace ANY nzb/torrent that cannot be processed and imported without manual interaction and thereby become a truly automatic service. Please give us an option to dismiss and blacklist any nzb/torrent that cannot be processed automatically. It requires the user to interact with Sonarr so a new episode may not come up in Plex automatically because Sonarr is waiting endlessly instead of just trying another nzb/torrent. This is very impractical because it goes completely against the concept of true automation. Same "problem" with any other manual processing exception (everything that doesn't get importet or blacklisted automatically but needs manual interaction.ĭescribe any solutions you think might work If sonarr doesn't find importable media it puts the nzb/torrent on hold (probably to allow for extraction of archives or whatever).
0 kommentar(er)
