Par2 more options and information

[zoned]

Two options

1st to download any missing filename.vol####+##.PAR2 files where needed but not to repair the file
2nd option to allow/disallow repair when file is ### mb or gb

This would allow us to have the correct vol PAR2 files needed for repair so can repair outside altbinz with other software. As is faster to do with large files.


Information (do excuse not knowing how par2 works)

1st To give information what vol PAR2 part affect which .rar or .### file.

Example: 100 .rar parts altbinz to show each vol PAR2 that are associated to each .rar part in main window next to each file when are expanded. Selectable to show as like group, poster.


# = number

[Rdl]

I could introduce option to repair files under certain filesize. That covers both requested options. However I'm not sure that anything can repair faster then the included multicore par2.exe

Regarding information, no par2 files don't work that way. One block or file is not associated with just one rar.

[zoned]

I could introduce option to repair files under certain filesize. That covers both requested options. However I'm not sure that anything can repair faster then the included multicore par2.exe

Having that allows us to input a file size threshold for this will be a great help thanks.

Regarding information, no par2 files don't work that way. One block or file is not associated with just one rar.

I put this as an information option since altbinz and par2.exe knows which are the correct ones as does add them when needed while downloading and before downloading the next file/s in the list.

For when a download is added sometimes has no vol.PAR2 files or are added later as extra, other or request etc. This info could be used to download only the vol.PAR2 files that are needed for repair with another software. Where can repair faster with only one read/write needed for read verify before write repair when has available vol.PAR2 blocks for repair. As sometimes there can be as many or more vol.PAR2 files than there are .rar files.

[Hecks]

As the request is only really justified if it's established that there are external clients that repair faster than Alt.Binz, I think you could at least explain which clients these are, with some actual evidence of faster repair speeds.

If this is proven, in the long run it would be better to focus the effort on improving repair speeds within Alt.Binz, in my opinion.

[zoned]

As the request is only really justified if it's established that there are external clients that repair faster than Alt.Binz, I think you could at least explain which clients these are, with some actual evidence of faster repair speeds.

QuickPar

I did write once what it was on the forum that took its time, will have a look later what I wrote. I think it was altbinz will read or verify of all files more than quickpar does for the same repair task, making quickpar faster. Maybe if altbinz did read/write as quickpar does, then both could repair at the same speed !

[Hecks]

QuickPar is not faster than Alt.Binz in my experience, but if there's a reproducible example to benchmark then by all means post it so Alt.Binz can be improved when handling those use cases. Otherwise this request is somewhat meaningless, IMHO.

[zoned]

Is this what you mean by test ? you didn't explain ! Though if it was needed i'm sure RDL would have asked, no worries here is a smaller gb file I just repaired. Until altbinz matches we will have an option setting for a threshold threshold value ### mb gb input to use.

Code: [Select]

Disc One  [4.084 mb]

AltBinz QuickPar Time Difference
Check Files Before Repair 4:40 3:48 0:52
File Repair Process 6:50 6:30 0:20


Disc Two  [4.183 mb]

AltBinz QuickPar Time Difference
Check Files Before Repair 5:01 3:53 1:08
File Repair Process 5:16 4:55 0:21


1 download nzb containing two disks

Disk one - needed x5 .rar parts to be repaired (each had 32/33 blocks) / x2 repair vol.par2 (altbinz had auto downloaded) (1.53mb and 6.08mb)
Disk two - needed x3 .rar parts to be repaired (each had 32/33 blocks) / x2 repair vol.par2 (altbinz had auto downloaded) (1.54mb and 3.08mb)

1 core cpu 1ghz / 1gb mem / win xp sp3 x32 / 7200 rpm hdd (pata 133)

more than 1 core cpu and HT variants used for other tasks such as video compression and more. Someday they will be used for internet and altbinz (unknown when)
When altbinz repair when is the same speed or faster than quickpar then allow altbinz to repair all files.

Quickpar can also repair some files when altbinz doesn't repair them or know they need to be repaired. On those occasions altbinz hasn't downloaded any vol.par2 files (as sees all ok green) then I will manually download all the vol.par2 files which some can be many and large. Could choose which if altbinz was able show which vol.par2 files would be needed, which I mentioned above first post 'Information'. But then on reflection if it knew which would also know needed to be repaired and so download the vol.par2 files. This said as 'Information' in the first post becomes irrelevant until such time it would be needed. Although would be still nice information to have if it was possible to show.

[Hecks]

I said *a reproducible example*, just posting a spreadsheet of numbers is useless.

[zoned]

You didn't say so I tried to guess seems wasn't enough for you never mind no loss. RDL has said there will be a threshold setting. So for those of us that have this problem we use the threshold setting. For those that don't have this problem let altbinz+par2.exe do it. An easy fix worry not problem gone.

[Hecks]

"Could introduce" does not mean "will introduce". There are plenty of other open requests that would be more useful to users than this one, let the development effort focus on those.

[zoned]

RDL develops and owns the altbinz code, I don't see any other name in the about tab !

So your computer can repair as the same speed that other softwares such as quickpar can repair. Other people may not have and I am one of those that find that quickpar is faster more the larger the archive gets.

I guess if you really did care for this you would have another computer likely older and test away until it does match your criteria. Then could post RDL of your findings to fix this, for many of us we don't have the time to do so. So until such time as someone does do this it is easier to have a fix that would help those that don't have a computer like yours to fix. Using another software for files over a certain size, size they instead input a value in the settings threshold. Simple and yet does give more time for other open requests than would be doing it your way