Check correctness of each downloaded file on-the-fly
Description of the SABnzbd configuration switch:
Normally, par2-based downloads are verified and (if required) repaired by the external par2 program. This takes a lot time. SABnzbd can check the correctness of downloaded files on the fly. A completely correct download does not have to be processed by par2 anymore. If there are any error in the files, the par2 program is launched anyway. Normally you would always want this option on.
Original text:
In the past i used some usenet apps in windows, and all of them seem to check (decoding, processing) each file (rar,zip) it downloads to see it it matches its CRC/integrity that saves time when all the files from the given NZB file has been downloaded. That way it will complete faster, this saves a huge amount of time specially on big files.... maybe by checking with par2 every rar as it downloads to check its integrity.. or integrating one gui to control it in LottaNZB, instead of using via HellaNZB since that one has issues, maybe using one like http://
Blueprint information
Related branches
Related bugs
Sprints
Whiteboard
Severin: It looks like this blueprint is implemented by SABnzbd's QuickCheck feature, which performs integrity checks of downloaded files on-the-fly and thus - if possible - avoids the costly PAR2 check/repair after the download of a whole NZB has been completed. This feature is enabled by default when LottaNZB sets up SABnzbd's configuration file. However, SABnzbd itself doesn't enable it by default and LottaNZB doesn't allow the user to change this option through the UI. So, the question how to handle existing SABnzbd users who might not have known about the existence of the QuickCheck feature.
Severin: I was wrong about QuickCheck not being enabled by default in SABnzbd. Thus, things get a lot easier when it comes to existing SABnzbd users. We should certainly not make it possible to disable QuickCheck through the UI because that space is way too precious. What we could do is display an info bar in the main window asking the user whether QuickCheck should be enabled (which is somewhat trivial, because similar infobars have already been implemented) or we simply ignore it when a user has chosen to disable QuickCheck.
