When nzbs have par files they are larger, currently we're grabbing the smallest nzb in that quality, when multiple releases come out with the same, some with par2 files, others without, we're grabbing the smallest release and missing out on par2 files. I think we need to be smarter about which we grab, not the largest (weed out the overly large files), but the smallest probably isn't the most preferred.
It might be easier (code wise) to just grab the largest, since people can already determine for themselves with quality definitions what is considered an overly large file.
Like over a year ago I did propose a 'preferred' size in addition to the existing min/max.
As a user, I would like to be able to tell Sonarr "Delay downloading for 6 hours after the first episode airs, and then download the smallest release available that matches X filter".
For some things, the quality doesn't bother me, especially if I'm going to be watching it on a mobile device anyway. Since I'm on a metered internet connection I would like to avoid fetching a 2GB file for a 30 minute show that I'll end up watching on a tiny screen. However, for some shows the only thing available is a large file and I would rather spend the bandwidth to get that then have nothing at all.
At the moment, I find myself spending a lot of time manually downloading files because I have setup my download profiles to target small encodings. Sometimes (fairly often) a show won't have an encoding available at the target size, which means I have to go in and manually initiate a download.
Any update on this? its been 5yrs, lol.
Also surprised this is still not implemented, all that would be required is a switch on the function used to compare size (i.e. use CompareByReverse instead) https://github.com/Sonarr/Sonarr/blob/c75c54688883461d0e5275f349fba957d992f765/src/NzbDrone.Core/DecisionEngine/DownloadDecisionComparer.cs#L191 I am maintaining my own fork just for that option
Sounds like a PR should be opened so it can be reviewed and implemented.
We've implemented preferred size for quality settings on Radarr v3 which also would be a fairly easy pull over. It solves this as @Taloth mentions above
@Qstick looks like that was this PR https://github.com/Radarr/Radarr/pull/4190 ?
Most helpful comment
Like over a year ago I did propose a 'preferred' size in addition to the existing min/max.