LessThanJake
27th September 2008, 22:57
Hi,
I did some tests on splitting H264-ESs.
AFAIK it is possible to split before a following IDR-Frame.
The ITU-T documentation says NAL-Unit-Type = 5 --> Coded Slice of an IDR-picture. So "5" ends up in an "00 00 00 01 65" - Hex-Sequenz for the startcode.
When cutting the bytestream with an Hex-Editor before any IDR-startcode, the first part can be played back without problems, but the second part can not be decoded accurately.
Of course I inserted the same SPS/PPS at the beginning of the second part.
So, how is this possible, when there can be no reference over an IDR-picture? Did I disregard something? Maybe a non-linear NALU-Order?
test-source:
~650 Frames Bick Buck Bunny
MeGUI, x264 unrestricted 1pass const. Quality / 24fps / crf18 @MKV / ~3MB
http://depositfiles.com/files/8280572
greets
LTJ
I did some tests on splitting H264-ESs.
AFAIK it is possible to split before a following IDR-Frame.
The ITU-T documentation says NAL-Unit-Type = 5 --> Coded Slice of an IDR-picture. So "5" ends up in an "00 00 00 01 65" - Hex-Sequenz for the startcode.
When cutting the bytestream with an Hex-Editor before any IDR-startcode, the first part can be played back without problems, but the second part can not be decoded accurately.
Of course I inserted the same SPS/PPS at the beginning of the second part.
So, how is this possible, when there can be no reference over an IDR-picture? Did I disregard something? Maybe a non-linear NALU-Order?
test-source:
~650 Frames Bick Buck Bunny
MeGUI, x264 unrestricted 1pass const. Quality / 24fps / crf18 @MKV / ~3MB
http://depositfiles.com/files/8280572
greets
LTJ