SABnzbd Forums

Posted: **June 4th, 2015, 4:45 am**

Not a Sab problem, but more Usenet in general.

Does anyone know how to deal with these downloads that are (for example) a whole season of a TV show, where you get lots of files named:

152043-0.2.30
152043-0.2.31
152043-0.2.32
152043-0.2.33
152043-0.3
152043-0.3.0
152043-0.3.1

Typically, when I've had downloads like this, I hand them off to QuickPar which renames them into something understandable. Then they can be unrar'd.

In the case of this particular season download, there were only 4 .par2 files for 13 episodes. So, I'm left with 9 episodes that I'm unable to rename correctly.

Is there a system to these numbers? If I can understand how they are allocated, then it wouldn't be too hard to BASH something together to rename them.

Thanks. $:-\$

Posted: **June 4th, 2015, 1:34 pm**

What I have seen in the past is that people post episodes for a season
using the same RAR names for each episode.
If indexers combine these in a single NZB, SABnzbd ends up with an NZB that contains many "duplicate" files.
Depending on the order of completion of each file, it may or may not end
up with episodes that are distinguishable from each other.

Posted: **June 4th, 2015, 2:59 pm**

I don't know if this is relevant, but in the par file you can which rar files it represents:

Code: Select all

$ strings -a -t x *02.par2 | grep -i bigrandom | head -4
   ce18 bigrandomfile.part01.rarPAR2
   de98 bigrandomfile.part02.rarPAR2
   ef18 bigrandomfile.part03.rarPAR2
   ff98 bigrandomfile.part04.rarPAR2

You can see if something is a par file at all:

Code: Select all

$ strings -a -t x *02.par2 | head -2
      0 PAR2
     2f |PAR 2.0

Search for the first rar file:

Code: Select all

$ strings -a -t x *02.par2 | grep -A1 FileDesc | head -2
   cdd8 FileDesc
   ce18 bigrandomfile.part01.rarPAR2

All files in a par2:

Code: Select all

$ strings -a -t x *02.par2 | grep -A1 FileDesc | grep PAR2
   ce18 bigrandomfile.part01.rarPAR2
   ff98 bigrandomfile.part04.rarPAR2
  12098 bigrandomfile.part06.rarPAR2
  13118 bigrandomfile.part07.rarPAR2
  17318 bigrandomfile.part11.rarPAR2
  242a8 bigrandomfile.part01.rarPAR2
  27428 bigrandomfile.part04.rarPAR2
  29528 bigrandomfile.part06.rarPAR2
  2a5a8 bigrandomfile.part07.rarPAR2
  2e7a8 bigrandomfile.part11.rarPAR2

And in rar files you can see which original file it will yield:

Code: Select all

$ strings -a -t x *01.rar | head -2
      0 Rar!
     34 stuff-to-be-uploaded\magicword-100MB.bin

So if you can give a pointer to the NZB, I can see if the above is useful for your download

Posted: **June 4th, 2015, 3:28 pm**

SABnbd already analyzes par2 files, it doesn't use the info for renaming purposes.
At least not in a way that solves the underlying problem.
The actual problem is that it's not known which files belong to which set.

There is a way around: supplying all files to the par2 runs on each set.
Unfortunately that will make verification/repair much slower for each normal multi-set too.

Posted: **June 6th, 2015, 9:48 pm**

shypike wrote:There is a way around: supplying all files to the par2 runs on each set.

Agreed.

Thanks guys.

SABnzbd Forums

downloads with insufficient par2 files used for renaming...

downloads with insufficient par2 files used for renaming...

Re: downloads with insufficient par2 files used for renaming

Re: downloads with insufficient par2 files used for renaming

Re: downloads with insufficient par2 files used for renaming

Re: downloads with insufficient par2 files used for renaming