![]() Since NZBGet knows exactly which files were downloaded with errors it passes that knowledge to the repair module.Īs a result the time consuming verification step is skipped and the repair module starts the repair process directly. Instead the source code of that tool (which is also written in C++ like NZBGet) is integrated into NZBGet. NZBGet doesn’t use external tool par2cmdline. For example on a slow device the verification may take an hour with repair taking 5 minutes. Typically the first step takes minutes or tens of minutes and the second step may take a few minutes or many hours depending on the damage (and CPU speed of course).įor a large download with little damage the first step (verification) may take longer than the actual repair.
0 Comments
Leave a Reply. |