Page 1 of 1

Weird PAR2 checking

Posted: July 16th, 2008, 9:01 am
by bugmenot
SABnzbd assumes that if PAR2 filename is e.g. release.par2, checked files must be too release.xxx. Problem is when PAR2 file is release-OTHER.par2, and it should check files like release-subs.rar or release-sample.mkv, SABNzbd thinks that all files should be named as release-OTHER.xxx.

Re: Weird PAR2 checking

Posted: July 16th, 2008, 9:36 am
by switch
SABnzbd does not make any decisions between par2 sets and the files to check. It simply gives par2.exe a parity file and par2.exe checks the files that are described within the .par2 file.

The only grouping we do is that of rar sets.

If you are having a specific problem such as -OTHER.par2 keeps on failing please post and I will look into it. By the way, if you have "Ignore Sample Files" on in config>switches the -OTHER.par2 will likely fail.

Re: Weird PAR2 checking

Posted: September 11th, 2008, 1:30 am
by ugokanain
I am having a similar problem. Strangely enough, sab seems to process the main par file. However, it isn't assembling the files because if failed the par test (have both the Ignore Sample Files, and Post-process Only Verified Jobs switches on).

Seems that sab handles par checking for both par2 files (main and other). Any chance that if one of the par files checks alright, that it could finish processing that par2 file?

Re: Weird PAR2 checking

Posted: September 11th, 2008, 2:01 am
by shypike
The option in Config->Switches, called "safe post-processing" determines whether or not incorrect downloads will be further processed.
If you set to "off", all post processing will be done regardless of verification results.

Re: Weird PAR2 checking

Posted: September 19th, 2008, 8:32 pm
by heawater
Hi,
I notice sabnzbd check the first *.par2 file, then download more parity files if incomplete.
But how does it do that? does it download only the numbers needed or all the files availlable?

Re: Weird PAR2 checking

Posted: September 20th, 2008, 1:28 pm
by shypike
Only the required files are downloaded.
When verification fails, it downloads more par2 files and a re-check is done.
This is repeated until repair succeeds or all par2 files have been downloaded.