Comments on: nzb 0.1.7 Released

By: Disgruntled

Disgruntled — Sat, 14 Jan 2012 01:00:05 +0000

What a piece of garbage. Don’t use this. If you accidentally click the play button instead of start, it downloads the entire video into memory and doesn’t save anything anywhere. If VLC doesn’t like it, your hooped. Have to re-download all over again.

By: BitPoet

BitPoet — Wed, 31 Jan 2007 18:14:05 +0000

I’ve also experienced those (minor though, compared to other nzb-capable grabbers) troubles with nzb, and I second xempt in his wish to have downloaded parts cached on the disk to prevent one from re-fetching articles after a hang.

I’d also be very happy if nzb was able to re-connect timed out or broken connections, both after a failure in the nntp host or after a forced dialup reconnect, because those make the program abort its download on my system (XP pc behind dsl router).

Otherwise, thanks for a nice piece of software

By: mnordstr

mnordstr — Wed, 31 Jan 2007 13:27:26 +0000

It doesn’t save downloaded parts on disk, however, after decoding the part it writes to disk and removes the stored part from memory. Usually when downloading it shouldn’t use more than a few megs for downloaded data.

If you are streaming a file it stores the decoded data in memory until the application reading the stream has read that data, which in certain cases can cause quite high memory usage.

Are you streaming or downloading, and what OS are you running?

By: Dactyl

Dactyl — Sun, 28 Jan 2007 23:14:27 +0000

I noticed that the app appears to decode everything into memory without writing temporary files to the HDD. In return, this ends up with the program using a pretty big memory footprint while it’s downloading and decoding data. Any chance for the next release you could make it cache data to the download folder? I know that the OS will page out memory to disk, but right now nzb.exe is using 720mb of RAM, and that’s affecting the speed other programs on my machine run at.

By: mnordstr

mnordstr — Mon, 08 Jan 2007 20:21:58 +0000

That error is sent from your Usenet provider, an issue on their side. nzb should however of course handle it gracefully and continue.

By: Jinx

Jinx — Tue, 02 Jan 2007 14:52:12 +0000

Every time I try and download a large amount of data, say about 4Gig, I usually get this:

Error: “503 Backend Error. No. 0×69000129″

then the program will crash out a bit later. Any ideas what could be the cause?
Using 0.1.7 version on Xubuntu 6.10 and Gentoo 2006.1.

A way to queue, pause and resume downloads would be cool, please.

By: xempt

xempt — Sun, 31 Dec 2006 18:51:12 +0000

Iâ€™ve been using this program since 0.1.6, and now i have 0.1.7 . I still seem to be having difficulties with the program crashing after hours of usage downloading. The most frustrating part is the failure of the decoder to compile the files already downloaded. This regrettably means that i have to re-download all the files all over again that were not compiled by the decoder. I also find it frustrating that all the news posts are not stored in a temp folder as they are downloaded, this would be useful if the decoder fails to initiate.

Id love to see this bug fixed, apart from that amazing program!

By: mnordstr

mnordstr — Mon, 11 Dec 2006 10:02:40 +0000

Interesting. Where do you get the .nzb files from? Do you have a sample that doesn’t work that I could try?

By: JB

JB — Sat, 09 Dec 2006 11:37:40 +0000

buggy as hell. Crashes at the slightest thing. Wont play back 99% of nzb files… no help. :(

By: mnordstr

mnordstr — Thu, 07 Dec 2006 16:07:09 +0000

Hmm, I can’t seem to reproduce the problem. Do you have an .nzb file that this happens with that I could try? Does this happen for every nzb file? This bug should have been fixed as of 0.1.5 but this might be another issue.