Not unrar'ing to the correct unrar folder

[MrbLOB9000]

It's not the way the things funcion in alt.binz. Last file that contributed to par2 set transfered unrar folder info. So you have a chance till last file downloads to change where will par2 set be unrared. And you can't change that by changing default unrar folder in setup, but by changing unrar folder for that collection in Download queue tab.

I don't think that's what he's talking about.  When it automatically unrar's a rar set it follows the "unrar to a different folder" option but if you right click on the par set and click unrar it disregards the option and puts it in the download folder instead.

nope not exactly. if a par2-set is imported via queue it comes with the unrar parameter coresponding to the collection in the queue and it will be unrared to the set unrar dir wether that's done automaticaly or manualy doesn't matter.

The Problem is that if a par-set is imported manualy it comes with no unrar dir so it will unrar to the download dir. so what would be needed would be either an optional import dialog where an unrar dir can be defined or a button/right-click-menue option to do the same...

it seems to happen for me most often when it has to fix the download with pars.  I just removed and re-added a par2 file manually to see if it will unrar by it's self or not.  If that is the default behavior that's pretty random design decision.

[MrbLOB9000]

just moved something small to the top, it downloaded and auto added the par2 file, I removed it and re-added it manually (that would basically be the only way that I had to manually add a par2 file), after it finished the download it unrar'ed it to the unrar folder like it should... so apparently manually adding par2 files isn't the problem...

edit: another one that had been downloading for a while I removed the par2 file and then readded it and it just unrar'ed just fine as well.

[MrbLOB9000]

The Problem is that if a par-set is imported manualy it comes with no unrar dir so it will unrar to the download dir. so what would be needed would be either an optional import dialog where an unrar dir can be defined or a button/right-click-menue option to do the same...

exactly, or an option to choose the unrar folder that is disabled by default and is enabled by altbinz after importing a par2 set manually. btw I'm still curious if you could add the sfv support, so altbinz can check and unrar throught the sfv file, in case there are no par files, and just say "not working" in case a file is missing or damaged?

that request already exists:

https://www.altbinz.net/forum/index.php?topic=1308.15

why is that even wanted? why is using a sfv file preferable to just downloading a par2 file? they're the same size and usually if a post has one it will have both and par2 has the repairing feature, I don't get it, am I missing something?

[MrbLOB9000]

just moved something small to the top, it downloaded and auto added the par2 file, I removed it and re-added it manually (that would basically be the only way that I had to manually add a par2 file), after it finished the download it unrar'ed it to the unrar folder like it should... so apparently manually adding par2 files isn't the problem...

edit: another one that had been downloading for a while I removed the par2 file and then readded it and it just unrar'ed just fine as well.

just had some par2's that got automatically added but still didn't unrar for some reason.

edit: another one that got automatically added just finished downloading as I was typing this post and did a par repair and then didn't unrar.

[davidq666]

just moved something small to the top, it downloaded and auto added the par2 file, I removed it and re-added it manually (that would basically be the only way that I had to manually add a par2 file), after it finished the download it unrar'ed it to the unrar folder like it should... so apparently manually adding par2 files isn't the problem...

edit: another one that had been downloading for a while I removed the par2 file and then readded it and it just unrar'ed just fine as well.

it works like this. once u manualy add something there is no dl dir associated once a file form the downloadqueue is added to that set it import the unrar dir associated from the queue. so the discribed behavior is normal try importing the par after the download has finished... this is what will ost likely happen all files get checked turn green but dont unrar the space for unrar dir is empty once u initiate unrar manualy it will be unrared to standard dl dir...

[davidq666]

The Problem is that if a par-set is imported manualy it comes with no unrar dir so it will unrar to the download dir. so what would be needed would be either an optional import dialog where an unrar dir can be defined or a button/right-click-menue option to do the same...

exactly, or an option to choose the unrar folder that is disabled by default and is enabled by altbinz after importing a par2 set manually. btw I'm still curious if you could add the sfv support, so altbinz can check and unrar throught the sfv file, in case there are no par files, and just say "not working" in case a file is missing or damaged?

that request already exists:

https://www.altbinz.net/forum/index.php?topic=1308.15

why is that even wanted? why is using a sfv file preferable to just downloading a par2 file? they're the same size and usually if a post has one it will have both and par2 has the repairing feature, I don't get it, am I missing something?

simply because there are posts have that have sfv's but no par2. right now they don't unrar automaticly with sfv support they could if non are damaged...

[MrbLOB9000]

just moved something small to the top, it downloaded and auto added the par2 file, I removed it and re-added it manually (that would basically be the only way that I had to manually add a par2 file), after it finished the download it unrar'ed it to the unrar folder like it should... so apparently manually adding par2 files isn't the problem...

edit: another one that had been downloading for a while I removed the par2 file and then readded it and it just unrar'ed just fine as well.

it works like this. once u manualy add something there is no dl dir associated once a file form the downloadqueue is added to that set it import the unrar dir associated from the queue. so the discribed behavior is normal try importing the par after the download has finished... this is what will ost likely happen all files get checked turn green but dont unrar the space for unrar dir is empty once u initiate unrar manualy it will be unrared to standard dl dir...

I understand what you're saying but that's simply not what's happening.  last night while I was sleeping 8 things finished downloading.  Of those 8 things all of the par2 loaded automatically.  5 of them unrared correctly, two didn't unrar, one had to be repaired then didn't unrar.  And it wasn't that it stopped unraring at a certain point because the ones that didn't unrar were in the middle of the list.

now, when I right click on the par2s that were automatically added but did not automatically unrar, they unrar in the download folder not in the unrar folder.

[Hecks]

Were there entries in the Unrar column of the PAR2 tab for the problem ones, or not?  Any Log messages?  Reproducible with same NZBs or not?  Reproducible in any conditions or not?  Reproducibility is the key.

[MrbLOB9000]

I can't figure out how to make it happen or make it not happen.  I'm redownloading one that didn't unrar automatically to see if it will mess up again.  What kind of error or message should I be looking for in the logs?

edit: nope, that one completed and then unrared this time...

[d4f0rc3]

You really don't get it do you? It's NOT about par2 that come from the download tab, but we are talking about par2/sfv files that were added manually (right-click in the par2-tab -> import par2). These par2 files are added without a custom unrar folder, so they unrar automatically to the download folder, and there is no way to set a custom unrar folder at the moment.

Your problem is a different one because 1. you talk about par2 files that come from active downloads and 2. that fail to repair sometimes. Completely different topic! Btw the solution is to just unpuase another small par2 volume maybe 1 or 2 blocks because sometimes altbinz fails to repair even if it has downloaded the missing blocks. No idea why that happens but adding another bunch of blocks solved the problem for me. And no I can't reproduce that, it seems to happen randomly and maybe 1 out of 20 times or so, and it is definitly altbinz's mistake because when I check manually with quickpar everything is fine although altbinz refused to repair/unrar. I'll check the log next time.

So please, why are you responding to posts that have nothing to do with your problem? You even figured out yourself that this thread has nothing to do with your problem:

I understand what you're saying but that's simply not what's happening.

[davidq666]

just moved something small to the top, it downloaded and auto added the par2 file, I removed it and re-added it manually (that would basically be the only way that I had to manually add a par2 file), after it finished the download it unrar'ed it to the unrar folder like it should... so apparently manually adding par2 files isn't the problem...

edit: another one that had been downloading for a while I removed the par2 file and then readded it and it just unrar'ed just fine as well.

it works like this. once u manualy add something there is no dl dir associated once a file form the downloadqueue is added to that set it import the unrar dir associated from the queue. so the discribed behavior is normal try importing the par after the download has finished... this is what will ost likely happen all files get checked turn green but dont unrar the space for unrar dir is empty once u initiate unrar manualy it will be unrared to standard dl dir...

I understand what you're saying but that's simply not what's happening.  last night while I was sleeping 8 things finished downloading.  Of those 8 things all of the par2 loaded automatically.  5 of them unrared correctly, two didn't unrar, one had to be repaired then didn't unrar.  And it wasn't that it stopped unraring at a certain point because the ones that didn't unrar were in the middle of the list.

now, when I right click on the par2s that were automatically added but did not automatically unrar, they unrar in the download folder not in the unrar folder.

what log entries are there about about the not unrared/not repaired collections? please remember to "anonymify" filenames when u post ur log

[MrbLOB9000]

You really don't get it do you? It's NOT about par2 that come from the download tab, but we are talking about par2/sfv files that were added manually (right-click in the par2-tab -> import par2). These par2 files are added without a custom unrar folder, so they unrar automatically to the download folder, and there is no way to set a custom unrar folder at the moment.

Your problem is a different one because 1. you talk about par2 files that come from active downloads and 2. that fail to repair sometimes. Completely different topic! Btw the solution is to just unpuase another small par2 volume maybe 1 or 2 blocks because sometimes altbinz fails to repair even if it has downloaded the missing blocks. No idea why that happens but adding another bunch of blocks solved the problem for me. And no I can't reproduce that, it seems to happen randomly and maybe 1 out of 20 times or so, and it is definitly altbinz's mistake because when I check manually with quickpar everything is fine although altbinz refused to repair/unrar. I'll check the log next time.

So please, why are you responding to posts that have nothing to do with your problem? You even figured out yourself that this thread has nothing to do with your problem:

I understand what you're saying but that's simply not what's happening.

I'm not sure what you're getting on about, because it not unrar'ing to the unrar folder seems to be related to manually unraring (by right click), and manually adding a par2 to the par tab doesn't seem to affect whether it ends up automatically unraring the files automatically or not.  It seems to randomly decide based on magic if it will unrar the files or not, and if you have to manually unrar it, it puts it in the download folder, which as I said, is an odd, reverse intuitive design decision if that's the way he wants it to work.

[Hecks]

There's certainly nothing at all normal about what you're experiencing on your machine.  I've *never* seen that behaviour here, in any version.  Certainly Alt.Binz doesn't operate "by magic".  As I said before, once it's reproducible by Rdl, he can fix it.  Until then, it's just random information, I'm afraid.

The unrar dir for imported par2s is obviously a different matter.

[davidq666]

...
I'm not sure what you're getting on about, because it not unrar'ing to the unrar folder seems to be related to manually unraring (by right click), and manually adding a par2 to the par tab doesn't seem to affect whether it ends up automatically unraring the files automatically or not.  It seems to randomly decide based on magic if it will unrar the files or not, and if you have to manually unrar it, it puts it in the download folder, which as I said, is an odd, reverse intuitive design decision if that's the way he wants it to work.

i can just repeat myself: please be exact in differntiating between collections that have fully downloaded (all set files: Par's+rar's+nfo+sfv's ect.) and those still in progress... from my experience collections where the par2-set is deleted an imported manualy after full completion will check the set but won't autounrar and manualy unrar only to the download dir... if u have strange behavoir please post the corresponding log...

[MrbLOB9000]

ok, so apparently you guys are calling manually adding par2 as adding the par2 for an nzb that is fully downloaded already.  That I don't do.

But the problem I'm having is that at random (no discernable pattern that I can find) it doesn't unrar some archives attached to a par2 file.  It should since it downloaded it and par checked it but it randomly just doesn't.  The majority of the time it unrars it but a decent amount of the time it doesn't and then I have to right click and click unrar, and in that case it puts it in the download folder not the unrar folder (which is I guess what that other guy was talking about that he didn't want).

Like I said above, I've tried re-downloading the same nzbs to see if on the second download it didn't unrar but the second time always worked like it should... I can't figure out why it's happening.