SABnzbd Forums

Hi all,
thanks for developing sabnzbd, its a great tool and I use it all the time.  The only thing I see it is missing (as opposed to 'other' newsreaders) is the ability to pause the queue for a set amount of time.  It would be great to have a drop down list or something allowing the selection to pause the queue for 15min, 30min, 60min...  That would be awesome!

thanks again

I've never seen this feature elsewhere.. but I never looked far.

I'll +1 the idea though. So many times I've urgently had to stop downloading to do something important at full speed then walk away, come back hoping to find my download there and all that awaits is disappointment.

Sure I could just remember to unpause it, but it'd be a great feature.

It's on the feature list, waiting for one of the team members to find it compelling enough to implement it.

rollingeyeball wrote: I've never seen this feature elsewhere.. but I never looked far.

I'll +1 the idea though. So many times I've urgently had to stop downloading to do something important at full speed then walk away, come back hoping to find my download there and all that awaits is disappointment.

Sure I could just remember to unpause it, but it'd be a great feature.

I was mainly referring to newsleecher...  it is an awesome idea, when I quickly have to download something and forget to unpause the queue

That's an excellent idea!. Never thought of that.
It would be brilliant. My kids ask me to pause for a while so they can get some online gaming on, but never tell me when they've finished so I forget to resume. A timer would solve that problem in an instant.

I second this. A timer-based throttle function 

pair of dimes wrote: What if you just added a bunch of schedules to resume?

The problem with this is that its then requires us to remove each pair after our pauses are done and we're never quite certain when this pause is required. This timer function would be easier for even our spouses/kids to use when they need to. Setting up a schedule requires more logical thinking than what may be available and usually ends up with disrupted data flow 

How i believe this function would work is:

1) Insert time needed for pause
2) server priorities this 'schedule' over normal schedule
3) schedule is created by taking current time, creates throttle start point, adds time required for resume to current time for end point and runs. After end point is run, resumes to normal schedule.

I wouldnt mind this feature either

I like this idea too.