So now I still have to manually extract them and remove all

Get help with all aspects of SABnzbd
Forum rules
Help us help you:
  • Are you using the latest stable version of SABnzbd? Downloads page.
  • Tell us what system you run SABnzbd on.
  • Adhere to the forum rules.
  • Do you experience problems during downloading?
    Check your connection in Status and Interface settings window.
    Use Test Server in Config > Servers.
    We will probably ask you to do a test using only basic settings.
  • Do you experience problems during repair or unpacking?
    Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Post Reply
tweets
Newbie
Newbie
Posts: 1
Joined: January 28th, 2012, 3:15 am
Location: pk

So now I still have to manually extract them and remove all

Post by tweets »

Hey I'd like to suggest another way to post process stuff.

Here's what I've experienced.
I download a pilot episode of a series which I happen to like (after watching the episode).
Then I download a nzb which has the full first season (including the pilot)
When I remove the pilot from the download job (defined by importing the nzb) it says its incomplete (duh I deleted the pilot) but it doesn't post process all the other episodes, even if they're verified :(
So now I still have to manually extract them and remove all the left-over files.
(also when retrying the failed download in this example, it rechecks EVERY episode even though they're already been checked, but this should be solved using the below method)

This is what I'd like to see:
Do not define post processing jobs by imported nzb's, define them by par2 collections (download jobs can still be defined by the imported nzb).
In my opinion there are two advantages when doing it like this:
1. It post-processes each individual episode when the others are still being downloaded
2. It post-processes each individual episode when others might fail.

I know I could just import each episode in a separate nzb and have no problem, but sometimes this isn't always available or preferred.

With 'job' I mean a row in the queue or history tables, and with 'define' I mean creating a job.
Top
User avatar
inpheaux
Administrator
Administrator
Posts: 562
Joined: January 16th, 2008, 9:14 pm

Re: So now I still have to manually extract them and remove

Post by inpheaux »

tweets wrote:I know I could just import each episode in a separate nzb and have no problem, but sometimes this isn't always available or preferred.
This is how SABnzbd is intended to be used. We feel NZBs should be as small as possible, representing one completed file. The vast majority of performance-related complaints we get regarding SABnzbd are due to people trying to load their Queues with nzb's that end up being hundreds of gigs a piece.

SABnzbd wasn't designed to handle jobs like this. While we've made our best efforts to accommodate arbitrarily sized NZBs, it's probably not a great idea to encourage them by enabling an edge-case like the one you've described.

If you keep your NZBs small then it works exactly how you want, and you get the added benefit of better performance.
Top
Post Reply

Return to “General Help”