Strange error with x264

[max-holz]

This morning I see that an encoding fails with an error that I never seen before, I use an avs script that I tested many times so I think it's not that the cause. This is the log:


Starting job job1-1 at 8.52.10
Job is a video job. encoder commandline:
--pass 1 --bitrate 740 --stats "C:\Scambio\Elaborazione Video\PortiereDiNotte\Portiere.stats" --bframes 3 --b-pyramid --filter -2,-1 --subme 1 --analyse none --me dia --threads 2 --progress --no-psnr --output NUL "C:\Scambio\Elaborazione Video\PortiereDiNotte\Portiere.avs"
successfully started encoding
Processing ended at 4.40.20
--------------------------------------------------------------------------

Log for job job1-1

avis [info]: 640x336 @ 25.00 fps (169725 frames)
x264 [info]: using cpu capabilities MMX MMXEXT SSE SSE2

--------------------------------------------------------------------------
job job1-1 has been processed. This job is linked to the next job: job1-2
Starting job job1-2 at 4.40.20
Job is a video job. encoder commandline:
--pass 2 --bitrate 740 --stats "C:\Scambio\Elaborazione Video\PortiereDiNotte\Portiere.stats" --ref 16 --mixed-refs --no-fast-pskip --bframes 3 --b-pyramid --b-rdo --bime --weightb --filter -2,-1 --subme 7 --trellis 1 --analyse all --8x8dct --me umh --threads 2 --progress --no-psnr --output "C:\Scambio\Elaborazione Video\PortiereDiNotte\Portiere.mkv" "C:\Scambio\Elaborazione Video\PortiereDiNotte\Portiere.avs"
successfully started encoding
Processing ended at 4.40.46
--------------------------------------------------------------------------

Log for job job1-2

avis [info]: 640x336 @ 25.00 fps (169725 frames)
x264 [error]: ratecontrol_init: can't open stats file
x264_encoder_open failed
desired video bitrate of this job: 740 kbit/s - obtained video bitrate: 0 kbit/s
--------------------------------------------------------------------------

[Manao]

In what way don't you understand "ratecontrol_init: can't open stats file" ?

[max-holz]

In what way don't you understand "ratecontrol_init: can't open stats file" ?

I control the stats file and I open it with a text editor as test. I hoped in some explanations, never happened before such kind of error.

[Manao]

Ok, i checked the source code. Wouldn't your system harddrive be full, by any chances ? Because that error happens in two cases : you can't open the previous stat files, or you can't create a new one.

[max-holz]

Ok, i checked the source code. Wouldn't your system harddrive be full, by any chances ? Because that error happens in two cases : you can't open the previous stat files, or you can't create a new one.

No, I will do the encoding another time, perhaps is only an isolated error cos my system was very busy at that moment.

[MeteorRain]

@max-holz:

Can you confirm that the x264 1st-pass encoding was successfully completed?

In some (very rare) time, x264 crashes but no error info given (in MeGUI, i suppose you use this tool). As we know, when fps was abnormal, x264 crashed and megui reported no errors.

[max-holz]

@max-holz:

Can you confirm that the x264 1st-pass encoding was successfully completed?

In some (very rare) time, x264 crashes but no error info given (in MeGUI, i suppose you use this tool). As we know, when fps was abnormal, x264 crashed and megui reported no errors.

I suppose, the time in the log seems confirm that 1st-pass encoding was successfully. I'am doing another encode.

[max-holz]

Another error: :(

Runtime error

R6034

An application made an attempt to load the C runtime library incorrectly.

Uhm after this error seems that 2nd-pass start correctly, the .mkv output is produced. I don't know what to say!!!

[MeteorRain]

I suppose, the time in the log seems confirm that 1st-pass encoding was successfully. I'am doing another encode.
afaik, if x264 completed its encoding, there should be some info like:
x264 [info]: slice I:* Avg QP:* size: *
x264 [info]: slice P:* Avg QP:* size: *
x264 [info]: slice B:* Avg QP:* size: *
x264 [info]: mb I I16..4: ****
x264 [info]: mb P I16..4: *** P16..4: ***** skip:*
x264 [info]: mb B I16..4: *** B16..8: *** direct:* skip:*
x264 [info]: final ratefactor: *
x264 [info]: kb/s:****

Actual bitrate after encoding without container overhead: *or some what.
so, if possible, try run
x264 xxxxxxxxxxxxxxxxxxxxxxxxxxx(a lot options) --progress 2>encode.log
and open encode.log to see if it IS completed.