<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><blockquote type="cite"><div>WHAT? Just a while ago I realized I'm passing H.264 encoded buffers to H264VideoStreamFramer, which is perhaps doubly encoding them to H.264 again.</div><div><br></div><div>Am I accidentally H.264 encoding twice? Does the original ByteStreamFileSource fed to H264VideoStreamFramer feed raw buffers to H264VideoStreamFramer?</div></blockquote><div><br></div>I think you're confused about what our software does. *None* of our software does *any* encoding. In particular, the "H264VideoStreamFramer" and "H264VideoStreamDiscreteFramer" classes each take - as input - already-encoded H.264 video data. They don't do any 'encoding' (because the input data is already encoded. All they do is parse the input H.264 video data, and output a sequence of H.264 'NAL units', with proper 'presentation time' and 'duration' values.</div><div><br></div><div>The difference between these two classes is that "H264VideoStreamFramer" takes - as input - H.264 video data that appears in a byte stream (e.g. a file or pipe). "H264VideoStreamDiscreteFramer", on the other hand, takes as input discrete NAL units (i.e., one NAL unit at a time), *without* any preceding 'start code'.</div><div><br></div><div>So, the choice of which of these 'framer' classes to use depends on what kind of data comes out of your "MF_H264_DeviceSource" class. If this class outputs an unstructured byte stream (that contains H.264 video data, with 'start codes' preceding each NAL units), then use a "H264VideoStreamFramer". If, however, your "MF_H264_DeviceSource" class outputs a sequence of NAL units (one at a time, without a preceding 'start code'), then use a "H264VideoStreamDiscreteFramer" instead.</div><div><br></div><div>In either case, your 'framer' object should then be fed into a "H264VideoRTPSink" object, for streaming.</div><br><div apple-content-edited="true">
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">Ross Finlayson<br>Live Networks, Inc.<br><a href="http://www.live555.com/">http://www.live555.com/</a></span></span>
</div>
<br></body></html>