A change in checking behavior

[semel]

id like to propose a change in checking behavior.

atm if sabnzbd has several items in a queue then check is performed on all of them one after another. And only when all checking is done on _all_ items sabnzbd starts downloading the first one

Is it possible to make sabnzbd check n1-download n1,check n2-download n2, check n3-download n3 etc
Due to some reasons sometimes checking is really slow(not usual 12-20KB but 1-3KB) and it takes forever and sometime it becomes really inconvenient


TIA

[shypike]

SABnzbd doesn't check all jobs first.
But there is an unpleasant side-effect: after the check, the job is sent back to the queue.
Unfortunately that's at the END of the queue.
I'll see what I can do.

[semel]

But there is an unpleasant side-effect: after the check, the job is sent back to the queue.
.

i guess tthats what happened. i had like 8 items and sab did exactly this: checked n1-moved it to the end of the queue-checked n2-moved it to the end of the queue etc until every items was checked then it started downloading

cheers

[dagoob]

This isn't the behaviour I see with 0.7.3. After each file is checked it returns to the top of my queue. Would this be a result of "Automatically sort items by (average) age."? i.e. It's added to the end as you describe, but then sorted back to the top?

Personally, I was going to request a feature to prioritize checking, or at least run it in parallel with downloads. Maybe a small number of connections can continue checking even if downloading is occurring? I don't like having a long queue and then finding out hours later that I needed an alternative version of something near the end of the queue... :/

[shypike]

If you have auto-sort on, a job that is sent back to the queue will not necessarily go to the end of the queue.
0.7.4 will send the item back to its original position (unless you have auto-sort on).