SABnzbd Forums

Don't move post-processing files to history.
Files in history are expected to be completed or failed. Not checking, repairing or unrarring.

While you're at it, it would be nice to find an abort post-processing option.

Repairing 10 GB of rar files with each a few missing blocks is currently running for 20 hours on my nas now (@ 22%). It can manage a few missing blocks, but not missing GB's. So a "don't post-process when this much is missing" would be nice too.

We won't implement three queues.
Currently we have no option to terminate a running PP job. An upgrade to Python 2.7 is needed for that. Planned.
Repair is the time-consuming part: par2 won't try it when it's not possible.
There already is an "abort if completion not possible" option on Config->Switches.
It cannot be 100% accurate, therefor any marginally complete job is checked.

Too bad.

Repairing 93%... my pc was done in 5 minutes.

Would it help you to have three queues then?
When you have the possibility to stop a running PP job (which you will in a later release)
wouldn't that be enough?
In fact, the History queue of waiting jobs is separate from the list of finished ones.

Well, it wouldn't be necessary for functionality. But having a history list intuitively implies all tasks in it are completed or have failed. I always wondered why the pp jobs were in the history list initially.

Possibly an extra state in the normal queue can be used to track post processing jobs. As downloading and checking already are two "states".
A post process abort will be nice in any possible way. Currently all tasks not downloading fall into this black hole and lose all user controls. Except "retry" when failed.

You can already delete the not-yet-running waiting items.
The UI has been like this from day one and we never had a good reason to change it