Page 1 of 2
Verifying Takes EXTREMELY Long
Posted: February 1st, 2013, 7:10 pm
by Desisuperman11
I'm not sure if this is a necessary feature in the first place.. so before we go about trying to fix this let me explain what I want SabNZBD to do
1. Download the file
2. Download PARS automatically
3. Do a PAR check and repair if necessary
4. Unrar and rename
When I do this manually with Newzbin it only take a few minutes for this entire process yet when Sabnzbd does it, it takes FOREVER. What does Verify do anyways?
Can somebody please help me with this.. it's getting really frustrating and I'm having to do it manually for my movies. Thanks you very much
Re: Verifying Takes EXTREMELY Long
Posted: February 2nd, 2013, 3:15 am
by shypike
Par2 is the program used to verify and possibly repair you downloads.
We use the same program that most of the Usenet world uses.
The speed depends on the power of you hardware and the amount of
repair that needs to be done.
Re: Verifying Takes EXTREMELY Long
Posted: February 2nd, 2013, 3:23 am
by Desisuperman11
btw i have put "-t+" beside Extra Par2 Parameters and it's done nothing
Re: Verifying Takes EXTREMELY Long
Posted: February 2nd, 2013, 3:28 am
by Desisuperman11
shypike wrote:Par2 is the program used to verify and possibly repair you downloads.
We use the same program that most of the Usenet world uses.
The speed depends on the power of you hardware and the amount of
repair that needs to be done.
I use quickpar when I do it manually. I've done the same movies manually with quickpar and honestly it's done within minutes whereas is in Sabnzbd it just seems as if it's never gonna finish. Why such a huge variance with these two methods? I'm not complaining and I apologize if i'm coming off the wrong way but this doesn't make a whole lot of sense to me.
Re: Verifying Takes EXTREMELY Long
Posted: February 2nd, 2013, 3:29 am
by shypike
-t+ is more likely to slow things down that speed them up, due to the disk thrashing it can cause.
On what kind of hardware are you running SABnzbd?
Re: Verifying Takes EXTREMELY Long
Posted: February 2nd, 2013, 3:37 am
by Desisuperman11
I removed -t+ but I only put it there after I noticed how long it was taking. Hardware; 8GB, AMD Phenom Quad Core 940 in Windows 7 x64. Honestly, I've used quickpar countless times as I've always done this manually and my hardware has never been an issue. It takes anywhere from a 2-10 minutes to repair a movie for me.
Re: Verifying Takes EXTREMELY Long
Posted: February 2nd, 2013, 4:59 am
by shypike
No idea really, we have no control over the performance of par2.
On my less capable system it runs fine.
The only option left is to disable the multi-core par2 option in Config->Special.
Another option is to run the included par2 tool from a command line.
See what it does without SABnzbd.
Re: Verifying Takes EXTREMELY Long
Posted: February 3rd, 2013, 5:44 pm
by Desisuperman11
Please explain how to run par2 tool from command line? Thank you. it took me 5 hours to verify 4-5gb movie. Doesn't make sense
Re: Verifying Takes EXTREMELY Long
Posted: February 4th, 2013, 11:16 am
by shypike
Go to the folder where the RAR and PAR2 files are.
run this:
par2 r name-of-a-par2-file.par2 *
Re: Verifying Takes EXTREMELY Long
Posted: February 4th, 2013, 9:41 pm
by justforfun
Extremely LONG time and never finishes. removed the multi-core and still have the same issue
It is for every item that I download
Is there an option to downgrade?
Re: Verifying Takes EXTREMELY Long
Posted: February 4th, 2013, 10:14 pm
by justforfun
downgraded to 7.09 and it works - it continued where 7.10 was stuck. Just re-installed on top of 7.10.
There is an issue with 7.10
Re: Verifying Takes EXTREMELY Long
Posted: February 5th, 2013, 1:21 pm
by Desisuperman11
i will have something more concrete within a few hours and i'll update. I just ran cmd line for par2 and verifying and repair was done within a few minutes. I am now redownloading the movie with +Delete option so lets see what happens
Re: Verifying Takes EXTREMELY Long
Posted: February 5th, 2013, 2:17 pm
by shypike
Desisuperman11 wrote:i will have something more concrete within a few hours and i'll update. I just ran cmd line for par2 and verifying and repair was done within a few minutes. I am now redownloading the movie with +Delete option so lets see what happens
After that, please email the NZB to
[email protected] (and the URL of this message).
Re: Verifying Takes EXTREMELY Long
Posted: February 5th, 2013, 5:42 pm
by Desisuperman11
Ok so here's I've observed so lets see if we can make sense of this.
I tested a small movie "bachelorette.2012.limited.720p.bluray.x264-amiable"
The files downloaded as so ...
130052-1.0
130052-1.1
130052-1.2
.... 130052-1.95
The two par files it downloaded as so...
130052-1.par2
130052-2.par2
Now, when I run cmd line for the movie Par2 shows the following...
Target: "bachelorette.2012.limited.720p.bluray.x264-amiable.r00" - missing.
Target: "bachelorette.2012.limited.720p.bluray.x264-amiable.r01" - missing.
Target: "bachelorette.2012.limited.720p.bluray.x264-amiable.r02" - missing.
etc...
Now I ran Quickpar and it renamed all the files and indicated "Repair not needed". That process took about 10 seconds.
I hope you can shed some light on this. This is the same movie that took me 5+ hours to verify, repair and unpack. To verify this time it took no time at all however it just said files are missing. Now i'm super confused.
Another question.. Do PAR files download automatically? I noticed with another movie that there were PAR files but they did not download. These same PAR files show up in the "scratch" list in Newsbin pro
Re: Verifying Takes EXTREMELY Long
Posted: February 5th, 2013, 5:48 pm
by shypike
I recognize the pattern.
The support for obfuscated names has an unfortunate side-effect for these kind of NZBs, mostly on slow systems.
I'm looking at a solution.
You'll see that the NZB consists of one large and one or more small sets.
As a work-around you can remove the small sets from the file list, before you start downloading the NZB content.
130052-1.par2
130052-2.par2
These two have matching files starting with 130052-1 and 130052-2 respectively.
Look for the smallest set and remove those files.