Thanks for reporting this issue. I have just installed a new version
(2017.05.24) of the “LIVE555 Streaming Media” code that should (I hope) fix
this.
(Does this also solve the problem that “libasan” reported to you?)
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
__
> I am using the latest version of Live555RtspProxy server with multiple
> cameras as inputs. However I noticed a significant problem is persistent with
> it and I just want to report it to you.
>
> After it runs for a while, the rtsp request for some cameras works and for
> others is dead unl
in RTSPClient destructor the same "socket num" (fInputSocketNum) must be
used when clearing "server request alternative byte handler"
as when setting the handler, but this socket num fInputSocketNum is
"cleared" in resetTCPSockets and in grabSocket,
so if after setting the "server request alternati
yes version 2017.04.26
On Wed, May 24, 2017 at 1:42 PM, Gerald Hansink
wrote:
>
> -- Forwarded message --
> From: Frederik De Ruyck
> Date: Wed, May 24, 2017 at 12:07 PM
> Subject: Fwd: [Live-devel] libasan detects memory access error
> To: Gerald Hansink
>
>
> Ja, versie 2017.
unless the live555RtspProxy server is relaunched. It's not a
data bandwidth problem. This is the log from ffmpeg when it happens.
Thanks.
Dashan Chang
ffmpeg started on 2017-05-24 at 06:20:31
Report written to "ffmpeg-20170524-062031.log"
Command line:
"K:\\ffmpeg\\bin\\ffmpeg.
First, please make sure that you’re using the latest version of the “LIVE555
Streaming Media” code (the only version that we support). See
http://live555.com/liveMedia/faq.html#latest-version
The part of the code that you’re referring to - for handling RTP/RTCP-over-TCP
- is very comple
hi ross,
colleague could not subscribe to the mailing list with his email address so
see below for the forwarded question.
best regards,
gerald
Hi,
three weeks ago we've started
