SABnzbd Forums

First time poster, casual user of SABnzbd for about 3 years.

Tried to download an audio file uploaded within the last couple days that is about 50 Mb.

When SABnzbd is running, it shows the file size correctly, and it takes about the right amount of time for that size download. When completed, SABnzbd shows no error or need for a retry.

The file is in the "Complete" folder, with the right name, and file extension. It is audio, and it plays. But the "complete" file is only 400 Kb, so it only plays for several seconds before stopping (foobar2000 delivers a decoding error message, which isn't useful considering the file just ends).

There is nothing in the Incomplete folder for this download.

So this does not seem to be a throttle speed issue.

But what sort of issue is it?

Try downloading it with it set to only +Repair option (or even just Download if +Repair doesn't do the trick).
This way you will get the repaired rar files and can extract them yourselves and see what is actually in there!

1) When you wrote use the "+repair" option, did you mean in the "Processing" list box in the multi-operations section?

2) If so, then yes I just tried this, and I got the same thing with the same audio file and with a new one.

3) What repaired RAR files? In my Completed folder there is just a correctly labeled 400Kb FLAC file. Is there a temp folder with an RAR in it someplace?

You can click on the little arrow on the right and select per download the post processing option. Now try to set that to Download, then sabnzbd will not do any fixes and you can see what's actually downloaded.

If it's still weird you can send the NZB to Safihre@sabnzbd.org, I can test it for you!

I got his NZB and the problem is that this post is UUencode..

Oh ... well ... cool then!

That sounds like a problem I can solve.

And ... I code ... but not in this area ... so it's a fun bit of trivia to know, and maybe use later on something else. You're taking me back to learning Unix in the ... gasp ... 80's.

FWIW: I had seen the yEnc in some of the listings, but I never had reason to figure out its significance.

We never supported multi-part uu-encoded stuff.
And we're dropping uu-encoding altogether, due to its extreme rareness.
We have a hard time finding test material.