Parchive support and more

[blun7]

Wouldn't it be neat if parchives were supported?

Also I have an idea for moving finished downloads...

Currently you can unrar to a different folder which is nice since this can be on another drive and really speed the process up. It would be a neat feature if alt.binz could also move any files remaining after the collection finishes downloading and the rars have been extracted and deleted. The current move to unrar folder doesn't work so well in that it might move an nfo needed for a second par2 set. Even if the par2 set recreates the missing nfo you're still getting two copies of the nfo in the move to folder.

[davidq666]

Wouldn't it be neat if parchives were supported?

Also I have an idea for moving finished downloads...

Currently you can unrar to a different folder which is nice since this can be on another drive and really speed the process up. It would be a neat feature if alt.binz could also move any files remaining after the collection finishes downloading and the rars have been extracted and deleted. The current move to unrar folder doesn't work so well in that it might move an nfo needed for a second par2 set. Even if the par2 set recreates the missing nfo you're still getting two copies of the nfo in the move to folder.

in unrar options you can choose to have *.nfo's and *.jpg moved to the unrar folder... that should do the job, is it not working or am i not gettin the point? also you can define other filetypes to be moved aswell...

[cr4zyfr4g]

The current move to unrar folder doesn't work so well in that it might move an nfo needed for a second par2 set.

Just create subfolders based on nzb or archive name. Then you'll have only files from your collection inside that folder

[blun7]

Maybe some examples might help illustrate my point:

Let say a collection contains these files:
movie-a.par2
movie-a.rar -> movie-a.rxx
movie.nfo
README
movie-a.par2
movie-b.rar -> movie-b.rxx
movie.nfo
README

First of all there are oddly named files all the time, move *.nfo and *.jpg will unlikely work most the time.

If move *.nfo is set:
Assume both par2 sets are checking for that nfo and README (this is stupid but happens all the time). After the first set is extracted, the nfo is moved, forcing the second par2 set to repair it. Then altbinz will fail to move the second nfo over because that file already exists.

This is a problem I can live with, but would make altbinz that much cooler.

[davidq666]

so you've got a collection of 2 movies which share one parset like a 2 cd version... and you want them in 2 folders? why not split the collection? in movie a and b with different unrar-folder... and if it does't wanna move the file coz it exists use the overwrite file option...

[blun7]

This is harder to explain than I would have thought.

In my example there's one movie split into two cds (and rar'ed up), very common. So one movie split into 2 700mb cds, and each cd has its own set of pars.

[Hecks]

This is harder to explain than I would have thought.

In my example there's one movie split into two cds (and rar'ed up), very common. So one movie split into 2 700mb cds, and each cd has its own set of pars.

But why two .nfos for one movie?  I admit that I'm confused.

[davidq666]

This is harder to explain than I would have thought.

In my example there's one movie split into two cds (and rar'ed up), very common. So one movie split into 2 700mb cds, and each cd has its own set of pars.

now i understand... u have one movie in two parts and u want both unrared parts in one folder or two? i would basicaly spilt the collection in movie-part1 and movie-part2 have each one have their own unrar folder bud the same download so u have the nfo in the dl folder and the rest in separate

[blun7]

Let's have another go here...

Note that I have alt.binz configured to put downloads into folders based on nzb names, ie: c:\downloads\Movie (2007)\

Let's imagine that alt.binz has opened "Movie (2007).nzb" that describes theses files:

movie-part1.par2
movie-part1.rar -> movie-part1.rxx
movie.nfo
README
movie-part2.par2
movie-part2.rar -> movie-part2.rxx
movie.nfo
README

movie-part1.par2 will verify these files:

movie-part1.rar -> movie-part1.rxx
movie.nfo
README

movie-part2.par2 will verify these files:

movie-part2.rar -> movie-part2.rxx
movie.nfo
README

It's stupid to have the nfo in both par2 sets, but hey, it happens.

Alt.binz will either not download the second copies of movie.nfo and README, or will create new files called movie.1.nfo and README.1, depending on your configuration. I personally set alt.binz to not download existing files. I don't want multiple copies of nfos. The movie-part1.par2 set will repair and extract first. Note that I have alt.binz configured to extract files to a separate folder (d:\downloads\<nzb file name>).

These files are now deleted: movie-part1.par2 and movie-part1.rar -> movie-part1.rxx

If I configure alt.binz to move *.nfo to the same folder that the files were unrared to, alt.binz will have to repair the nfo in the second par2 set. Now there are up to three versions of the nfo. In any case, alt.binz will go on to repair and extract the second par2 set, and delete the remaining par2s and rars.

Since the original download folder c:\downloads\Movie (2007) has at best the README left behind, alt.binz won't delete the folder c:\downloads\Movie (2007), and I have to move the README and delete the folder by hand.

I think it would be cool if alt.binz moved all files that are left behind after par2 repair and unraring of a collection. This would eliminate annoyances like described above, and would work for mp3 albums and any other weird thing I download. Of course this would take some work, since moving files takes place after unrarring, which is organized by grouping files in a par2 set. Maybe par2 sets could be grouped the same way the download queue groups collections.

Feel free to ignore this suggestion. Although it would make my life a little easier, it's no biggy.

[Mystic2010]

+1 for parchives