> However the problem is that in both samples, we have listening UDP sockets on
> the client side.
Don't worry. Those (2) sockets are created, but if you're receiving the
RTP/RTCP packets over TCP (either over the RTSP/TCP connection, or over a
RTSP/HTTP/TCP connection) then those sockets are
Hi Ross;
We are have tried both the openRTSP, and testRTSPClient samples.
We are tunnelling over HTTP. Both samples work – we receive video and can
display it.
However the problem is that in both samples, we have listening UDP sockets on
the client side.
The whole idea of tunnelling over HTT
> I use their tool in my projects (a modified version). They're talking about
> streaming the MP4 *file*, or im wrong?
Yes, you're wrong. They're not streaming 'the file'; they're streaming data
that's extracted from the file. (The 'hint track' hack (which, BTW, is one of
the parts of the MP4
>From GPAC developpers:
"
In short, MP4Box can be used:
- for attaching metadata to individual streams or to the whole ISO file to
produce MPEG-21 compliant or hybrid MPEG-4/MPEG-21 files
- and packaging and tagging the result for streaming, download and playback on
different devices (e.g. phone
> From Matroska developpers:
>
> "Live streaming is the equivalent of TV broadcasting on the internet. There
> are 2 families of servers for that. The RTP/RTSP ones and the HTTP servers.
> Matroska is not meant to be used over RTP. RTP already has timing and channel
> mechanisms that would was
> it's pocible to use Live555 RTSP Proxy to proxy from HTTP Unicast to RTSP
> (UNICAST)?
No, because the "LIVE555 Proxy Server" code assumes that the 'back-end' stream
is accessed via RTSP.
However, it should be straightforward to write a RTSP server (a regular RTSP
server; not a proxy server)
