FAQ: GKnot fails to find a log file! (Last update 17 June 2003)

FAQ: GKnot fails to find a log file! (Last update 17 June 2003) 

Q: What is this log file, and why is it important? A: In any 2-pass or multiple pass DivX encoding, the first pass produces a frame-by-frame analysis of the video stream, and the .log file is this analysis. It is used by the second and subsequent passes to produce the final video. This log is also used during single pass compression tests in Gknot. Without the .log file, a compression test produces no results. Without the .log file, a multiple pass encoding will not complete. Q: Why would DivX not create the log? A: These are the most likely possibilities, in order of frequency:DivX is either not installed, or not installed properly. The video served by the AviSynth (.avs) script may have errors or produce invalid video for Virtual Dub and the DivX codec. With Gknot 0.28 and above, you may not have YV12 color space properly configured in Windows. Your computer is overclocked or has insufficient airflow or cooling. You've run out of disk space. Q: How can I tell which is my problem? A: Take them in order.Check to see if Virtual Dub sees the proper release of the DivX codec. Start VDub, use the Video...Compression command, and make sure that the correct release of DivX is installed. Check to see if your AviSynth script (.avs file) can produce video, and you can scroll through properly. Use GKnot's Preview function to open the script in Windows Media Player, or open the script with VDub or your favorite AVI player. If it produces video, make sure the resolution is valid for DivX encoding. (If you leave Gknot's Modulo settings at default Mod32/Mod16, you will not have this problem.) If the script fails, there is either an error in the script, or AviSynth is not installed properly. If VdubMod fails to encode the first pass with "videosourceavi error: the sourceimage format is not acceptable. (error code -2)" you may have to make a manual change in your Windows registry. See TelemachusMH's comment in . Encoding stresses your CPU, producing heat beyond the amounts produced with most desktop applications. If you are overclocking, set your PC back to normal. If you have insufficient airflow, you might also have problems. There are motherboard monitors and stress tests available. For more information, peruse the forum. Are you low on disk space? The encoder will produce both the log file as well as a dummy AVI file. {Edited for 0.28 releases of Gknot. Include new YV12 error, and cleaned up 2-pass discussions to include all multipass encodings.}

Same Log File problem 

GKnot 28 is not a production release. Development releases should be discussed in the forum.

Fixing the problem 

Hi- I wish that Gknow had an uninstall program that removed everything, including all the registry keys GKnot Options Tab-Delete Registry Keys.

Thank you 

Yes, thank you. I had already tried that and still had the problems until I did the manual registry deletions. Cheers.

Hi there I still cannot beat this problem. I have search this forum for all hints about this problem and have tried almost anything. But still no success. I have cleaned the registry by hand uninstalled a countless number of times. I still get an error message during second pass of encoding using divx 5.05. I run latest version of GordianKnot. I can do compressebility test and I can do preview in windows media player. But I still get the following message: 18:13:46: Started DivX5-First Pass: E:\test.avs 18:31:06: Finished DivX5-First Pass. Duration: 17 minutes, 19 seconds. 18:31:06: Trying to open Log-file. 18:31:09: Error: Could not open E:\\vdenc.log 18:31:09: Error: Could not count encoded Frames. 18:31:09: Speed: 14300.668 Frames per Second. 18:31:09: WARNING: Number of counted frames differs from settings! 18:31:09: WARNING: Settings: 12486 18:31:09: WARNING: Counted: 0 18:31:09: WARNING: Difference: 12486 18:31:09: Correcting Bitrate... 18:31:09: Original Bitrate = 3072 k(=1000)Bits/s 18:31:09: ERROR: Correction impossible. 18:31:09: Now encoding at 3072 k(=1000)Bits/s The logfile is located on the E-drive and I can open it with notepad without any problems. Do any of you have any suggestions of what to check next? Thanks in advance, Mogens :confused:

It appears to be a path naming problem, since it's searching for two back slashes. I'll PM len0x and ask him to review...