Alex,
Thanks for the report. Yes, this is a bug. It has been fixed in the latest
version (2015.07.31) of the “LIVE555 Streaming Media” code, released just now.
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
___
live-devel mailing list
l
Thanks for the report. This is now fixed in the latest version (2015.07.31) of
the “LIVE555 Streaming Media” code, released just now.
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
___
live-devel mailing list
live-devel@lists.live555.com
h
Craig,
Thanks for sending this. I had not seen a RTSP “SETUP” command fail like this
before. This definitely seems to be a bug in your ‘back end’ server; I wonder
how they are able to properly handle any RTSP clients at all??
In any case, I have just released a new version - 2015.07.31 - of
Hello,
In each of the the test*Receiver apps, they utilize RTCPInstance and pass
it an estimatedSessionBandwidth of 160. I realize this parameter doesn't
have to be accurate, but it should be roughly the bitrate of the stream,
right? The test*Streamer apps use an estimatedSessionBandwidth of 5000,
Hi,
Found a memory leak in class ProxyServerMediaSession. This leak grows with
more number of cameras registered to live555ProxyServer.
class PresentationTimeSessionNormalizer is derived class of Medium. So that
whenever object of class PresentationTimeSessionNormalizer is created, it
creates its
