[Live-devel] Modifying LiveMedia RTSPServer classes to support URI parameters

[Jeff Shanab]

By rtsp you mean as a client?

The system often connects and is told by the server what it supports.  DESCRIBE,SETUP,PLAY

I am talking to security cameras and I am expecting on some cameras this info to change. I will detect this on the fly from a changed PPS and SPS. Indeed since I embed them or they are embedded in the stream it is the decoder that detects this on decode of first frame made by the [7][8][5]

-----Original Message-----
From: live-devel-bounces at ns.live555.com [mailto:live-devel-bounces at ns.live555.com] On Behalf Of Matt Schuckmannn
Sent: Tuesday, June 14, 2011 1:33 PM
To: live-devel at ns.live555.com
Subject: [Live-devel] Modifying LiveMedia RTSPServer classes to support URI parameters

Has anyone succeeded in modifying the LiveMedia classes to support accepting parameters in the URI, something like the following to request a specific height and width, bitrate, and framerate:

rtsp://media.server.com/live_video?height=320&width=400&kbps=300&fps=15

With a H.264 stream changing some of these parameters will change the SPS, and PPS and thus change the SDP. The way RTSPServer, ServerMediaSession, and OnDemandMediaSession work they all make assumptions about the media name and that the SDP will not change and key parts of each classes interfaces are not virtual so changing things appears to be difficult without changing the LiveMedia code. I just wanted to ask if anybody else has tackled this task and how it went for them.

Thanks,
Matt S.

PS I will admit that I'm still using a somewhat older version of LiveMedia, if recent changes to the library has made this task easier let me know and I'll look into updating things.



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