I have already read the various articles of comparisons of TCP vs
UDP for RTP and I understand the differences.
What I am looking for is
a. Has anyone tried the LIVE555 code running it as a server
successfully for RTP over HTTP
Do you really mean "RTP over HTTP"? Our server implementation
Hi LIVE555-ians
I have already read the various articles of comparisons of TCP vs UDP for RTP
and I understand the differences.
What I am looking for is
a. Has anyone tried the LIVE555 code running it as a server successfully for
RTP over HTTP for compressed live video (such as H.264 coming f
>I found what makes it work for me:
>
>If in the following piece of code I call readSocket WITHOUT the
>timeout parameter everything works fine again
Ah, you've discovered a bug in the code.
Instead of omitting the "&timeout" parameter, change the line
struct timeval timeout;
to
I found what makes it work for me:
If in the following piece of code I call readSocket WITHOUT the
timeout parameter everything works fine again
void SocketDescriptor::tcpReadHandler(SocketDescriptor*
socketDescriptor,
int mask) {
do {
Usage
>Interesting it seems like the MacOSX build acts different from
>the Linux build, my Linux build works exactly as you say.
>My MacOSX build does only receive RTP over UDP. When I tell it to use
>RTSP-over-HTTP tunneling (on port 80), the program finally outputs:
>...
>
>Started playin
Interesting it seems like the MacOSX build acts different from
the Linux build, my Linux build works exactly as you say.
My MacOSX build does only receive RTP over UDP. When I tell it to use
RTSP-over-HTTP tunneling (on port 80), the program finally outputs:
...
Started playing ses
>ah, that would be a live stream from the ceiling of my office:
>
>rtsp://qt2.waag.org/test.sdp
This works perfectly for me with "openRTSP" built with the latest
version (2008.02.08) of the code, using RTP/UDP, RTP/TCP ("-t"), or
RTP/HTTP ("-T 80"). I have no idea why it might not be working fo
ah, that would be a live stream from the ceiling of my office:
rtsp://qt2.waag.org/test.sdp
it should be running all day except for the moments that my computer
crashes or network hickups occur
On Apr 2, 2008, at 1:53 AM, Ross Finlayson wrote:
>> thanks for the quick reply. This option resul
>thanks for the quick reply. This option results for me in the same
>empty files. The exact same options (-t and -T 80) both work on my
>older (v2007.08.03) build of openRTSP .
>So I would say that something must have changed.
Please send us a (publically-accessible) "rtsp://" URL of a stream
t
thanks for the quick reply. This option results for me in the same
empty files. The exact same options (-t and -T 80) both work on my
older (v2007.08.03) build of openRTSP .
So I would say that something must have changed.
On Apr 1, 2008, at 11:09 AM, Ross Finlayson wrote:
>> hi,
>>
>> It se
>hi,
>
>It seems like i'm not able anymore to receive rtp over http. While an
>older build of openRTSP receives data properly, a build with the
>latest source only results in empty files (audio-MPEG4-GENERIC-1 and
>video-MP4V-ES-2) and network traffic stopping almost directly after
>the session
hi,
It seems like i'm not able anymore to receive rtp over http. While an
older build of openRTSP receives data properly, a build with the
latest source only results in empty files (audio-MPEG4-GENERIC-1 and
video-MP4V-ES-2) and network traffic stopping almost directly after
the session ha
12 matches
Mail list logo
