Don't Unrar a Selected Set?

[ppan]

I am having problems with AutoPar on certain types of file-sets where the rar and par2 files broken up in several subsets.

Is it possible to somehow select those sets in the download queue and exclude them from being Auto-Unrared (but preferably still auto-downloading any necessary par2 files)?

[DThor]

Yeah, I've seen those. I've found that if I just leave it, it tends to just work, for the most part. Why would you want to exclude them, specifically, from unrar when you could just turn it off if you wish? Are you finding it's over downloading pars because you have aggressive mode enabled? Just curious, I don't see that.

DT

[Quade]

Yeah, I'm not seeing a justification for disabling unrars. At worst, you might have to unrar by hand if Newsbin can't.

[ppan]

Yeah, I've seen those. I've found that if I just leave it, it tends to just work, for the most part. Why would you want to exclude them, specifically, from unrar when you could just turn it off if you wish? Are you finding it's over downloading pars because you have aggressive mode enabled? Just curious, I don't see that.

DT

I downloading several sets at the same time, many of which Unrar works fine with. Thus, I do not want to turn off AutoPar completely.

In v4.32, for the sets with subsets, I get several copies of the same files as AutoPAR repeatedly tries to Unrar, and the whole set is not extracted anyway (only one of the subsets). Thus, I would like to exclude only those sets from being Unrared (I will do those manually, or use the AutoUnpack software).

(Note: Aggressive mode is off)

[Quade]

Sounds like the unrar is failing, it gets some more pars and it tries again. Might be worth finding out why the unrar fails.

[ppan]

Sounds like the unrar is failing, it gets some more pars and it tries again. Might be worth finding out why the unrar fails.

The duplicate files keeps happening in v6.40b1.
I think that the unrar fails because AutoPar may not process the different sub-sets in the right order. For example, the set is:
Somefile.part001.rar - Somefile.part025.rar
Somefile.part026.rar - Somefile.part050.rar
Somefile.part051.rar - Somefile.part075.rar
Somefile.part076.rar - Somefile.part100.rar

with PAR sub-sets:
Somefile_ pt1.volxxx.PAR2 (e.g. 10 different pt1 PAR files covering rars 1-25)
Somefile_ pt2.volxxx.PAR2 (e.g. 10 different pt2 PAR files covering rars 26-50)
Somefile_ pt3.volxxx.PAR2 (e.g. 10 different pt3 PAR files covering rars 51-75)
Somefile_ pt4.volxxx.PAR2 (e.g. 10 different pt4 PAR files covering rars 76-100)

For it to work properly, the repair needs to be separately for pt1, pt2, pt3 and pt4.
After any repairs are completed, it needs to be followed by unrar from Somefile.part001.rar.

[Quade]

Well there you go. That explains the problem. When a PAR set completes, it never means a complete rar set is on disk until the last PAR set finishes. Because each block of RARS is incomplete, you see it try to unrar multiple times. The unrar will fail each time and all the PARS will then be downloaded.

If you order the download list so, the first rar (.rar or part01.rar) is in the last block of RARs, it probably won't attempt to unrar multiple times. It might still download all the PARS though.

I'll note this screwy way of posting and think about how to handle it. SInce it's 4 unique par sets, it doesn't look like a single set of RARS to Newsbin.

So basically order the list so:

Somefile.part001.rar - Somefile.part025.rar

Downloads last.