Error Messige

[Dodger44]

:rolleyes: Yep i'm a Newbie
First just want to say how much i like gknot. The first 2 movies i did came out fantastic.
Now on my 3rd attempt i'm getting this error
I didn't want to post the entire log it's just too big. :)


8:42:46 AM: Started DivX5-First Pass: D:\Movies vob\stickup.avs
1:28:25 PM: Finished DivX5-First Pass. Duration: 4 hours, 45 minutes, 38 seconds.
1:28:25 PM: Trying to open Log-file.
1:28:25 PM: Error: Could not open D:\Movies vob\stickup.log
1:28:25 PM: Error: Could not count encoded Frames.
1:28:25 PM: Speed: 0.000 Frames per Second.
1:28:25 PM: WARNING: Number of counted frames differs from settings!
1:28:25 PM: WARNING: Settings: 174647
1:28:25 PM: WARNING: Counted: 0
1:28:25 PM: WARNING: Difference: 174647
1:28:25 PM: Correcting Bitrate...
1:28:25 PM: Original Bitrate = 1883 k(=1000)Bits/s
1:28:25 PM: ERROR: Correction impossible.
1:28:25 PM: Now encoding at 1883 k(=1000)Bits/s

Can someone please tell me what this means and what i'm doing wrong?

[jggimi]

Welcome to the forum! I hope you find it useful.

The log file "D:\Movies vob\stickup.log" that cannot be opened is the frame-by-frame analysis produced by the first pass and used by the second.

Does this file exist? Can you open it? How big is it?

There can be several reasons for not producing a log file... DivX 5 codec not installed or not installed properly.

You can check this by using the Video....Compression command in VirtualDub. If DivX 5 is in the list of codecs, then it is installed properly.

AviSynth script (.avs file) has an error, or AviSynth not installed.

You can check this by attempting to open your .avs file in VirtualDub or in your favorite AVI player. If you get video, then the script is working. If there is an error in the script, you will get a message telling you which line is in error. If you don't have AviSynth installed, you won't be able to open the script.

Running out of disk space.

Heat problems -- often overclocking -- that cause CPU instability.I can't tell anything else looking at just this subset of the log. And next time, please:9) Use a title that describes the content of your post.There are many applications in use by the community; you wanted this one looked at by Gknot users.