Retrty 2 Next Retry 1250% completed

[zoltix]

Hi,
When I download an nzb and a one rar is broken in the packet NZ doesn’t want to download automatically the par2 to repair the package. But when I make right client and force the resume on par2 files, it can repair and unrar.
Perhaps it's a bad setting in my config but I changed nothing since the last update.



Thanks you for your help

Version 6.30 Build 1832
Image link not allowed for unregistered users

https://lh5.googleusercontent.com/-jgUs ... 0titre.png

[DThor]

Unless I'm misreading that, it looks like newsbin is retrying the missing chunk download. After two retries, it will go after the pars, download and repair. There's a setting for number of retries in options. If you're sitting there watching it and can clearly see it's missing some chunks that could be repaired and you just want it now, the simplest solution is to right click on the parent of the post and select assemble incompletes. That bypasses trying to wait for chunks that might never show up in return for the higher disk/cpu path or par repair, without needing to fuss with separate components of the post. The default state for newsbin is about minimizing par repair if possible at the expense of not necessarily looking like the fastest solution if you're riding the download.

Having said that, I was gabbing with Quade on the irc channel last night about this, and he acknowledged he's aware it's not necessarily the best solution for all scenarios and is planning on revisiting this approach in a future release.

DT

[Quade]

Yeah, what he said. It was something I wanted in 6.3 but, ran out of time to implement.

[zoltix]

So, for the next realease.
Again Thanks for your response ..

[DThor]

Probably, but just to be clear, nothing's broken. If you just ignore it, it will work fine, it's not stuck. You can also set retries to 1, will halve the wait time.

DT

[Quade]

There are two forces at work here.

1 - Some people want it to just give up, assemble and attempt a repair.

2 - Some people have shitty connections and/or PC's and if you do #1 too aggressively, you end up with files that can't be repair but, if you retried a couple times, you'd have gotten enough blocks to repair it.

#1 works fine if everything is working properly. Many people though run into #2.

So, the retries lets you tailor how long newsbin will try. It's setup to retry at least once.