[x264-devel] debug information
Stephan Menzel
stephan.menzel at gmx.eu
Mon Feb 23 11:40:13 CET 2009
Hi there,
I'm doing a bit of progress with my project to encapsulate an x264 encoded live stream into mp4. I took examples from the x264 source and bundled them with the mp4 output. Alas, the created file is nearly empty (707 bytes after close()) and so I'm wondering where I could start looking for the problem.
x264 writes debug output and so I thought it should be possible to read from it whether it actually encoded something successfully. This is what it writes:
x264 [info]: profile Main, level 3.0
set_param_mp4 setting res 640x480 for track 1
mp4 [info]: initial delay 0 (scale 25000)
x264 [debug]: frame= 0 QP=13.21 NAL=3 Slice:I Poc:0 I:1200 P:0 SKIP:0 size=141645 bytes PSNR Y:47.71 U:51.15 V:51.17 SSIM Y:0.99635
x264 [debug]: frame= 1 QP=12.84 NAL=2 Slice:P Poc:2 I:0 P:465 SKIP:735 size=1151 bytes PSNR Y:47.78 U:51.16 V:51.18 SSIM Y:0.99637
x264 [debug]: frame= 2 QP=12.86 NAL=2 Slice:P Poc:4 I:0 P:415 SKIP:785 size=668 bytes PSNR Y:47.78 U:51.17 V:51.18 SSIM Y:0.99637
x264 [debug]: frame= 3 QP=12.86 NAL=2 Slice:P Poc:6 I:0 P:410 SKIP:790 size=639 bytes PSNR Y:47.78 U:51.17 V:51.18 SSIM Y:0.99637
and so on. It always says I:0 after the first frame and only a few bytes coming out of it. The raw images come from a jpeg sequence, hopefully properly converted into YV12 (previous thread ;-)
Anyway, I'm just trying to find out whether I'm misusing gpac or x264 so if one can see anything helpful out of that debug out please let me know. I haven't got a clue what those values mean.
My impression is, that set_eop_mp4() doesn't get enough data. Isn't gf_isom_add_sample() the function that's actually writing the encoded data into the file? And yet, straceing it, I see no file IO in that function even though p_sample->dataLength is larger than zero (283294).
Cheers,
Stephan
More information about the x264-devel
mailing list