On Wed, Sep 30, 2009 at 2:26 AM, Stas Desyatnlkov <span dir="ltr"><<a href="mailto:stas@tech-mer.com">stas@tech-mer.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div link="blue" vlink="purple" lang="EN-US">
<div>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">Sender only.</span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">I see some video providers that mix AVC into TS. </span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">NAL, SPS and PPS are all part of the elementary stream packet.
How they ensure that client receives SPS and PPS in time is not clear. Probably
the receiving side waits for the next SPS, PPS and start showing video after
that.</span></p></div></div></blockquote><div><br>OK, so the sender is not a "black box," like you describe, but something to which you could easily add the SPS/PPS info to the SDP exchange?<br><br>You *can* send it in stream, but the risks you accept are A) the client may not be listening when they're sent, and/or B) those packets are lost/corrupted en-route (assuming you're using UDP as a transport). It's just that simple.<br>
</div></div>