Steve,
My answers below:
>On the receiver end:
>- You need to gather SPS and PPS from SDP once your media sub-session is
>created, which involved base64 decoding and adding a NALU start code
>(dependent on the decoder connected at the output
> of receiver
So I should write it at the beginnin
Does LIVE555 supports
1. RTP over RTSP.
Yes (client and server). (Is this not obvious from the code??)
2. RTP over RTSP over Http
Yes, but currently only for clients. (Server support for this has
not yet been completed.)
3. RTP over RTSP over https
I don't know.
if yes then how be
Does LIVE555 supports
1. RTP over RTSP.
2. RTP over RTSP over Http
3. RTP over RTSP over https
if yes then how because the "portNumBits tunnelOverHTTPPortNum" parameter
only talks about http not about https.
Regards
Deepti
Help save paper - do you need to print this email ?
This e-mail
I think I might be wrong, is the NAL unit type octet respectively :
0 11 00111 for SPS so 0x67
0 11 01000 for PPS so 0x68 ??
___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
Thanks for your reply Ganesh, I have some questions inline.
On Server:
> - SPS and PPS are used to generate sprop_parameter_sets. The 2 parameter
> sets i.e. SPS and PPS should be encoded in base-64 format with a comma
> separating the two. Do note that SPS and PPS information should not have the
