COMPRESSIBILITY TEST bug !!

[Daweed]

Hi,
i 've just install Gordian and it 's unable after the compressibilty test to have the value importing in gordian
where does this stat files is saved and is it possible to put it in manually!!
thanks
David

[jggimi]

There should be a _Gknot.log file (either in your working folder or in your Gknot folder) from a compress test. But even without it, I have two guesses -- well one guess, an encoder failure -- but two likely reasons: You are using Gknot 0.27, but did not install both the RipPack and the SystemPack, so you have not completed the installation of all components.

You are using DivX 5, and installed 5.03. Gknot will not work with DivX 5.03Other possibilities exist, but without seeing your log file, these are the most likely.

[manono]

Hi and welcome to the forum-

Come on, man. You are making your first post after installing for the first time and running a well known, much beloved, and long time proven piece of software. And you're proclaiming a bug with double exclamation points? Now just think for a minute. What do you suppose the chances are that the fault is at your end, rather than with GKnot? :rolleyes: jggimi's got the answer for you. Next time think before you speak. Sorry if I sound harsh. Must have gotten up on the wrong side of the bed.:)

[Flora]

I'd this bug once with everything installed correctly 0.27 + system pack +Divx 3.11 + Divx 5.02 Pro and it could not complete the compressibility test in divx 5.02 on a specific movie. (Strange Days)
Only this one though.
it works in Divx 3.11

Might have been my pc.
I've changed the psu since then but didn't bother myself to try again

[TiLOLO]

Hi Flora, i had the same bug on my PC. The solution is to remove GKnot + System Pack + the DivX codec. After this, (re)install Gordian and the system pack (once again !!!!!!). It could works...Normalement....;)

A plus...

[Flora]

...all I wanted to say is that sometimes the problems with Gknot might come from hardware especially PSU.
Keep in mind that Divx Encoding is very ressources consuming and therefore it stresses the hardware.

a++ aussi. ;)

[wingphil]

do you mean cpu? if you do then yes but only if you've overclocked it or are using an insufficient heatsink/fan. if your chip is running within its design parameters you should be able to leave it for days at 100% load.

if your psu is not rated highly enough your machine will generally not start at all.

[Flora]

For instance it is a common problem that you can boot no problem. but then anytime you're stessing your PC then it freezes.

Nothing to do with overclock and FSB to high, because it does it even when you do not overclock.
It is the PSU that is the cause of this kind of problem.
Trust me. I had enough pb with PSUs to tell you that. ;)

[Babeinternational]

If cpu is central processing unit, what is psu?
CPU causing compression check errors?
A compression check doesn't use more CPU than an average encoding project (difference is in the script), therefore if your cpu crashes when doing a compression check, you should also have this problem while encoding...
Anyway, gotta have guts nowadays to display a huge french flag...
Chapeau bas, Mademoiselle (?)

[Flora]

Originally posted by Babeinternational
If cpu is central processing unit, what is psu?
CPU causing compression check errors?
A compression check doesn't use more CPU than an average encoding project (difference is in the script), therefore if your cpu crashes when doing a compression check, you should also have this problem while encoding...
Anyway, gotta have guts nowadays to display a huge french flag...
Chapeau bas, Mademoiselle (?)


PSU stands for Power Supply Unit : Alimentation in french
I do not think compressebility check uses more power (WATT) than a complete compression. it's probably about the same. The main thing with crappy PSU is that they've got problem to raise in power very quickly. When starting doing a Comp check you virtually go from 0% CPU usage up to 100% in a very very small time.
more cpu usage = more power consumed.
A 1800+ consume up to 55 Watt when cpu usage = 100%. and this is on the 5V ramp of your PSU which is generally for a standard 300Watt PSU between 15 and 20A.
5*20=100 Watt of maximum consumation on the 5V ramp. that means that when your 1800+ is running at full speed you've only 45 Watt left on your 5V ramp. which is used to other devices such as Graphic card.
No need to say that a recent G-card + a fast processor would take the crap out of your 300Watt PSU in no time.

The Comp check is fast so very quickly you go back to 0% CPU usage. basically it is a bit hard to follow for crappy psu.
but you're right to mention that it should cause the whole compresion to crash because actually it did once or two.
As I said earlier I changed the PSU and then all those problem vanished.


About the french flag the only things I can say is: I love France.
And I ain't talking about what I think of the current international crisis... ;)

[ohliuv]

Originally posted by Babeinternational
Anyway, gotta have guts nowadays to display a huge french flag...

the french fries are off the menu in the White House, now they call them 'freedom' fries :D

[Babeinternational]

Et vous les Belges savez mieux que quiconque que les Français n'ont pas inventé les frites...
Oups, getting off topic.

[KitKat]

Didn't feel like starting a new thread... Somewhat same prob here.

My comp. check fails cuz VirtualDub, upon startup, shows the error "Problem reading log file" ans exits right away. NEbody got a clue?

Now, if you don't mind, I'll go "freedom kiss" my girlfriend! Frites alors! :-D

[KitKat]

Hehe, forget it. I found what was my problem. It was the the divx codec's log file (divx.log) VitualDub was refering to. Somehow, it expects a file to be already present, even if it's just an empty file... Go figure... :p

[Sephiros]

I must say I don't think PSU is in anyway related to these kind of software problem.

If the PSU wasn't able to give enough power in a short period of time, I see3 outcomes:
- Enough capacitors on the Mobo to keep the power up long enough :D
- System freeze (or reboot on modern mobo like for Athlon P4)
- System shutdown (not a windows shutdown, just like you unplugged it from he outlet)

I once had a shitty PSU (which by the way exploded in less than a year) and I had some random system shutdown when playing games (I wasn't in the divx business by the time) but it just act as if you were unplugging the comp. from the outlet...

Anyway, I love France too, and French/belgium/freedom/whateveryouwant fries as well !

Patrick (St Patrick day tomorrow yeaah!)

Oh, and when the PSU exploded, well, surprisingly, it shutdown :D