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
Another solution would be to modify your server to return the actual npt
in the PLAY response.
Currently, when your server resume from the previous position, it does
not return any npt value in the PLAY response.
I guess both fixes would be valid.
Best regards,
Sebastien.
___
Hi Ross,
The return value of getNormalPlayTime() is false in case of a "resume"
play because in this case the value of playStartTime() is incorrect.
playStartTime() returns 0 if the stream resume from the previous
position, and then fNPT_PTS_Offset is set to the last presentation time
value.
So wh
It did resume from where it paused. I did the same test with VLC for the
client to check the video resume, and I also had the NPT reset to 0.
Here is the RTSP exchange :
Sending request: PAUSE
rtsp://192.168.1.13:8554/mpeg2TransportStreamTest/ RTSP/1.0
CSeq: 5
User-Agent: ./testRTSPClient (LIVE55
> I tried to issue a PAUSE and then a PLAY without specifying a start
> value (so it resumes from where it paused), and the return value of the
> function getNormalPlayTime() starts from 0 again. Why ?
I don't know. Please show us the RTSP protocol exchange.
(Did the media playback actually resu
