Why does Altbinz sometimes not unpack files that are complete?

[elephant66]

Why does Altbinz sometimes not unpack files that are complete?

Sometimes ALTbinz doesnt unpack files

nothing is set to pause (nfo par etc) except 'sample' and 'sample par'

----
sometimes it unpacks the 'sample file' if it has the 'same name' as the file and then doest unpack the file
(surely altbinz could check for this behaviour - ie sample file is tiny - main file is huge (compared to the amount of files and size)- and correct this behaviour)

----

other times the files are complete tested with quick par - but altbinz did not extract

-----

other times files need 'repairing'(quick par) with quick par and 'extracting' winrar

-----------------


Its very hit or miss

and super time consuming to extract loads of HD stuff

----

Any ideas on how to get better functionality

cheers


--

Is there a repair and extract program?

[Hecks]

I think "hit and miss" is an exaggeration.

There are edge-cases, sure, mainly with malformed releases, and you've detailed some of them - keep posting these (to Requests or Bugs forum, depending, and in both cases give enough info to reproduce, otherwise it's pointless) - but Alt.Binz works fine in daily use 99% of the time, as those of us who've been using it for many years now can confirm.

[elephant66]

Who knows what causes the failure to extract. 
i suggested a few possibilities,
but that doesn't account for all.

in the case i am talking about:

I believe that once Altbinz fails to repairing/extracting one item, then it stops repairing/extracting all together.
I cue up a load of things .  come back in the morning only to find 33% have extracted
sometimes 33% some times 70% sometime 100% 

-there's no real pattern in the what stops it extracting
- i've been using the app since July 12, 2010
- average of 300GB to 700GB per month
- i would say the failure to extract files behaviour is representative of how the app has functioned - in lots of different versions

no real pattern.  sometimes i look in the folders in the PC explorer as they are downloading etc.  Sometimes i just leave the app running and not touch anything.

I though it might be a known problem

by the looks of things Hecks hasn't experienced this problem.



I found a fix

-------

solved with par and rar portable

http://www.portablefreeware.com/forums/viewtopic.php?t=3447

----

but on another note

you guys could fix the 'sample file extracts' instead of the 'full file' problem  (mentioned above)

I download a video but get the 1 minute sample rather than 1h30m

surely Altbinz could tell from the file size downloaded that this behaviour is incorrect.

------

Anyway keep up the good work

[Hecks]

Yes, in certain situations, once the par2 process crashes it won't continue processing the rest of the queue - you'll find posts about this on the forum, and some fixes and workarounds. There are always reasons for this, though, and it's far from being the majority experience. With now 1000s of users, we'd be swamped here with complaints daily if that were true ...

So to repeat:

1. If Alt.Binz isn't working as expected, post a report in the Bugs forum that can be reproduced so it can be fixed.

2. If Alt.Binz is working as expected , but you'd rather it worked differently (like with handling of identically named files), post a request in the Request forum - one request per thread.

[elephant66]

cheers bud

I'll use par and unrar

don't want to tiddle around with 'workarounds'

[munchies2x]

Yeap, affecting me as well. Have been silent bout this, as I thought I was downloading excessively lol

[leechmaster]

Me on the other hand is experiencing the issue that sometimes the decoding just stops although all files are downloaded and I have a queue of 20+ decoding which doesn't decode. It's not due to CPU being busy as this happens with 5% CPU load as well. Any ideas?

[Rdl]

Me on the other hand is experiencing the issue that sometimes the decoding just stops although all files are downloaded and I have a queue of 20+ decoding which doesn't decode. It's not due to CPU being busy as this happens with 5% CPU load as well. Any ideas?

You should have something in log.