SABnzbd Forums

I wanted to discuss a possible speed up with regard to PAR2 verify.

How about doing it immediately after assembling a file? That way, you can most likely load it straight from the disk cache, saving a lot disk trashing. Then sabnzbd can keep track of how many blocks it needs (possibly even giving up downloading if the available blocks are not enough?) and get them right at the end of the download and repair immediately instead of verify - fetch - verify again to repair?

Shypike already has this on his to-do list, it just isn't something targeted for 0.4.0.

Great, keep up the good work!

Exporting the queue into individual NZB files would be another great feature but by far not as important (mainly useful for upgrades I guess)

numbipim wrote: Great, keep up the good work!

Exporting the queue into individual NZB files would be another great feature but by far not as important (mainly useful for upgrades I guess)

They are already in your nzb backup dir why do you want that?

Think he means that while downloading that the nzb gets put in a special directory so if there is a update he doesn't lose his queue.

If you do mean that, you can backup your cache dir and if the upgrade went ok, shutdown sabnzbd+ and copy back the cache and start sabnzbd+.

They are already in your nzb backup dir why do you want that?

Well they would be, if that was active by default. I forgot to set it up. Exporting the queue would solve that issue, I guess. Or I might just wait until it is empty