Hi Ross, sorry for the miss information previously, let me share my use case;

I have to send video analytics metadata related to an another video RTSP 
stream, I have to simulate onvif profile T, so need to add the metadata rtsp 
uri into the metadata onvif profile.

Current setup is a camera connected to a computer and we are doing some 
processing to the video, the text to stream will change every 1 second and is 
not longer than 200 characters.

From onvif streaming specs RTSP should conform  [RFC 2326].

 RTP shall conform [RFC 3550], [RFC 3551], [RFC 3984], [RFC 7798], [RFC 3016] 
or [RFC 3640], and JPEG over RTP

https://www.onvif.org/specs/stream/ONVIF-Streaming-Spec.pdf Refer to section 
5.1.2


Im not sure if this is the correct path, please let me know your input, I will 
appreciate a lot !

Thanks
Max

On 3 Aug 2021, at 9:35 AM, Ross Finlayson 
<finlay...@live555.com<mailto:finlay...@live555.com>> wrote:

[EXTERNAL EMAIL]

On Aug 2, 2021, at 5:55 PM, Maximiliano R. Godoy Skorin 
<mrgo...@aerospace.cwtlimited.com<mailto:mrgo...@aerospace.cwtlimited.com>> 
wrote:

Hi!

I have been trying to stream an XML file

The problem here is that - without further explanation - it doesn’t really make 
much sense to ’stream’ a XML file.  What is the kind of media (i.e., audio, 
video, text) that you want to stream, and how does it change over time?  And 
how does this media relate to the XML file?

Note also that - for each medium that you want to stream - there should be an 
IETF-defined RTP payload format for this medium, describing how this medium is 
to be packed into RTP packets.  (This should not just be something that you 
conjure up yourself.)


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


_______________________________________________
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel

_______________________________________________
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel

Reply via email to