Thanks for the note. This has been fixed in the latest version of software
(2013.02.27), released today.
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailm
> I noticed that after a seek, the first TS packet from live555 server,
> does not have the correct continuity counter value (with respect to the
> last packet before the seek). There is a discontinuity.
> This is error is reported in VLC and wireshark.
Mumble... When streaming from a Transport S
On Feb 23, 2013, at 10:04 AM, Sébastien Escudier
wrote:
> Another solution would be to modify your server to return the actual npt
> in the PLAY response.
Sorry for the delay in responding to this. Yes, you're right - this is
actually the best solution (because it's the server, not the clien
> Can you tell whats the issue.
No, because you haven't provided nearly enough information. First, you need to
make sure that your 'back-end' RTSP server - not just the proxy server - is
using an up-to-date version of our software. Then, you will need to run the
proxy server with the -V (that
Hello Developers,
I am new to your software.
I was using proxy server for receiving stream from the
"testOnDemandRTSPServer",
While using the stream that we receive from the proxy server i saw the
following messages on the proxy server console:-
Sending request: GET_PARAMETER
rtsp://192.158.15.1
> I am trying to see how to propagate a timestamp between an RTSP server and a
> RTSP client.
Your question makes no sense, because the things that get 'propagated' from
servers to clients are *presentation times*. (RTP timestamps are used only
internally, by the RTP/RTCP protocol, as a mechan
Hi Ross,
I am trying to see how to propagate a timestamp between an RTSP server and a
RTSP client.
One aspect involve the RTCP SR, but this information is send less often than
the RTP, so the first frames are not synchronized.
I saw that the rtptime return by the PLAY is compute
Hi Ross,
just to inform you that if "Transport:" line is missing in Server Setup
Response, Live crashes (RTSPClient::parseTransportParams() does not
accept NULL paramStr)
(yes this line is required, it's just for more safety...)
Regards,
E. HEURTEL
___
