Hum, sorry, but it seems that it's the profile high that is used with the preset faster:
Quote:
E:\BD3D2MK3D_projects\test_faster\00015>"D:\Tcl\work\BD3D2MK3D\toolset\avs2yuv.exe" "__ENCODE_3D_MOVIE.avs" -frames 3084 -o - | "D:\Tcl\work\BD3D2MK3D\toolset\x264_x64.exe" --crf 22 --preset faster --sar 1:1 --range tv --colormatrix bt709 --frame-packing 3 --qpfile chapters_3D.qpfile --frames 3084 --fps 24000/1001 --output "00015_3D.264" --demuxer y4m --stdin y4m -
__ENCODE_3D_MOVIE.avs: 1920x1080, 24000/1001 fps, 3084 frames
y4m [info]: 1920x1080p 1:1 @ 24000/1001 fps (cfr)
x264 [info]: using SAR=1/1
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.1 Cache64
x264 [info]: profile High, level 4.0
[3.0%] 94/3084 frames, 14.05 fps, 1172.49 kb/s, eta 0:03:32
|
I've also verified the other presets, and only the superfast preset gives not a high profile. In that case, it's baseline, not main. So, unless you force x264 to use the main profile by specifying additional x264 options, BD3D2MK3D is right. Or x264 is wrong.