2x download when unraring sometimes?

[Mjrweed]

Some nzb`s contain more than one equal rar files

Example:

test1.r01
test1.r02
test1.rar

and then lower down in the download tab list:

test1.r01
test1.r02
test1.rar

(I guess they put in a double set sometimes, in case some files are damaged or missing)

If you have autounrar and delete files after unrar, then altbinz will download the same files one more time and write over the test1 file. This means double bw usage.

Is there any way to get autounrar after the whole nzb set has downloaded so that this doesnt happen?

I love this feature, and i use it all the time, its just so frustrating when this happens :|

Any help will be much appreciated. Thanks!

PS: IF this has been discussed in earlier threads, i apologize, i did a search but couldnt find anything about this.

[Ascathon]

Check your setup better. Duplicate file thingy is really in there.

[Hecks]

Perhaps you've dl'ed one of a number of spam posts in recent weeks, which have been using the same headers as legit ones.  This confuses indexers like Binsearch and NZBIndex, so they appear as one collection in search results instead of two.  There's really no way around this apart from keeping a sharp eye out for collections that seem too large.

[Mjrweed]

Check your setup better. Duplicate file thingy is really in there.

Jupp, the skip duplicate files option is checked.

Perhaps you've dl'ed one of a number of spam posts in recent weeks, which have been using the same headers as legit ones.  This confuses indexers like Binsearch and NZBIndex, so they appear as one collection in search results instead of two.  There's really no way around this apart from keeping a sharp eye out for collections that seem too large.

Yeah, maybe i should just not check the option for delete files after unrar, and delete them manualy instead.

Abit annoying, but nothing i cant live with

[davidq666]

Check your setup better. Duplicate file thingy is really in there.

Jupp, the skip duplicate files option is checked.

Perhaps you've dl'ed one of a number of spam posts in recent weeks, which have been using the same headers as legit ones.  This confuses indexers like Binsearch and NZBIndex, so they appear as one collection in search results instead of two.  There's really no way around this apart from keeping a sharp eye out for collections that seem too large.

Yeah, maybe i should just not check the option for delete files after unrar, and delete them manualy instead.

Abit annoying, but nothing i cant live with

yeah that duplicate file option doesn't help in that case, because it only takes effect if something was already downloaded before the dupe gets imported... i wouldn't disable "delete after unrar" because the u would have to delete all rars manualy even if there where no dupes in the collection.

if u don't use nzbplay very often u could play try disableing "sort rars while importing" and "sort by supbject while importing". so that if the nzb has the files in the order test1.r01 test1.r02 test1.rar it doesn't get changed around.
also make sure that u've got "move par2 to the front of the queue" checked and maybe also pause during unrar and repair. if all of the "first" collection is located above the second it should unrar first and u could delete the rest manualy from queue if u notice it on time.

[Mjrweed]

if u don't use nzbplay very often u could play try disableing "sort rars while importing" and "sort by supbject while importing". so that if the nzb has the files in the order test1.r01 test1.r02 test1.rar it doesn't get changed around.
also make sure that u've got "move par2 to the front of the queue" checked and maybe also pause during unrar and repair. if all of the "first" collection is located above the second it should unrar first and u could delete the rest manualy from queue if u notice it on time.

Nope, never used nzbplay

I can try that, but i`m not always around the computer when i download stuff, so i guess deleting files manualy is my only option at the moment :|

Edit: When disabling "sort rars while importing" and "sort by supbject while importing" it only downloaded 5 duplicate rars of 23, on my last try, so that helps abit at least.

A "move rar file to bottom of que" would be a nice feature, but some sets have part01.rar so that would be a problem too i guess. "Unrar after whole nzb is downloaded" would probably be the best solution

[davidq666]

no the best solution would be an additional check for identical names (and filesizes) within the collection on import! The dupes found should then be treated the same way as the prevously downloaded files so either skipping or pausing. but i imagine that it would be quiet some work to implement that kind of dupe checking.

[Mjrweed]

I agree, that would indeed be the best solution, but probably easier to just delay the unrar until whole nzb is done.

Maybe both features could be requests for future updates of this already great program

[davidq666]

...but probably easier to just delay the unrar until whole nzb is done...

that one i don't realy get.
it would download all dupes in a collection and create an unecessary waiting period everytime there is more than one par-set in the collection

[Mjrweed]

...but probably easier to just delay the unrar until whole nzb is done...

that one i don't realy get.
it would download all dupes in a collection and create an unecessary waiting period everytime there is more than one par-set in the collection

Not if "skip file if already downloaded" is enabled?

"Move rar file to bottom of que" could also be a nice option