AutoRAR extract location mess up

[oferlaor]

I am using 6.5B5.

It is set to download to a local directory, but autoRAR out to another drive (NAS drive) using the NZB and file name.

However, I see that in some cases, it does the autoRAR to a the local download drive, or to the outgoing (NAS) drive, but without the directory name.

This seems to be a new issue.

[Quade]

How are you defining the NAS path? I mean what's the path you've set? Does the NAS path include "$(NZBFILE) in it?

[oferlaor]

My unrar folder looks something like this:
Z:\finished\$(FILENAME)\$(NZBFILE)\

[DThor]

If it's only in some cases, you'll need to identify what's different between the two. Perhaps a PM to Quade with the post details of one that works and one that doesn't.

The filename variable is one of those wildcard options that can lead to unexpected results.

DT

[oferlaor]

Not really sure why.

I couldn't tell what was different. All I know is that sometimes I either got the AutoRAR directly to z:\finished (no subdir), and sometimes it decoded to c:\finished\FileName\NZBFile...

I use a variety of NZB sources - some auto downloaded, some from sickbeard and some through a shared dropbox and a monitored folder...

[DThor]

Well, as I said, if you PMed an nzb to Quade he could look at it. My guess is if you removed the filename var from the equation, things would be more reliable. Not a solution, per se, but might help identify the issue.

DT

[Quade]

Oh, so the nas if mounted as a normal drive. That's what I wanted to know.

I use a variety of NZB sources - some auto downloaded, some from sickbeard and some through a shared dropbox and a monitored folder...

Is what I'd look at since, each of those can have their own unrar path.

[oferlaor]

Dthor,

Since I also download through regex with autodownload, I can't get rid of the filename, because in that situation there is no NZB name...

Quade,

yep, it's a normal net mapped drive.

I understand each of these can have its own unrar path, but because of the situation, I can't really tell if a specific download came from one source or another (I actually don't care where it came from). I can pretty much either say it came from an NZB (sickbeard autodownloaded to a monitored NZB folder) or autodownloaded.

In either case, the unrar path should point to the same location, since I didn't modify it manually...

[DThor]

I guess you're missing my point. I'm talking about problem solving and troubleshooting. So, yes, some scenarios may not work, but it would at least potentially isolate it to the type of pathing you're doing. Otherwise, the bug report turns into "it doesn't work", which isn't terribly useful. I may be completely off base, nothing at all to do with filename, but unless you can provide an example for Quade to troubleshoot, not much can happen.

DT

[oferlaor]

I'm a developer myself, so I know how frustrating it is to receive bug reports that are vague or don't have an attached reproduction scenario...

I'll try and pin it down.

[oferlaor]

It looks like the auto downloads are auto raring to the rar output directory without sub directories.

Strangely, the software now creates subfolders on the download dir...

[oferlaor]

Is anyone seeing this problem.

It seems to be new to b5.

[Quade]

I'm not seeing it but, my setup just isn't as complicated. There's a B6 in the wings with some extensive fixes. I'm hoping the problem has solved itself.

[oferlaor]

B7 is just as bad as b6

Nzbs look ok but auto downloads and search results come out all over the place.

Auto downloads typically end up in the target directory but the auto rar ignores the pathing directories.

Search is worse - it sometimes downloads to the local (temp) directory.

[Quade]

Pretty sure the NZB think is fixed. It'll be in B8. Someone showed me exactly how to reproduce it. At that point the fix was easy.

I expect that's also your unrar issue. The pattern in the download list was very clear. Every other file had the wrong folder. That would have been a good clue too.