We have things working now by avoiding the issue by creating our own
customized DiscreteFramer. It avoids the problem by directly using
the output buffer and does not touch the Bank buffers. I suspect
there is a problem with the H264VideoStreamFramer.
No, I think it's OK. However, it expects
Ross,
We have things working now by avoiding the issue by creating our own
customized DiscreteFramer. It avoids the problem by directly using the
output buffer and does not touch the Bank buffers. I suspect there is a
problem with the H264VideoStreamFramer.
BTW, does it conflict with the H264 sta
I tried the "H264VideoStreamDiscreteFramer" first and got the following:
Warning: Invalid 'nal_unit_type': 0. Does the NAL unit begin with a
MPEG 'start code' by mistake?
Well yes, apparently it does. Note that in H.264 (unlike MPEG-1, 2
or 4), MPEG 'start codes' are supposed to be used onl
*Thanks for the response, Ross.
I tried the "H264VideoStreamDiscreteFramer" first and got the following:
Warning: Invalid 'nal_unit_type': 0. Does the NAL unit begin with a MPEG
'start code' by mistake?
With the "H264VideoStreamFramer" and BANK_SIZE set to 200, I get the
following for a few
I'm puzzled as to why I get this problem as this should be common to
both MPEG4 and H264. Any ideas?
I notice that for MPEG-4 you are using a
"MPEG4VideoStreamDiscreteFramer", but for H.264 you are using a
"H264VideoStreamFramer". If your H.264 encoder delivers discrete NAL
units (i.e., one-
