SABnzbd+ repair fails but MultiPar succeeds?

[Aftcomet]

I have SABnzbd+ set to verfiy and repair the files when it's done downloading them. I finished downloading a 50GB file that showed up in the history as failed. I deleted it and retried it multiple times. But this last time, before deleting it, I went into the incomplete folder and ran MultiPar on it and it repaired the file!

Now, I'm still a little new to Usenet after being on torrents for so long. It doesn't sound logical that one program would use all the repair blocks and the other wouldn't. It can be faster but not more accurate, right?

So this has me thinking. I also use SickBeard and I've been having a lot of episodes fail that MultiPar might have been able to repair. Is there any way to integrate it into the process?

EDIT: Make that two different nzbs now.

[shypike]

Multi-par is not the solution.
You probably have hit on posts that have a non-standard way of naming par2 files.
Currently SABnzbd doesn't support that.
Multipar (or QuickPar on Windows) seem to do better because you feed them all
par2 files regardless.
Doing that in SABnzbd would mean that almost all verifications would be slower.
But we are looking at improving this.
Can you email an example (preferably not a 50G one) NZB to bugs@sabnzbd.org?
(and add the URL of this message.)

[Aftcomet]

Thanks for the explanation. Is it okay if I send a few 50GB nzbs? I don't have any ones right now that I know have this issue for sure or should I wait until I come across a smaller one?

[shypike]

The naming convention, I can check anyway even with big ones.
It's just that I don't download 50G items without a very good reason
So feel free to send me stuff.

[Aftcomet]

Ah thanks! I've sent the email. If I can also help in any other way please let me know. I'm not in IT so I won't be able to contribute to the source code, but if you need some small tasks I'm willing to help out.