<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'>I agree, but thought perhaps we could defined list of parameters, probably based of what SimpleRTPSink uses. If people on this list have an opinion, please feel free to contribute to what the parameters could be. <BR>
<BR>
Regards,<BR>
Stuart<BR>
<BR>
<BR>
On 1/15/10 2:39 PM, "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'>>I was looking into a similar problem as the OP here. It seems that<BR>
>having the ability to add additional payload types dynamically would<BR>
>be a useful feature of the live555 library. This would be much more<BR>
>preferable than having to change the library source code to add a<BR>
>payload. I have a couple of ideas how this could be done. Would<BR>
>you be interested in reviewing a proposed patch?<BR>
<BR>
Yes, sure. Note, though, that doing this in a clean and general way<BR>
may be nontrivial, because the parameter lists for each "RTPSource"s<BR>
"createNew()" function can differ. It's going to be difficult to do<BR>
this in a generic way for all payload types; some will probably have<BR>
to remain 'hard coded'.<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>