Support Forum

would it be smarter to verify each file as it comes in, i.e. something like store it in a directory by itself and verify just that file against that par2 file, and take note of how many blocks failed and then move to be with the rest of the files. Thereby avoiding a verification stage at the end. So...

installing the ppa with 0.7.10

using what's in ubuntu 12.10 which apparently is 0.7.3

the way sabnzbd calls par2 doesn't seem to always work for this. If the files are obfuscated (in my case, renamed from original to random names). Then when par2 is called on the par2 file, it doesn't find any files with the same name. So it fails. However, if its called as "par2 r <par 2 file> ...

I agree, my point was, in the case where you can split it up easily, do it. In the case where you can't, don't and just continue with standard behavior. if one can handle the average and very common case better by preprocessing, why not do that? especially as (I'm guessing, can always be wrong), isn...

you're right (I didn't see the feature request forum at the bottom). With that said, I think I proposed a solution that wouldn't require the queue being fundamentally changed, just require the nzb be preprocessed and would handle a large amount of nzbs).

sanbnzbd does a reasonable job handling nzb files with multiple parsets. However, it differs processing of the entire sets of pars until the entire nzb has been downloaded. Wouldn't it be better to try and process and the par2 right away? yes. I know one can (should? though i'm not sure I agree with...