Page 1 of 1

better handling of post processing jobs

Posted: April 27th, 2011, 2:42 am
by n2k
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.

Greets,
n2k

Re: better handling of post processing jobs

Posted: April 27th, 2011, 3:29 am
by shypike
It looks like you forgot to delete the par2 files belonging to the pilot.
If there was a single par2 set for the whole season, then it won't be possible to
convince par2 not to reject the set.

Improvements in post processing are planned for later releases,
we don't consider them to be the biggest issue currently.

Re: better handling of post processing jobs

Posted: April 27th, 2011, 3:52 am
by n2k
To my knowledge I did remove all par2 files for the pilot (I'll try again), and no there's not a par2 for the whole season, each episode has its own par2.
I'm waiting for the improvements in the next versions :)

Thanks for the reply.

--Edit:
When retrying from the history I removed all par2's for the pilot, but it probably doesn't work because it was downloaded the first time :)

Re: better handling of post processing jobs

Posted: April 27th, 2011, 4:33 am
by shypike
n2k wrote: When retrying from the history I removed all par2's for the pilot, but it probably doesn't work because it was downloaded the first time :)
Did you remove the par2 files from the "incomplete" folder or in the details screen of the UI?
In the latter case you will not see files that are already downloaded
and the smallest par2 of the pilot will still be there.

There's a request in our system for automatic split of multi-sets (at NZB load time).

Re: better handling of post processing jobs

Posted: April 27th, 2011, 2:28 pm
by n2k
shypike wrote: Did you remove the par2 files from the "incomplete" folder or in the details screen of the UI?
Yep, I deleted it from the details screen of the UI, the small par2 shows up when doing like this:
Download everything, while the pilot rars are deleted.
Shows up as failed in the history.
Global pause sab -> click retry from the history job -> click the job in the queue (enter details screen) -> delete everything from pilot (rars, par2, yes the small par2 file is there as well).
When this re-download is complete it says failed again :p
(but I didn't do this the very first time when importing the nzb, so thats why its probably still checking it / reporting it as failed, even after retrying)
shypike wrote: There's a request in our system for automatic split of multi-sets (at NZB load time).
With 'a request in our system' you're probably referring to an upcoming/planned feature in like a bug/feature tracking system?
If so, great! can't wait for it ;D

Re: better handling of post processing jobs

Posted: October 9th, 2012, 3:29 pm
by n2k
I was wondering if this is coming any time soon? :)

Re: better handling of post processing jobs

Posted: October 10th, 2012, 5:08 am
by shypike
This is the roadmap: http://wiki.sabnzbd.org/roadmap
Keep in mind that this a volunteer's project, with currently very few volunteers.
Timing promises are the hardest.

Re: better handling of post processing jobs

Posted: October 10th, 2012, 8:53 am
by n2k
shypike wrote:This is the roadmap: http://wiki.sabnzbd.org/roadmap
Keep in mind that this a volunteer's project, with currently very few volunteers.
Timing promises are the hardest.
I see thanks for roadmap link.
And I suppose you're talking about the AutoSplit feature, I was wondering if this is requires the Sort function to be enabled?

Re: better handling of post processing jobs

Posted: October 10th, 2012, 9:29 am
by shypike
n2k wrote:
shypike wrote: And I suppose you're talking about the AutoSplit feature, I was wondering if this is requires the Sort function to be enabled?
Yes, autosplit. No, the idea is not that the two must be coupled.
It hasn't been worked out completely yet.

Re: better handling of post processing jobs

Posted: October 10th, 2012, 10:43 am
by n2k
Thanks for clarification!
This is the last major feature I'm waiting for in SABnzbd, as I have been using it for 2+ years with much pleasure :)

Re: better handling of post processing jobs

Posted: March 14th, 2013, 4:01 am
by nataliemann
This guy is so nice he is willing to suggest better ways on this problem. Let's appreciate that.miss delaware sex tape