Page 1 of 1

Version 6.31 Release Candidate 4 Available...

PostPosted: Fri Mar 23, 2012 11:46 pm
by dexter
Quade found a bug in AutoPAR processing where PAR chunks weren't getting counted right so there were cases where Newsbin might not process a downloaded RAR set when it should.

Also, there are now two new hidden options for AutoPAR processing. "Aggressive Mode" starts the repair and unrar process within 10 seconds of the last chunk downloading if there are enough par blocks. The other option allows you to have PAR files download all the time instead of remaining paused and only downloaded if needed. For clean installs, Aggresive Mode will be on and PARS will not be paused. Upgrades retain current settings. Details for changing the states of the options are in the text release notes delivered with Newsbin.

The download link is on the Newsbin Beta Page.

Re: Version 6.31 Release Candidate 4 Available...

PostPosted: Sat Mar 24, 2012 2:45 am
by ozzie
Just DL the new RC and installed, I saw the mention of "Aggressive Mode" and open the NBI file in Notepad to check the settings, and found it wasn't there, so I added the line AggressiveAssembly=1

Will this work, by my adding it this way?

Re: Version 6.31 Release Candidate 4 Available...

PostPosted: Sat Mar 24, 2012 2:51 am
by Quade
You need to exit Newsbin and then save the NBI. Then restart Newsbin.

[01:50:23] HIGH - Aggressive Assembly mode: Enabled

Is what you'll see on startup if it worked.

Re: Version 6.31 Release Candidate 4 Available...

PostPosted: Sat Mar 24, 2012 3:21 am
by ozzie
The only line relating to PAR or RAR I see is...
[17:17:06] HIGH - Par2Repair - Single-core 1.0

EDIT
Just changed the line I had it on, and it now works ok... :)

Re: Version 6.31 Release Candidate 4 Available...

PostPosted: Sat Mar 24, 2012 11:44 am
by alexander038
I had a few problems too some time ago with the endless retries but today i was able to unrar a post
after two retries without downloading/using the par2's :)
Hope the pause par's and retry options won't go away in future versions.

Re: Version 6.31 Release Candidate 4 Available...

PostPosted: Sat Mar 24, 2012 12:44 pm
by Quade
No, it'll be there.

There's two kinds of people:

1 - Perfect or nearly perfect servers so, a quick assemble and repair is all they need.

2 - Not so perfect servers where a couple retries will actually pull additional chunks.

"Aggressive" mode is for #1 and regular mode is for #2 people.

Re: Version 6.31 Release Candidate 4 Available...

PostPosted: Sat Mar 24, 2012 1:46 pm
by Semel
Works nice.
Yet still nbpro is more demanding in terms of disk writes\reads performed at the same time(unraring while downloading) compared to sabnzbd (even with all those chunk\memory tweaks)

Thus i still urgently and humbly request==>

Pause Downloading During Post-Processing Pauses downloading at the start of post processing and resumes when finished.

if its not much of a trouble that is

Speed limiter is already in place. I suppose these two settings can be grouped together

Re: Version 6.31 Release Candidate 4 Available...

PostPosted: Sat Mar 24, 2012 2:19 pm
by Quade
Yet still nbpro is more demanding in terms of disk writes\reads performed at the same time(unraring while downloading) compared to sabnzbd (even with all those chunk\memory tweaks)


And my question is "so what"? Why does this matter at all?

Total disk IO, particularly for repair is lower in Newsbin than in any of my competitors. Total amount of data downloaded for a RAR set it also significantly lower. By 10-20% depending on whether you let Newsbin manage the pars or not. That's because they download all the pars and Newsbin just downloads the pars it needs (or none if the files are perfect). If you use "MemCacheLimit" to cache the entire file in memory before writing it out, autopar disk IO is ZERO for scanning the files for valid data. It's just scanning RAM before the file is written out.

You once complained that Newsbin downloads slowed down when unraring. I fixed that. Now you're complaining that Newsbin downloads don't slow down while unraring.

Is your machine unusable while this is going on? To me, that's the only justification for a change like this.

Re: Version 6.31 Release Candidate 4 Available...

PostPosted: Sat Mar 24, 2012 3:17 pm
by alexander038
Ok, thanks Quade :)

PS: most perfect imo is to download the post from my server + extern fillserver complete without even need the par2's
and any par tools at all.
I don't download that much but i haven't used any par's for weeks now cause the fill server downloads all missing parts
if needed.

Re: Version 6.31 Release Candidate 4 Available...

PostPosted: Sun Mar 25, 2012 8:50 am
by FriedLocust
[13:41:20] HIGH - Par2Repair - Single-core 1.0

Can I still copy the files from the MulticorePAR630.rar dex provided, or have the file files changed?
I would like to have multicore support on my amd system. :mrgreen:

Is there a way to help you guys testing, because I read nobody of you has amd systems?

Re: Version 6.31 Release Candidate 4 Available...

PostPosted: Sun Mar 25, 2012 9:18 am
by Quade
You ought to be able to copy the dll over. This issue is that multi-core doesn't work for some AMD but, seems to for others.

Re: Version 6.31 Release Candidate 4 Available...

PostPosted: Sun Mar 25, 2012 10:31 am
by FriedLocust
Ok, I will copy the files then.

I have a phenom x4 955 maybe those are not recognised?

Re: Version 6.31 Release Candidate 4 Available...

PostPosted: Mon Mar 26, 2012 12:23 am
by chiphead
nice job Q

Re: Version 6.31 Release Candidate 4 Available...

PostPosted: Wed Mar 28, 2012 3:50 am
by mimauk
Ver6.31 B4

Had a strange one this morning when I booted my PC up and started NB.

Every time I tried to update my Groups - 55 groups with headers from both Easynews Europe and US servers - NB would crash.

The Windows Error details said the event name was BEX - whatever that is. This happened about 4 or 5 times.

The way I got around it was to ''Show all posts'' with ''None'' in the Display Settings and then delete everything in the group for all 55 groups.

When I restarted NB and updated all the groups everything worked fine again.

Data Base corrupt ????