jj666 wrote:Needed to fill from an NZB and discovered that you can't either prioritise individual files, or pause individual files, so needed to download a fair chunk from the start to get the missing files.
I don't use auto par in the app never have, it waste to much time. It's twice as fast if you unrar to different drive other than the download drive when you unrar.
Jonny wrote:I don't use auto par in the app never have, it waste to much time. It's twice as fast if you unrar to different drive other than the download drive when you unrar.
You might not have noticed, but NB can automatically unRAR to another drive. Just set another path in Options, under AutoPAR Options.
I have it set up to download to local disk, and then unRAR to my NAS.
Regards;
/jb
richy99 wrote:not sure it works over the share like that, have you tried mapping the drive and using that folder path?
Quade wrote:Nothing wrong with that path. You're probably not letting Newsbin manage the pars so, some are still downloading after the file finishes. If you don't let Newsbin manage the pars, it only deletes the ones it sees before the file is done. The rest just download.
It is working, it's unraring to the other destination which is all it said it was going to do. Kind of shrugging my shoulders about the NZB and SFV files. If it had to repair and generate them that's where they lay. They're not rars so, they have nothing to do with unraring to another folder.
If you want to say "be nice if they were deleted after repair" then that's another issue.
"Not doing what YOU want isn't the same thing as not working."
Yea but it NOT doing what I've done for SIX YEARS now with the app and now I can't , well that's hardly progress. And if you think for one second people don't delete files from que or MOVE them around then you're just delusional. I'm glad everything you grab is nice and tiddy and never needs to be tweaked or moved or couple things removed here and there. But the same applies just because you don't do it, doesn't mean tons of people don't too. I find the idea that you don't even seem to get the need to move or delete files in que. That concept is insane I tell ya.
snes150 wrote:There is a lot of raging going on in this thread. Let's just cut out all the dumbass rants and get straight to the point:
Please put back the ability to remove specific files from the download queue instead of having the program remove the entire package when a specific rar is selected.
A simple fix, thanks in advance.
richy99 wrote:id suggest reverting back to v5.59 for now until the beta cycle is further down the line as currently v6 doesnt suit your needs
neilt0 wrote:* Move a rar (within a collection) up, down, to the top or bottom
* Pause an individual rar
* Delete an individual rar
* When adding an NZB, have all the pars added, but in paused mode (even with Autopar disabled) -- I should still be able to move the pars or un-pause them etc.
richy99 wrote:you do seem to be using it differently to how it is intended to be used, v6 works differently to v5, v6 adds the pars paused so they only get downloaded if neeed, you do not have to micromanage the queue anymore by moving par2 files in and out of the download list
mho wrote:richy99 wrote:you do seem to be using it differently to how it is intended to be used, v6 works differently to v5, v6 adds the pars paused so they only get downloaded if neeed, you do not have to micromanage the queue anymore by moving par2 files in and out of the download list
It still starts with the biggest .par2 file, not the smallest, if any repair block is needed. To some people, this is an issue. If breakage is small (only 1 or 2 blocks needed), .par2 files are big (the latter ones) and bandwidth is limited, for example.
- mho
It still starts with the biggest .par2 file, not the smallest, if any repair block is needed. To some people, this is an issue. If breakage is small (only 1 or 2 blocks needed), .par2 files are big (the latter ones) and bandwidth is limited, for example.
Quade wrote:It still starts with the biggest .par2 file, not the smallest, if any repair block is needed. To some people, this is an issue. If breakage is small (only 1 or 2 blocks needed), .par2 files are big (the latter ones) and bandwidth is limited, for example.
No it doesn't. It'll default to the largest if something goes wrong but, it downloads the smallest that it thinks fits.
snes150 wrote:I have had to manually tell Newsbin to assemble incompletes before. It then starts repairing them.
Why doesn't it do that automatically?
Return to V6 Technical Support
Users browsing this forum: Google [Bot] and 2 guests