Parity repair of renamed/obfuscated posts

[pigstramus]

This is a PEBCAK issue, but I was wondering if anyone knew the answer anyway.

From time to time I'll be daft and assume the post is more or less 100% complete, and leave QuickPar to automagically repair the set. In the case of these obfuscated posts, like R287402S9NP3R5299397SS99N2S316N6, the source file extension rarely line up in any meaningful way with the obfuscated file extension. For example, R287402S9NP3R5299397SS99N2S316N6.19 isn't This.Mite.Be.Cool.r19, and R287402S9NP3R5299397SS99N2S316N6.r20 isn't This.Mite.Be.Cool.r+1 from r20, if that makes any sense.

So when there's a post that's missing a file or two, maybe due to propagation issues or whatever, and automatic repair simply renames the set to the source file names, I don't know which files I'm missing. You would think I could just review the logs and get whatever is missing, but Newsleecher has previously tagged everything as downloaded when I've found that it has actually skipped some files.

Does anyone know if it's possible to "reverse" the par2 so I'll get a list of which source file is paired with which posted file?

[wintressdude]

Never encountered this - always figured after the download that in addition to the rename, the par util would include the integrity checking for all parts. Have never seen the renamed pack ever have missing source files.

[pigstramus]

Yeah, it's my fault for assuming stuff. Checking AutoRepair allows QuickPar to rename the files when they are finished being written to disk, regardless of how many files of the set are currently available. Got it fixed by using the entire set of par files, and I'll obviously avoid AutoRepair in the future.

Still curious about if it's possible.