jggimi
17th March 2003, 21:32
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 http://forum.doom9.org/showthread.php?s=&threadid=51906.
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 PC Hardware (http://forum.doom9.org/forumdisplay.php?s=&forumid=16) 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.}
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 http://forum.doom9.org/showthread.php?s=&threadid=51906.
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 PC Hardware (http://forum.doom9.org/forumdisplay.php?s=&forumid=16) 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.}