#18 x264_encoder_encode failed (--tff)

[Anonymous]

x264vfw_full_42_2538bm_41390

When I try to compress an interlaced video (1920x1080, 60i) with --tff option in VirtualDub 1.10.3, I get an error "x264_encoder_encode failed". Compression options are in the attached file.

x264 log file:

x264vfw [warning]: --psnr used with psy on: results will be invalid!
x264vfw [warning]: --tune psnr should be used if attempting to benchmark psnr!
x264vfw [warning]: interlace + weightp is not implemented
x264vfw [info]: using SAR=1/1
x264vfw [warning]: interlaced (1) > level limit (0)
x264vfw [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 AVX2 LZCNT BMI2
x264vfw [info]: profile High, level 4.2
x264vfw [error]: x264_encoder_encode failed
x264vfw [info]: frame I:1 Avg QP: 0.25 size:589225 PSNR Mean Y:67.70 U:67.48 V:66.80 Avg:67.50 Global:67.50
x264vfw [info]: mb I I16..4: 70.1% 8.7% 21.1%
x264vfw [info]: final ratefactor: 23.25
x264vfw [info]: field mbs: intra: 0.0%
x264vfw [info]: 8x8 transform intra:8.7%
x264vfw [info]: coded y,uvDC,uvAC intra: 98.3% 81.7% 81.6%
x264vfw [info]: i16 v,h,dc,p: 7% 4% 80% 9%
x264vfw [info]: i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 21% 10% 49% 4% 3% 4% 3% 4% 3%
x264vfw [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 25% 10% 35% 6% 5% 6% 4% 6% 4%
x264vfw [info]: i8c dc,h,v,p: 80% 4% 8% 8%
x264vfw [info]: SSIM Mean Y:0.9998189 (37.422db)
x264vfw [info]: PSNR Mean Y:67.697 U:67.481 V:66.800 Avg:67.499 Global:67.499 kb/s:141272.73

[BugMaster]

Looks like you simply go out of memory (32-bit apps without /LARGEADDRESSAWARE flag can't allocate more than 2 GB). Try to lower memory usage by lowering --sync-lookahead, --rc-lookahead, --ref, --bframes or --threads from default values (--rc-lookahead is the most memory hog among them iirc). Otherwise upgrade to using x64 version of VirtualDub and x264vfw. You can look at memory usage in Process Explorer to look if it is near 2 GB limit.

P.S. MBAFF encoding (--tff/-bff) need more memory than progressive encoding.

[Anonymous]

Yes, seems like you right, it is memory. x64 version works fine. Lowering memory usage also works. Thanks! Case closed.

PS: Maybe you should add a "Out of memory" error message in the log file to avoid such questions...