Thanks for the reply. When I using RTP-over-UDP streaming is no such
problem. However, when playing a stream sometimes appear friezes. I
found this same problem in mailing list (/Fri Dec 19 19:31:41 PST
2014/). I understand that change source code precludes further support,
but the proposed sol
Because your problem seems to be specific to ‘Windows 7’, I doubt that we’ll be
able to help you. Does the problem happen (on Windows 7) only with
RTP-over-TCP streaming, or does it also happen with normal RTP-over-UDP
streaming?
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
I compiled the latest (2015.02.05) source code for the client
("openRTSP") and the server ("testOnDemandRTSPServer") for Windows
platform. Then I tested applications on two Windows versions (Windows 7
and 8), start the "openRTSP" client with and without parameter "-t". On
Windows 8 everything w
Just to clarify, the message does not appear, but the error is still there.
Thanks.
2013/9/30 Francisco Feijoo
> My mistake, that message appeared yesterday before I updated both server
> an client to the latest live.2013.09.30
>
> I have re-checked now and that message does not appear any mor
My mistake, that message appeared yesterday before I updated both server an
client to the latest live.2013.09.30
I have re-checked now and that message does not appear any more.
2013/9/30 Ross Finlayson
> RTCPInstance error: Hit limit when reading incoming packet over TCP.
>> Increase "maxRTCP
> RTCPInstance error: Hit limit when reading incoming packet over TCP. Increase
> "maxRTCPPacketSize"
> MultiFramedRTPSource error: Hit limit when reading incoming packet over TCP.
> Increase MAX_PACKET_SIZE
These errors suggest that either your server (network camera?), your client, or
both, a
Hello Ross,
I want to stream over TCP different streams that have been recorder from
different cameras with live555 RTSP Server. Some are HD (H264 and MJPEG)
and the frame size can be quite big (250 kb or more). If I stream over UDP
all is working perfectly.
I need to connect from the Internet so
Dear all,
MPlayer SVN-r34578-4.5.1
FFMPEG 0.10
livem555 rev live.2012.02.03
When I play a streaming via RTSP, I found the memory will increase slowly. (
Every serveral minutes increase 0.1%)
At first the memory will use 1.0%, but it will use 14% mem after play serveral
hours.
If I play the
Yes, our server starts sending out RTP packets just before sending back the
RTSP "PLAY" response. The reason for this is that the RTSP response includes a
"RTP-Info" header, whose contents (in part) depend upon parameters obtained as
a result of starting to send out RTP packets.
But this shoul
Correct me if I'm wrong but from what I can tell taking a *quick* look
at RTSPClient::handleResponseBytes
and RTSPClient::parseResponseCode, it could be that the parsing fails
if there is an interleaved media
packet before the actual RTSP response?
On Tue, Oct 4, 2011 at 10:16 AM, Ralf Globisch
Hi Ross,
Please could you venture your expert opinion on the following:
We are streaming from a live555 RTSP server to an android version of
VLC built with live555 using RTSP over TCP.
When streaming over wifi, there are no problems.
When streaming over 3G/Edge, the VLC client never starts playin
>My question is how can I processs the RTSP while the server is
>receiving the RTCP.
Our current server implementation of RTP-over-RTSP does not handle
any RTSP commands after "PLAY". Sorry.
However, if your ciient is sending RTCP "RR" reports - which it
should be - then those will be counted
Hi,
When I use the realplayer to receive AV data from live555, I find the player
will terminate the stream after 44mins' palying(I force the realplayer to use
TCP only). I find the realplayer will send a OPTION to the server every 45
mininute, after analyzing the sniffer data:
1407 45.051016
13 matches
Mail list logo
