[nzbget] NZBget 0.7.0 download and discussion

[hugbug]

The latest version of nzbget - 0.7.0-testing-r357 - is available for testing as CSI-package:
- for A100 (and compatible devices): nzbget-0.7.0-testing-r357-bin-a100-csi.zip;
- for C200: nzbget-0.7.0-testing-r357-bin-c200-csi.zip.

The package for C200 was already tested and I think it's already in CSI-repository.
I have not tested the package for A100 because I don't have a working A100 setup at the moment. If somebody could test the package, please report how it works. I'd like it to be tested at least once before putting it into CSI-repository.

To install: download the file using web-browser, then use the function "install from local file" in CSI.

EDIT: already found one misconfiguration in A100 package: the option "UnrarCmd" of post-processing script is set to "/nmt/apps/bin/unrar". That's not a correct path on A100. Please change the option after installation. A proper path would be probably "/mnt/syb8634/bin" but I'm not sure.

[coendeurloo]

Does the new version still have those awesome warnings?

[Ger Teunis]

(10-13-2009 12:16 PM)coendeurloo Wrote:  Does the new version still have those awesome warnings?

You can reconfigure them yourself via the config of NZBget itself, even with the current version.
People tend to complain just because they can

[coendeurloo]

Can i configure the text too, so instead of 'warning' it says 'no warning at all' and make the color something more appropriate, like green? (see this for some more explanation on the color choice)

The dictionary-description for the word 'warning' is: "Warning statements are a description of a potentially hazardous situation."

[Ger Teunis]

(10-13-2009 01:55 PM)coendeurloo Wrote:  

Can i configure the text too, so instead of 'warning' it says 'no warning at all' and make the color something more appropriate, like green? (see this for some more explanation on the color choice)

And the dictionary-description for the word 'warning': Warning statements are a description of a potentially hazardous situation.

I agree that NZBget should only display errors and critical issues AND postprocessing progress (although it is informational).

In my opinion users aren't interested in individual files or articles, just the whole download itself (progress), errors and postprocessing. But that's my two cents. I tried to configure such a thing with the only side effect that the postprocessing was marked as warnings (yeah yeah, they aren't)

Still hoping some web developer will stand up and help us on a newer web ui, which hugbug is open for. If anyone here has some spare time and php knowledge: your help will be greatly appreciated. You will get all the support you need from at least me and I suspect hugbug as well.

[coendeurloo]

WARNING: I understand

[hugbug]

Quote:Can i configure the text too, so instead of 'warning' it says 'no warning at all' and make the color something more appropriate, like green?

Yes, you can. Set the option "ProcessLogKind" to "info" instead of "warning" (under NZBGET-SERVER -> LOGGING).

The default configuration of the latest package uses "info" by default. I don't know what happens when you update an installed CSI-package with a new one.

Quote:In my opinion users aren't interested in individual files or articles, just the whole download itself (progress), errors and postprocessing. But that's my two cents.

If I understand correctly the idea behind suppressing of info-messages for individual files was to be able to see the log-messages describing the status of collections (NZBs). Those messages were quickly pushed away by (unnecessary) info-messages otherwise.

For that purpose we have the new history-feature now.

However I've made an option in web-interface, which allows to filter any messages based on substrings, e.g.:

Code:

$MessageFilter='successfully downloaded';

This feature was not included in the latest version of web-interface. I'm still considering if I should do this, because it has some side effects, like a possible performance impact due to checking of all (1000 or so) log-messages on every status update in web-interface.

---

Already found one misconfiguration in A100 package: the option "UnrarCmd" of post-processing script is set to "/nmt/apps/bin/unrar". That's not a correct path on A100. Please change the option after installation. A proper path would be probably "/mnt/syb8634/bin" but I'm not sure.

[lappe]

NZBget have all of a sudden startet to download everything twice!

First it downloads and unpacks fine, but then it starts downloading a file by almost the same name (e.g. I started to DL xyxyx.MKV and it afterwards it starts to DL xyxyx.AVI)

What has happened?

[hugbug]

(10-14-2009 06:04 PM)lappe Wrote:  NZBget have all of a sudden startet to download everything twice!

First it downloads and unpacks fine, but then it starts downloading a file by almost the same name (e.g. I started to DL xyxyx.MKV and it afterwards it starts to DL xyxyx.AVI)

What has happened?

See [nzbget] Downloads movie twice after update

[GaryD]

Is anyone else having problems with the scheduler not pausing?

[Soulmoo]

Hi,

Testing the 0.7 nzbget on the c200.

And i have to use the mini.php in browser.
So in browser i put http://ip c200:9999/nzbget_web/mini.php
Is that the only gui screen at the moment on the c200 to see the mini one?

Also i cant use the browse tab to search for nzb files.The browse tab is greyed out?
So i put the nzb files manually in the apps/nzbget/.nzbget/nzb folder is this normal for now ?

Greetz

[Soulmoo]

Hi,

Ok found it

So http://ip c200:9999/nzbget_web/index.php is main screen.
But on the nmt c200 the index.php still gives me xmlhttp not supported.
Mini.php works

So the browse tab works from on the pc using http://ip c200:9999/nzbget_web/index.php with pc webbrowser.
There the browse tab isnt greyed out.

Well after reading and testing found so more of my stupid questions then.

If youre new to this kind of stuff it aint that easy.

The more i discover the more i like the c200 hihih

greetz

[moddigi]

I was wondering last night whether to upgrade to the C-200. I'm guessing as the processor is faster, then the decoding/extracting etc will be faster than the A110 too?

[moddigi]

Just another quick thing. I have FeedTime and it's set to download a certain TV series. Earlier today, it downloaded these two NZB's :

Quote:Wed, 21 Oct, 17:21 TEST [NZBMatrix] complete

TEST exampletitle.s07e05.720p.hdtv.x264.x264

Wed, 21 Oct, 17:21 TEST [tvnzb] complete

TEST exampletitle.s07.e05.720p.hdtv.x264

They're exactly the same TV episode but the NZB filenames are slightly different. One of them doesn't have the "group release" name "x264" in the title, and the other does. No worries though, as FeedTime advises me that NZBGet will automatically detect duplicate NZB's.

However, due to the fact that the NZB filenames are slightly different, NZBGet will still download both NZB's. I can't see any way around this problem, other than NZBGet being able to check the actual .rar files inside the NZB for duplicates.

My PC NewsLeecher program does this; you open two .NZBs with totally different file names but the same content and NewsLeecher checks the contents and only adds one NZB to the queue list.

Is there any way that this kind of verification can be added in the future? Filename verification seems a pretty weak way to do things, unless it's a limitation of the small CPU on the A110?

[hugbug]

A new GUI for NZBGet is currently being developed by jdembski. Everyone interested should post suggestions in NZBGet Forum.