UnRAR folder 'add-ons' broken

[meimeiriver]

Ever since I upgraded to 6.70, build 4600, the UnRAR location 'add-ons' no longer work. Like

F:\burn\newsbin\Downloads\$(FILENAME)\

The $(FILENAME) part gets ignored (on all downloads, not just 1), and, in this case, just wind up in F:\burn\newsbin\Downloads\ instead.

[Quade]

I just tested $(FILENAME) and it worked fine for the download path. Then I added it to the UnRAR path and it worked there too.

Make sure you haven't set a "per group" UnRAR path. It'll override the main unrar path.

Newsbin finds the filename from the subject. If you're downloading something that doesn't have the filename in the subject, then the filename won't be used.

If you use NZB Files you probably want to use $(NZBFILE) instead of "$(FILENAME)"

[meimeiriver]

Thanks for your reply.

Hmm, strange it works for you. Not sure exactly where I can find this "per group" UnRAR path, so here is a small screenshot of the pertinent window:

https://onedrive.live.com/redir?resid=CC6AFE600F85B114!125&authkey=!AI7lgnrNpHr8ZVQ&v=3&ithint=photo%2cjpg

I hadn't actually changed any setting: I merely upgraded.

[Quade]

How are you downloading? Search, Headers or NZB Files?

Wonder if it's related to that.

[meimeiriver]

How are you downloading? Search, Headers or NZB Files?

Wonder if it's related to that.

Strictly using NZB's.

[Quade]

How about emailing one to ts@newsbin.com. I'll check it out.

[meimeiriver]

How about emailing one to ts@newsbin.com. I'll check it out.

Just emptied my download folder (with the .nzb's in them), LOL. Trying to find a new one.

Preliminary report: several downloads wounds up in the correct unRAR spot. I'm beginning to suspect it only happens after a repair took place. Will send you a good nzb as soon as I find one (that is short enough too, download wise).

Thanks.

[Quade]

If they were already in the download list when you upgraded it could be a change in behavior that goes away when you add new NZB's to the list.

[meimeiriver]

How about emailing one to ts@newsbin.com. I'll check it out.

Just sent you a faulting nzb. Thank you!

[mankind99uk]

Having the same problem when using any nzb, unrar doesn't use D:\Newsbin Download\$(GROUP)\$(FILENAME)\ it ignores the last part and unrar's in the $(GROUP) folder

[meimeiriver]

Having the same problem when using any nzb, unrar doesn't use D:\Newsbin Download\$(GROUP)\$(FILENAME)\ it ignores the last part and unrar's in the $(GROUP) folder

Makes one think whether it's really just $(FILENAME) which is broken?! (Under circumstances)

[Quade]

I got the NZB. Haven't had a chance to look at it yet. I have a feeling the problem is with the subject and not $(FILENAME) because one of you has some files that add filename and I had 100% filename so I'm thinking it's NZB Specific.

[meimeiriver]

I got the NZB. Haven't had a chance to look at it yet. I have a feeling the problem is with the subject and not $(FILENAME) because one of you has some files that add filename and I had 100% filename so I'm thinking it's NZB Specific.

Thanks for being on the ball with this.

[Quade]

You can see the proposed download path in the download list when the files are added. If they don't show the filename then it's probably not going to be in the path.

[jonas]

I have the same problem. Ever since updating to 6.7 $(FILENAME) gets ignored. I've changed it to $(NZBFILE) and thats working fine, its just FILENAME thats broken.

[meimeiriver]

You can see the proposed download path in the download list when the files are added. If they don't show the filename then it's probably not going to be in the path.

Just got a 'miss' again; and the name was clearly present in the download path.

[Quade]

You have an unrar path set too. The unrar path sets the final destination meaning the download path can be correct and then they get unrared to some other folder.

NZB Downloaders should probably use $(NZBFILE) though. It's more reliable than filename because filename requires Newsbin to extract the filename from the subject.

Might be interesting to try clearing the unrar folder in the options and then set the NZB Download folder to be what the unrar folder used to be. In that way it downloads and unrars to the same folder.

[meimeiriver]

Might be interesting to try clearing the unrar folder in the options and then set the NZB Download folder to be what the unrar folder used to be. In that way it downloads and unrars to the same folder.

Problem with that is, I really need a separate download path first: can't hold it all on the same drive. And you really take a *huge* performance hit on unRAR-ing when source- and destination disc are the same. I'd rather see it fixed one day.

I shall try $(NZBFILE), though. But please note that this erroneous behavior only started with 6.70, build 4600.

Thanks, as usual, for looking into it.

[Quade]

Problem with that is, I really need a separate download path first: can't hold it all on the same drive. And you really take a *huge* performance hit on unRAR-ing when source- and destination disc are the same. I'd rather see it fixed one day.

I just wanted to see if it worked. If that worked then the problem is that the unrar path is losing the filename.

There won't be any fixes till the next beta cycle starts up so, at this point I'm just trying to characterize it.

[mankind99uk]

Tried adding $(NZBFILE), that worked using NZB's only.
Went back to $(FILENAME), doesn't work, the unrar path has lost the filename.

[meimeiriver]

Tried adding $(NZBFILE), that worked using NZB's only.
Went back to $(FILENAME), doesn't work, the unrar path has lost the filename.

Using $(NZBFILE) myself now (as I only use NZB's anyway). So far so good (remember, it didn't always go wrong: only sometimes). 'Still collating.'

$(FILENAME) remains flaky. UnRAR-ed several music folders the other day, all of which went into their appropriate name folder, except for 1 single, stray .flac file, that just wound up in the main folder.