<HTML>
<HEAD>
<TITLE>Re: [Live-devel] How to transfer a new RTP Payload type.</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Ross,<BR>
<BR>
I was looking into a similar problem as the OP here. It seems that having the ability to add additional payload types dynamically would be a useful feature of the live555 library. This would be much more preferable than having to change the library source code to add a payload. I have a couple of ideas how this could be done. Would you be interested in reviewing a proposed patch?<BR>
<BR>
Regards,<BR>
Stuart<BR>
<BR>
<BR>
On 7/29/09 8:24 AM, "Ross Finlayson" <<a href="finlayson@live555.com">finlayson@live555.com</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>>3. My query is how can I receive that new type of metadata payload.Below is<BR>
>the method you sent me :<BR>
><BR>
>>>You would need to define and implement two new classes:<BR>
><BR>
>>>1/ A new subclass of "MultiFramedRTPSink", for sending RTP packets in<BR>
>>>the new payload format.<BR>
>>>2/ A new subclass of "MultiFramedRTPSource", for receiving RTP<BR>
> >>packets in the new payload format.<BR>
<BR>
<BR>
Sorry, I forgot to mention a 3rd thing that you need to do:<BR>
3/ Modify "MediaSubsession::initiate()" so that it recognizes the SDP<BR>
description for your payload type, and creates an appropriate<BR>
"RTPSource" subclass. For an example of how to do this, search for<BR>
"H264" in "liveMedia/MediaSession.cpp".<BR>
<BR>
--<BR>
<BR>
Ross Finlayson<BR>
Live Networks, Inc.<BR>
<a href="http://www.live555.com/">http://www.live555.com/</a><BR>
_______________________________________________<BR>
live-devel mailing list<BR>
<a href="live-devel@lists.live555.com">live-devel@lists.live555.com</a><BR>
<a href="http://lists.live555.com/mailman/listinfo/live-devel">http://lists.live555.com/mailman/listinfo/live-devel</a><BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
<BR>
This transmission is intended only for use by the intended<BR>
recipient(s). If you are not an intended recipient you should not read, disclose copy, circulate or in any other way use the information contained in this transmission. The information contained in this transmission may be confidential and/or privileged. If you have received this transmission in error, please notify the sender immediately and delete this transmission including any attachments.<BR>
</BODY>
</HTML>