[Live-devel] RTP Extension

Yedidia Amit amit.yedidia at elbitsystems.com
Thu Oct 30 02:11:49 PDT 2008


I mean to RTP Header Extension. and thank you for your answer.
 
what I am trying to do is adding meta data per frame to a H264 RFC3984
stream.
another way which cross my mind is to put this meta data in NAL with
unspecified NAL type (24-31).
But I need it to interop with clients which dont support my meta data.
(they just need to ignore this data)
Do you think it will do the job?
 

Regards,


Amit Yedidia

Elbit System Ltd.

Email: amit.yedidia at elbitsystems.com

Tel: 972-4-8318905

----------------------------------------------------------

 


________________________________

	From: live-devel-bounces at ns.live555.com
[mailto:live-devel-bounces at ns.live555.com] On Behalf Of Ross Finlayson
	Sent: Thursday, October 30, 2008 10:47 AM
	To: LIVE555 Streaming Media - development & use
	Subject: Re: [Live-devel] RTP Extension
	
	

		What is the proper way to imlement adding RTP extension
in Live555?


	it depends what you mean by "RTP extension".

	If you're referring to just implementing a new RTP payload
format, then this is easy - just define and implement your own
subclasses of "MultiFramedRTPSink" (for sending) and
"MultiFramedRTPSource" (for receiving).

	If, however, you're referring to implementing RTP *header*
extensions (as defined in RFC 3550, section 5.3.1), then there's
currently no clean way to do this; instead, you would need to modify the
existing "MultiFramedRTPS*.cpp" code to support this.
	-- 

	Ross Finlayson
	Live Networks, Inc.
	http://www.live555.com/


The information in this e-mail transmission contains proprietary and business 
sensitive information.  Unauthorized interception of this e-mail may constitute 
a violation of law. If you are not the intended recipient, you are hereby 
notified that any review, dissemination, distribution or duplication of this 
communication is strictly prohibited. You are also asked to contact the sender 
by reply email and immediately destroy all copies of the original message.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20081030/96e194b1/attachment.html>


More information about the live-devel mailing list