Beck38
06-21-2013, 09:35 PM
This was posted in another thread, but I decided not to 'hijack' it and instead started a new thread:
Stop using all these 'automated' repair and de-crunch 'tools', virtually all of them 'integrated' into transfer programs have major problems. In short, d/l the thing and process MANUALLY with quickpar and winrar, and you'll find that you'll get a lot more than trying to let someone you've never met whose code you don't get to 'review' take control of your machine and leave you most times than not with.... nothing.
Don't be so paranoid.
SAB source code: https://github.com/sabnzbd/sabnzbd
It does a fine job of post-processing and is updated quickly to maintain this standard. Very few complete or partial+par downloads will fail as a consequence of automating post-processing with SAB. I can't speak about recent versions of other applications.
Manual pp may give you better insight into any problems you experience but it won't fundamentally change the result all that often, if ever.
SabNABd started out as a really excellent tool, free (of course), and extremely stable. Unequivocal thumbs up, universally.
Slowly but surely, the folks programming it started adding 'bells and whistles', trying to fill all sorts of requests fo this and that. First, adding 'automated' par and rar and then more and more other 'requests'. The program started getting 'wobbly', then more so, until it's where it is now, very unstable (running on the same machines it started out on, btw).
Where one could launch the thing and let it grind away d/l'ing for hours and hours (necessary due to the speed of my link and the huge files), but where now it barley lasts 2-3 hours at a stretch before coming to a screeching halt - not a crash per se, as the base machine and the web browser it's using (Firefox in my case) don't report any problems, but it's in a 'halt' status nonetheless
'Mission Creep' has overtaken a once lightweight, stable program. Typical effect of too many programmers trying to justify their 'work', something that is endemic with commercial software.
So, when folks report some wacky things going on with one of these Swiss-Army knifes of software, I suggest stripping out all the bells and whistles and going 'back to basics'.
Stop using all these 'automated' repair and de-crunch 'tools', virtually all of them 'integrated' into transfer programs have major problems. In short, d/l the thing and process MANUALLY with quickpar and winrar, and you'll find that you'll get a lot more than trying to let someone you've never met whose code you don't get to 'review' take control of your machine and leave you most times than not with.... nothing.
Don't be so paranoid.
SAB source code: https://github.com/sabnzbd/sabnzbd
It does a fine job of post-processing and is updated quickly to maintain this standard. Very few complete or partial+par downloads will fail as a consequence of automating post-processing with SAB. I can't speak about recent versions of other applications.
Manual pp may give you better insight into any problems you experience but it won't fundamentally change the result all that often, if ever.
SabNABd started out as a really excellent tool, free (of course), and extremely stable. Unequivocal thumbs up, universally.
Slowly but surely, the folks programming it started adding 'bells and whistles', trying to fill all sorts of requests fo this and that. First, adding 'automated' par and rar and then more and more other 'requests'. The program started getting 'wobbly', then more so, until it's where it is now, very unstable (running on the same machines it started out on, btw).
Where one could launch the thing and let it grind away d/l'ing for hours and hours (necessary due to the speed of my link and the huge files), but where now it barley lasts 2-3 hours at a stretch before coming to a screeching halt - not a crash per se, as the base machine and the web browser it's using (Firefox in my case) don't report any problems, but it's in a 'halt' status nonetheless
'Mission Creep' has overtaken a once lightweight, stable program. Typical effect of too many programmers trying to justify their 'work', something that is endemic with commercial software.
So, when folks report some wacky things going on with one of these Swiss-Army knifes of software, I suggest stripping out all the bells and whistles and going 'back to basics'.