OK, I think I figured out the problem, and have installed a new
version (2010.11.10) of the "LIVE555 Streaming Media" code that
should, I think, fix it. (Note that this was a problem only with the
"openRTSP" application, not with our RTSP client code in general.)
--
Ross Finlayson
Live Networ
Dear Ross,
> Does the crash still happen if you omit the "-Q" option?
I need to check that. I'll give you some feedback soon.
> Can you post a (publically-accessible) "rtsp://" URL of a stream that
> illustrates the problem?
Unfortunately, the streaming server is not publically-accessible.
I ca
Thanks for the report.
Does the crash still happen if you omit the "-Q" option?
Can you post a (publically-accessible) "rtsp://" URL of a stream that
illustrates the problem?
--
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
___
live-dev
Dear All,
When launching the following command OpenRTSP.exe -Q -d 15 , the
OpenRTSP application
get crash every time I get the following protocol sequence at the end of the
streaming session
client -> serveur RSTP TEARDOWN
serveur -> client RTP
serveur -> client RTP
serveur -> client
Hi Ross,
many thanks for your quick feedback.
Currently I'm using Kasenna MediaBase RTSP server, but sigh, my evaluation
license has expired few days ago and I'm waiting for instructions on how to
renew it! So at the moment I cannot tell you what the server answers, but if you
have experience on
I use live555 version from 2007 year, distributed by
Appro Technology(c) with wis-streamer.
Sorry, but absolutely no support is given for old versions of the software.
(And for the second (and last) time: You should be looking only at
"presentation times", not "RTP timestamps". Our software c
Dear Mr. Ross Finlayson!
I'm very glad for your detail explanation, but RTP timestamp is really
changed.
I print timestamp value into MultiFramedRTPSink::setTimestamp() after call
of convertToRTPTimestamp().
Saw that printed value "jumped" once after the second instance of VLC player
connected to s
The conversion from presentation time to RTP timestamp (in the server
code), and from RTP timestamp to presentation time (in the client
code) happens automatically, and is not something that you should
concern yourself with. As a (server or client) developer, you need
concern yourself only wit
Der Sir!
I'm works with live555 to stream H264 encoded video, via RTP.
I have found not clear functionality in your code and I will be grateful if
you explain to me.
When secondary client connected to same stream I saw "jump" into RTP
timestamp in first stream.
I have seen a code and to me functio
