mini-moose
21st July 2012, 08:52
I'm trying to encode an h264/AVC with x264.exe via cmd using lavf decoder instead of avisynth.
I get all sorts of notifications/warnings on the 2 different sourced tests I tried:
1) using m2ts source it gives this message at the beginning of the encode:
[NULL @ 01538d80] start time is not set in estimate_timings_from_pts
[NULL @ 0153abc0] start time is not set in estimate_timings_from_pts
cmd used:
x264.exe --level 4.1 --crf 19 --preset slow --keyint 240 --min-keyint 24 --demuxer lavf --fps 24000/1001 --frames 10001 --vf crop:left=0,top=132,right=0,bottom=132/resize:width=1280,height=544,method=spline,sar=1:1 -o test1.mkv "00012.m2ts"
2) using mkv (just the video from an m2ts demuxed to mkv - different one than the first) - constant msgs :
[matroska,webm @ 014b2a40] Unknown entry 0x1654AE6B01 0:04:32
[matroska,webm @ 014b2a40] Unknown entry 0x1654AE6B02 0:03:08
[matroska,webm @ 014b2a40] Unknown entry 0x1654AE6B04 0:02:30
at some point it turns to red msgs:
[h264 @ 03079f80] number of reference frames (0+4) exceeds max (2; probably corrupt input), discarding one
[h264 @ 03b64000] number of reference frames (0+4) exceeds max (2; probably corrupt input), discarding one
[h264 @ 0156d0a0] number of reference frames (0+4) exceeds max (2; probably corrupt input), discarding one
and then back to the firs unuknown entry msgs.
cmd used:
x264.exe --level 4.1 --crf 19 --preset slow --keyint 240 --min-keyint 24 --demuxer lavf --fps 24000/1001 --frames 10001 --vf crop:left=6,top=0,right=0,bottom=0/resize:width=1280,height=720,method=spline,sar=1:1 -o test2.mkv "avc_vid.mkv"
I tried several times running that encode and the red msgs don't always show up and when they do it's not always in the same stage. the matroska,webm msgs however are constant.
edit:
I also tried using .h264 as input.
right away I received a single "[h264 @ 019929e0] Estimating duration from bitrate, this may be inaccurate" notice and a few minutes in a nice long block of "[h264 @ 015930a0] number of reference frames (0+6) exceeds max (4; probably corrupt input), discarding one" red warnings.
Also it overrides the --fps 24000/1001 switch and uses 25/1 fps.
I get all sorts of notifications/warnings on the 2 different sourced tests I tried:
1) using m2ts source it gives this message at the beginning of the encode:
[NULL @ 01538d80] start time is not set in estimate_timings_from_pts
[NULL @ 0153abc0] start time is not set in estimate_timings_from_pts
cmd used:
x264.exe --level 4.1 --crf 19 --preset slow --keyint 240 --min-keyint 24 --demuxer lavf --fps 24000/1001 --frames 10001 --vf crop:left=0,top=132,right=0,bottom=132/resize:width=1280,height=544,method=spline,sar=1:1 -o test1.mkv "00012.m2ts"
2) using mkv (just the video from an m2ts demuxed to mkv - different one than the first) - constant msgs :
[matroska,webm @ 014b2a40] Unknown entry 0x1654AE6B01 0:04:32
[matroska,webm @ 014b2a40] Unknown entry 0x1654AE6B02 0:03:08
[matroska,webm @ 014b2a40] Unknown entry 0x1654AE6B04 0:02:30
at some point it turns to red msgs:
[h264 @ 03079f80] number of reference frames (0+4) exceeds max (2; probably corrupt input), discarding one
[h264 @ 03b64000] number of reference frames (0+4) exceeds max (2; probably corrupt input), discarding one
[h264 @ 0156d0a0] number of reference frames (0+4) exceeds max (2; probably corrupt input), discarding one
and then back to the firs unuknown entry msgs.
cmd used:
x264.exe --level 4.1 --crf 19 --preset slow --keyint 240 --min-keyint 24 --demuxer lavf --fps 24000/1001 --frames 10001 --vf crop:left=6,top=0,right=0,bottom=0/resize:width=1280,height=720,method=spline,sar=1:1 -o test2.mkv "avc_vid.mkv"
I tried several times running that encode and the red msgs don't always show up and when they do it's not always in the same stage. the matroska,webm msgs however are constant.
edit:
I also tried using .h264 as input.
right away I received a single "[h264 @ 019929e0] Estimating duration from bitrate, this may be inaccurate" notice and a few minutes in a nice long block of "[h264 @ 015930a0] number of reference frames (0+6) exceeds max (4; probably corrupt input), discarding one" red warnings.
Also it overrides the --fps 24000/1001 switch and uses 25/1 fps.