by meBigGuy (Posted Thu, 26 Jun 2014 01:10:35 GMT)
Problem 1 is a bug. If the main par2 (download_name.par2) is missing, it won't even try for the rest if auto par2 is selected. You can par2 from any par2 file, not just to "top" one.
As for "assemble incomplete":
The process of selecting the failed files (from the failed list), re-adding them to the download list for the directory each is supposed to go to (which is impossible to remember), then trying to find them in the download list so I can select them again and then "assemble incomplete" is totally broken. The download list is grouped, and the files may appear across multiple groups. It's nearly impossible to find them.
And, move to top, etc work weirdly. I can't select a part and move it to top. Seems to only work on groups of parts.
(Is there a way to turn off grouping of parts in the download list?).
What I don't understand is why "assemble incomplete" is not the default. The tool should just download what is there and then see if it can be repaired. If it fails par2, then it fails par2. But you can't know if you don't try. Why put an arbitrary "90%" threshold? The idea that if there is any failure you throw out the whole part and force manual intervention seems totally broken.
The tool has become very cryptic and taken a step backwards (in some respects) since 4.32. In 4.32 I could just select the failed files, select "download incompletes" and the remaider of the files would be downloaded to the directories they were originally targeted for.
You do realize that *almost* all unrepairable downloads are repairable if you "download incomplete".
Reporting this meaningfully is make complex by the fact that the tool behavior *seems* to change from run to run. I have to select features, exit the program, delete the db3's, then restart to try to force consistent behavior.
The last run I tried seemed to do the incompletes assembly by itself, but it took a while. But auto-unrar was deselected.
Thanks for responding, everyone.
mBG
Read Main Topic
Problem 1 is a bug. If the main par2 (download_name.par2) is missing, it won't even try for the rest if auto par2 is selected. You can par2 from any par2 file, not just to "top" one.
As for "assemble incomplete":
The process of selecting the failed files (from the failed list), re-adding them to the download list for the directory each is supposed to go to (which is impossible to remember), then trying to find them in the download list so I can select them again and then "assemble incomplete" is totally broken. The download list is grouped, and the files may appear across multiple groups. It's nearly impossible to find them.
And, move to top, etc work weirdly. I can't select a part and move it to top. Seems to only work on groups of parts.
(Is there a way to turn off grouping of parts in the download list?).
What I don't understand is why "assemble incomplete" is not the default. The tool should just download what is there and then see if it can be repaired. If it fails par2, then it fails par2. But you can't know if you don't try. Why put an arbitrary "90%" threshold? The idea that if there is any failure you throw out the whole part and force manual intervention seems totally broken.
The tool has become very cryptic and taken a step backwards (in some respects) since 4.32. In 4.32 I could just select the failed files, select "download incompletes" and the remaider of the files would be downloaded to the directories they were originally targeted for.
You do realize that *almost* all unrepairable downloads are repairable if you "download incomplete".
Reporting this meaningfully is make complex by the fact that the tool behavior *seems* to change from run to run. I have to select features, exit the program, delete the db3's, then restart to try to force consistent behavior.
The last run I tried seemed to do the incompletes assembly by itself, but it took a while. But auto-unrar was deselected.
Thanks for responding, everyone.
mBG
Read Main Topic
