<DIV>>Alternatively, you could use (in your "createNewRTPSink" implementation) one of the alternative forms of >"H264VideoRTPSink::createNew()" that takes the SPS and PPS NAL units as parameters.  See >"liveMedia/include/H264VideoRTPSink.hh".<BR></DIV>
<DIV>     Hi, I use  the alternative forms of "H264VideoRTPSink::createNew()" that takes the SPS and PPS NAL units as parameters.Now the SDP have "a=fmtp:xx packetization-mode=1 profile-level-id=xx  sprop-parameter-sets=xx,xx",but the wireshark can't a<SPAN id=result_box lang=en class=short_text closure_uid_k6g42x="128" Tc="null" a="undefined" c="4"><SPAN closure_uid_k6g42x="309">nalysis the sprop-parameter-sets c<SPAN id=result_box lang=en class=short_text closure_uid_k6g42x="128" Tc="null" a="undefined" c="4"><SPAN closure_uid_k6g42x="351">orrect</SPAN>ly. I find that m</SPAN></SPAN></SPAN><SPAN lang=en class=short_text closure_uid_k6g42x="128" Tc="null" a="undefined" c="4"><SPAN closure_uid_k6g42x="309"><SPAN lang=en class=short_text closure_uid_k6g42x="128" Tc="null" a="undefined" c="4">y SPS's length is 122 (byte). I find other's SPS's length is shorter. Is there something wrong or the wireshark's problem??  </SPAN></SPAN></SPAN></DIV>
<DIV><SPAN lang=en class=short_text closure_uid_k6g42x="128" Tc="null" a="undefined" c="4"><SPAN closure_uid_k6g42x="309"><SPAN lang=en class=short_text closure_uid_k6g42x="128" Tc="null" a="undefined" c="4">     Thanks !</SPAN></SPAN></SPAN></DIV>