SABnzbd Forums

There's nothing to fix.
If SABnzbd sees matching par2 files, it will use them to verify the download.
If you don't want that, set the option Config->Switches->"Process only verified downloads" off.

There was one minor issue fixed in 0.7.19
If the download also has an SFV file and the files verify against the SFV,
the bad par2 files will be discarded. Previous versions still wanted to verify against the invalid par2 files.

shypike wrote:There's nothing to fix.

There was one minor issue fixed in 0.7.19
If the download also has an SFV file and the files verify against the SFV,
the bad par2 files will be discarded. Previous versions still wanted to verify against the invalid par2 files.

Ok sorry, i guess i was confused, i thought that behaviour with the bad par2 and correct / verified .sfv would happen even if "Process Only Verified Jobs" was on?

because it didnt work

I will just turn off Process Only Verified Jobs

thanks

IMHO this should always be the workflow,

Check downloaded file against SFV if it exists, if the SFV exists and CRC32 matches, end checks. CRC32 could be generated on the fly as the file downloads.
If no SFV file exists, test zip/rar, if successful, end checks.
If no SFV exists and file fails testing, download relevant PAR(s).
If PAR(s) are downloaded repair files.

Obfuscated files could be renamed from SFV contents if CRC32 matches. ie. Check SFV content for file name, if the file name exists in the SFV compare CRC32. If the file name doesn't exist in the SFV, compare all CRC32 contents from the SFV, if that matches there's a pretty good chance the matching CRC32 is the obfuscated file so rename it?

Worth looking at, but posters create so much variance.