I think I might not understand how the file download size limitations work. I have set in the nzbdrone settings that all formats are limited to 420MB for 30 minutes and 840MB for 60 minutes. Yet nzbdrone is sending 1500MB files to sabnzbd+ for download. My goal is to download any available quality as long as it fits within the size limits set. I don’t care if it is considered “HD” or “SD” since that designation seems to vary from search engine to search engine and from uploader to uploader. All I’m truly interested in is the file being no larger than the size specified. Is that what the limitations setting is suppose to be used for or do I misunderstand the purpose of the file size function?
I have screenshots if you would like to refer to them, just not sure how to upload them with the new forum format.
What Indexer are they coming from, is it just one or many?
One of two things could be happening, either the file size is wrong coming from the indexer, or there is a bug with file size checking. I don’t personally use the file size limitations, but I know a number of people do and don’t recall any major issues with it.
I have several indexers enabled, I found the entry in the log where it says that it added it to the queue but I don’t see how to tell which indexer it came from as more than one returned responses to the queries.
jasoncole2003 said:
I have several indexers enabled, I found the entry in the log where it says that it added it to the queue but I don’t see how to tell which indexer it came from as more than one returned responses to the queries.
You can see the indexer it came from on the History page.
Also if you’re using a “Spotweb” based indexer, that would be very possible due to the implementation of the encrypted nzb’s. That way the indexer thinks that the file is between 5kb and a couple of megs while the real download contains a much larger file.
If needed I can provide a screenshot showing what’s happening.
jasoncole2003 said:
I have several indexers enabled, I found the entry in the log where it says that it added it to the queue but I don’t see how to tell which indexer it came from as more than one returned responses to the queries.
You can see the indexer it came from on the History page.
It appears, as far as I can tell that all of the “oversize” downloads are coming from nzbclub.com. I checked a couple of the releases on nzbclub and they are listed twice with the same name, one entry contains the nzb with the actual media, the second entry is the nzb file alone and therefore is much smaller, under 1MB. It appears that the nzb only entry is the one nzbdrone is picking up and when it forwards it to sabnzbd+, the nzb file is retrieved and sabnzbd+ then tries to down the actual media which is over the size limit. It doesn’t appear to be an issue with encrypted files as none of the files I looked up on nzbclub were reported as encrypted. It appears to be simply an instance of downloading a nzb that contains only an nzb to the actual content.
Would it be very difficult to put a lower limit on download size to screen out these nzb only entries? I wouldn’t think that anyone would be downloading any actual shows that would be sub 1MB so if done it shouldn’t screen out any legitimate downloads. Or is there a different/better way this could be handled or is it something that the amount of work required to resolve this is prohibitive?
I just found one also from nzbs.org. Checking the entry on nzbs.org shows that there is only one entry and that entry reports, on their website at least, that it is over a GB in size. So its not just nzbclub that these oversized downloads are coming from, nzbclub just is the most prevalent.
@bartjel I doubt we would exposed the lower limit in the UI, but instead have it hard coded to a reasonably small value. More than a few MBs, but larger than a short series (or webisode).