On Thu, Oct 7, 2010 at 5:47 PM, Ross Finlayson <span dir="ltr"><<a href="mailto:finlayson@live555.com">finlayson@live555.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Ah, yeah--I forgot about that. For H264, you really need to write some code to parse the SPS/PPS information that's present in the SDP exchange<br>
</blockquote>
<br></div>
Note that we already provide code to do this parsing; you don't need to write it yourself.<br>
<br>
Just call "MediaSubsession:: fmtp_spropparametersets()" to get the SPS/PPS string, and then call "parseSPropParameterSets()" to parse it. See, for example, the code for "H264VideoFileSink", which uses this.<br>
<font color="#888888"><br></font></blockquote><div><br>No, not just base-64 decode it, but actually _decode_ the SPS/PPS info. You do need to do this to get the properties of the incoming video, like resolution, profile, level, etc. It involves exponential golomb decoding and following the H264 specification, and is generally necessary for most media frameworks like DShow and GStreamer. <br>
</div></div><br>