SABnzbd Forums

Hello,

I have been using SABnzbd for a while now, first on a windows machine and now on an Ubuntu headless machine that I made for downloads.

On both machines there is a single error that is common to both; failure to handle misnamed articles. If the article downloads rar files named XYZ.rar but the .par files are expecting ASD.rar, the verification will expect too many blocks and thus fail, even after having downloaded all the .par files associated with that article.

What I do currently is having a share from the download folder accessible on my windows PC and use QuickPar (a windows par verification tool) that recognizes the misnamed article and renames it. It can do that without the presence of any actual blocks available, so the downloading of blocks is not needed.

On checking the man par2 entry I found that par2 can also do that as long as you give it a command that takes an asterisk in the place of a filename to check. Renaming files is not part of the par2 automatic checks.

Having checked the newsunpack.py source file I have seen that SABnzbd uses the actual filename that is downloaded to check and repair. This does not handle misnamed articles, as the man par2 entry shows.

Is there a way that a function be entered in SABnzbd that can handle misnamed articles?

Thank you.

It's on the todo loist for a furture release.
Just adding more par2 files to verifies/repairs has side-effects,
so it's not a trivial exercise.

as I saw in the source code, there are many many things you do to verify, check, manage and download parity blocks. Would the replacement of the filename with an asterisk not be a valid way? I dont understand, of course, all the little dependancies and nuiances f your code, but from reading the par2 documentaion it seems that by replacing filename with an asterisk simply applies a par2 check to everything relevant in the directory, which should not have anything else other than the archive and the par2 files. If I'm wrong, apologies.

It takes more time if you offer more par2 files,
so verifying multi-set downloads will become slower for everyone.
Also SABnzbd tries to find out which par2 files are actually used and those are replaced afterwards.
I've seen par2 do crazy things with finding matching repair blocks in unrelated par2 files.
Past experience has taught me to be very careful with such changes.