2 Random Bugs For Gknot .23

[warrior15r]

I've noticed 2 random bugs that the latest version of gknot that you gusy should take care of.

1) Azid step for trying to find maximum gain value is randomly skipped. I've experience it on several movies, and on 2 different computers. Sometimes I start the encoding process, "trying to find maximum gain value" step is missing. So i stop it and restart the process again. Trying it the second time, this step works. Again this is a random error that occurs plenty of times. Please address it.

2)Encoding First pass gets an error message and first pass is skipped but 2nd pass keeps going to try to encode the whole film. The problem is solved by just ending the queues and restarting the process again. Running the encoding jobs the second time, there are no error messages. This problem also occurs randomly on more than one film.

Can someone give me an explanation on these errors? I think creators or gknot need to fix these bugs.

[TheWEF]

if the bug really is random, then the problem is your system and not the program.
if not you have to find out and tell me exactly how to reproduce it. i never had these problems...

wef.

[MaTTeR]

@warrior15r
Your system is obviously the culprit because the rest of us don't see these issues whatsoever. Are you perhaps another Win98 user?

[warrior15r]

I actually have two systems that are doing this. One of them was freshly formatted because i thought it would solve the problem. Problem stil persisted after formatting. Could there be any chance that azid is really going but is just not displayed in log? I'm running windows xp professional on both systems.

[catoichi]

I have the same problem as warrior15r. It happened when I tried to re-do the encoding of the same file a third time (it was too big the first time, and the subs were in the wrong place the second time). This is what the log looks like:

7:38:59 PM: Started DivX4-First Pass: G:\foo\bar.avs
7:39:00 PM: Finished DivX4-First Pass. Duration: 0 seconds.
7:39:00 PM: Trying to open Log-file.
7:39:00 PM: Error: Could not open G:\foo\bar\bar_2.log
7:39:00 PM: Error: Could not count encoded Frames.
7:39:00 PM: Speed: 0.000 Frames per Second.
7:39:00 PM: WARNING: Number of counted frames differs from settings!
7:39:00 PM: WARNING: Settings: 115642
7:39:00 PM: WARNING: Counted: 0
7:39:00 PM: WARNING: Difference: 115642
7:39:00 PM: Correcting Bitrate...
7:39:00 PM: Original Bitrate = 1073 k(=1000)Bits/s
7:39:00 PM: ERROR: Correction impossible.
7:39:00 PM: Now encoding at 1073 k(=1000)Bits/s

The first pass is simply skipped somehow. Do you need to see more of the log file?

Edit: Win2k SP2, Gordian Knot 0.23.0.17

- ichi

[guiguess]

Hi,

I have exactly the same problem than catoichi.
I don't have my log file anymore, but it writes the same thing, namely it can't open the .log file, and I don't understant why ...
So, is it a bug or a problem coming from us ?

My config : Win2k + Gordian 0.23 beta (+ patch)

[TheWEF]

Originally posted by catoichi
7:39:00 PM: Finished DivX4-First Pass. Duration: 0 seconds.

this means that virtualdub crashed for unknown reason and did not encode the first pass. most likely this happened because the divx4 codec has problems with your system. try to use 4.12 instead of 4.11 or the other way round.

wef.

[warrior15r]

I am using Divx 4.12.

Still no explanation for both problem # 1 & 2?

[TheWEF]

warrior15r, i already told you that i need more detailed information to even investigate this, at least a log or something...
what do you expect?

[MaTTeR]

@TheWEF

I wish I had your patience dude:D I don't know how you do it!

Suppose that warrior15r assumed you could mind read since you created the most awesome app ;)

[warrior15r]

Sorry WEF, I don't have a log. I'll post it the next time the error occurs. Thanks for your patience though.

[guiguess]

Ok, maybe it will help some of you guys : in fact I was using Divx 4.11 codecs. I upgraded to 4.12, and the problem is solved : it succeeds now in opening the .log file :

14:18:36: Started DivX4-First Pass: C:\movie\dvd2avi.avs
14:22:49: Finished DivX4-First Pass. Duration: 4 minutes, 13 seconds.
14:22:49: Trying to open Log-file.
14:22:50: Success: Log-file open.
14:22:50: Encoded: 2405 Frames.
14:22:50: Speed: 9.493 Frames per Second.
14:22:50: WARNING: Number of counted frames differs from settings!
14:22:50: WARNING: Settings: 239998
14:22:50: WARNING: Counted: 2405
14:22:50: WARNING: Difference: 237593
14:22:50: Correcting Bitrate...
14:22:50: Original Bitrate = 889 k(=1000)Bits/s
14:22:50: ERROR: Correction impossible.
14:22:50: Now encoding at 889 k(=1000)Bits/s
14:22:50: Started DivX4-Second Pass: C:\movie\dvd2avi.avs
14:26:51: Finished DivX4-Second Pass. Duration: 4 minutes, 1 second.
14:26:51: Speed: 9.956 Frames per Second.
14:26:51: Started Appending Credits and Muxing Audio.: C:\movie\dvd2avi_Movie.avi
14:27:10: Finished Appending Credits and Muxing Audio.. Duration: 19 seconds.
14:27:10: Done.
14:27:10: Movie = C:\movie\dvd2avi.avi
Total Encoding Time: 8 minutes, 34 seconds.
23/01/2002 14:27:10: Job "Movie Divx 4" finished.

There's still an Error while trying to correct the bitrate ... should I pay attention to this or is it normal and I don't have to worry ?
Thx.

[TheWEF]

i guess you just did a short test-encode here?
if yes then it's normal...

[guiguess]

Indeed, I encoded just 1 % of the movie to check if there was still the error, or if it worked.
It seems to work well so, I will test it this night :)

Thx for having taken time to reply.

[rui]

Originally posted by TheWEF


this means that virtualdub crashed for unknown reason and did not encode the first pass. most likely this happened because the divx4 codec has problems with your system. try to use 4.12 instead of 4.11 or the other way round.

wef.

Well, for me the solution to Vdub crashes was sticking with divx4.11 that comes in Gnot package :)
The last time i upgraded to divx 4.12, i got 2 Vdub crashes.
I already posted somewhere in the forum something about Vdub crashes and Gnot 0.23 My conclusion at the time was that the problem wasn't Gnot or Vdub but divx 4.12
I believe that divx.com forums has something about divx4.12 being a bit buggy in AMD platforms. The majority of crashes they reported there was with AMD's K6, but i saw some Tbird's crashes reports too.

[guiguess]

I just finished encoding, I did well, and the quality is quite good (the movie is Saving Private Ryan).
In fact, I could never obtain a good quality for this movie with codecs 3, and I'm not a Nandub expert, I just followed the guides without trying to tweak the options more than what was explained in the guides, and the quality was very very poor (2 CD's).
So I decided to try with the 4, I was used to the 3 + Nandub, it was the first time with the 4, but it worked well, I'm pretty satisfied of the quality that is - for *this* movie - really better than what I got with the 3, even if the encoding was a little long (9h30 for a movie of 2h40 on 2 700 Mo CD's, muxing 2 audios (encoded before), on a Pentium 3 1 GHz).

[catoichi]

I was using DivX 4.02, but have the same problem with 4.11 and 4.12. Encoding with Xmpeg 4.2 works fine, though. So I'm not sure the problem is with the DivX codec. I'm running on a dual P3 600 MHz system. It was working fine for quite some time and then suddenly stopped working (after encoding the same file a few times, like I said).

Edit:

Ahh.. it works without subtitles. Is there a known problem with VobSub? Or with GKnot+subs?

- ichi

[rui]

Originally posted by catoichi
Edit:

Ahh.. it works without subtitles. Is there a known problem with VobSub? Or with GKnot+subs?

- ichi
Hope not because i really like to encode using subtitles :)

[catoichi]

Certain combinations of subtitles, resize filter and noise filter cause the crash. I am running with subtitles, Sharp Bicubic resize and Medium Noise filters and it crashes only when "Put Noise Filter before Resizing (slower)" is selected under Extras. That checkbox is checked by default, so you must remember to uncheck it if you have problems.
(All of these options show up when you hit "Save & Encode", in case you are wondering.)

- ichi

[rui]

Well, thanks for the info :)
I will be sure to avoid the " deadly" combinations :D