> I was thinking that RTSP would not work if the live 555 server and the
> client (viewer) are on different subnets as the client wouldn't be able
> to reach the server. [...] have
> I understood this correctly ?
No, you haven't understood this correctly - because RTSP (the control protocol)
r
Thanks Ross,
>>1/ Can LIVE555 stream H.264 or MPEG4 video to rtp://:1234 without using RTSP to set-up the stream
>Yes, (although note that the "rtp://" URL is nonstandard, and is used
only by (some) receivers - e.g., VLC - and has nothing to do with our
code). Note, though, that H.264 and MP
> Can live555 stream H.264 or MPEG4 video to rtp://:1234
> without using RTSP to set-up the stream (e.g. the client might be on a
> different subnet to the live555 server) ?
There are (from what I can tell) two different questions here:
1/ Can LIVE555 stream H.264 or MPEG4 video to rtp://:1234
> The FAQ mentions that the testMPEG4VideoStreamer program incorporates an
> RTSP server to provide the SDP description - is this why the RTP
> multicast stream is accessed using the RTSP unicast address ?
Yes.
> VLC instructions (http://www.videolan.org/doc/play-howto/en/ch04.html)
> suggest
Can live555 stream H.264 or MPEG4 video to rtp://:1234
without using RTSP to set-up the stream (e.g. the client might be on a
different subnet to the live555 server) ?
I am extending a program (a camera application running on Embedded Linux
and using live555 to serve the video streams) to add
Can I test my understanding of the testMPEG4VideoStreamer multicast
sample application and ask a question on the server media session
reference count ?
testMPEG4VideoStreamer creates an RTSP server to stream test.m4e and
reports 'Play using this stream using the URL ...'. The URL is of the
for
