Quote:
Originally Posted by wiggaz
Would be possible to have the log of x264?
|
Well, it's possible, but the log file will be very large, because it includes all lines produced by x264, including the % of completion. For example, you will get something like this:
Code:
y4m [info]: 1920x1080p 0:0 @ 24000/1001 fps (cfr)
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.1 Cache64
x264 [info]: profile High, level 4.1
[0.0%] 1/119388 frames, 0.51 fps, 241.29 kb/s, eta 64:46:02
[0.0%] 12/119388 frames, 5.44 fps, 32.43 kb/s, eta 6:05:35
[0.0%] 23/119388 frames, 9.33 fps, 23.41 kb/s, eta 3:33:12
[0.0%] 34/119388 frames, 12.52 fps, 20.21 kb/s, eta 2:38:50
[0.0%] 45/119388 frames, 15.06 fps, 18.55 kb/s, eta 2:12:07
[0.0%] 55/119388 frames, 16.91 fps, 17.66 kb/s, eta 1:57:38
[0.1%] 61/119388 frames, 17.22 fps, 17.23 kb/s, eta 1:55:30
[0.1%] 66/119388 frames, 17.36 fps, 16.97 kb/s, eta 1:54:33
[...]
There is a lot of "[X.X%]" lines that will be saved to the log file without any good reason.
As far as I know, there is no way to capture only the interesting lines or filter out the %.
I can add an option to save the log if you wish. It's not difficult to do. In the meantime, you can edit the __ENCODE_3D.cmd script yourself, and add " 2>&1 | tee x264.log" at the very end of the x264 command. For example:
Code:
[...]
"path\to\BD3D2MK3D\toolset\avs2yuv.exe" ^
"__ENCODE_3D_MOVIE.avs" -frames 119388 -o - ^
| "path\to\BD3D2MK3D\toolset\x264_x64.exe" ^
--crf 20 --preset slower --level 4.1 --vbv-bufsize 78125 --vbv-maxrate 62500 ^
--frame-packing 3 --qpfile chapters_3D.qpfile --frames 119388 --fps 24000/1001 ^
--output "00000_3D.264" --demuxer y4m --stdin y4m - 2>&1 | tee x264.log
[...]
Note the space between the "-" and 2>&1.
Thanks for your kind words!