Re: [Live-devel] The bug about StreamState::fStartNPT

2013-03-22 Thread Ross Finlayson
OK, now I understand the problem that you're reporting. (I didn't pay much attention to it before, because you use an unprofessional email address, and many of your previous comments have been bogus.) Yes, the server did have a problem computing the 'current NPT' if it received more than one c

Re: [Live-devel] The bug about StreamState::fStartNPT

2013-03-22 Thread kingaceck
> But after first call this function the value of mostRecentPresentationTime > and initialPresentationTime will be reset to zero. >No you're wrong. Those values get set to zero only when the "RTPSink" object >is created. But I see those values get set to zero when the "RTPSink" continue to play

Re: [Live-devel] The bug about StreamState::fStartNPT

2013-03-21 Thread Ross Finlayson
> But after first call this function the value of mostRecentPresentationTime > and initialPresentationTime will be reset to zero. No you're wrong. Those values get set to zero only when the "RTPSink" object is created. Ross Finlayson Live Networks, Inc. http://www.live555.com/ ___

[Live-devel] The bug about StreamState::fStartNPT

2013-03-21 Thread kingaceck
The function OnDemandServerMediaSubsession::getCurrentNPT() will return the value of the stream's NPT.But after first call this function the value of mostRecentPresentationTime and initialPresentationTime will be reset to zero.When the second call of the function It return the NPT that after fir