Thanks - in the meantime the change will be getting plenty of testing
here; I'll let you know if we experience any problems with it.
From: live-devel-boun...@ns.live555.com
[mailto:live-devel-boun...@ns.live555.com] On Behalf Of Ross Finlayson
Sent: Monday, April 01, 2013 9:47 PM
To: LIVE555 St
Thanks for the reply. I actually made that change about a year ago; I
was aware that the code was already calculating presentation time for
the purpose of synchronization, but for some reason I thought it was
just a relative presentation time, not an absolute one that accurately
reflected the time
Thanks for the suggestion. I'll likely make this optimization (or something
like it) in a future release of the software, though I first need to think
through it a bit, to make sure there are no unforeseen consequences of not
returning to the event loop after each byte read.
Ross Finlayson
Liv
My apologies, I accidentally left in an unused variable declaration that
I was using for debug purposes. Amended patch attached.
From: live-devel-boun...@ns.live555.com
[mailto:live-devel-boun...@ns.live555.com] On Behalf Of Colin Caughie
Sent: Monday, April 01, 2013 4:46 PM
To: live-de...@n
> The attached patch allows access to the last received sender report RTP
> timestamp, making it possible to get the full NTP/RTP time mapping currently
> in effect (since it was already possible to get the last received NTP
> timestamp).
>
> This information can be used to calculate the wallc
When an application is receiving data on some but not all of the streams
in an interleaved RTSP session (i.e. it isn't calling getNextFrame() for
some of the streams), the streams that are not being received consume an
enormous amount of CPU cycles compared to the streams that are being
processed.
The attached patch allows access to the last received sender report RTP
timestamp, making it possible to get the full NTP/RTP time mapping
currently in effect (since it was already possible to get the last
received NTP timestamp).
This information can be used to calculate the wallclock timestam
