I realized that there is semi-documented support for manually getting ping
times via RTSP, by sending an empty GET_PARAMETERS command. The round-trip
latency can be measured from the response time. Apparently this is
problematic on certain servers, which do not respond to that command after
the P
I see - thank you. That was a bit of a sanity check. In our case, we need
to keep server-to-client latency low and predictable. Our use case is
indeed like the exception you mention, with multiple receivers in the same
'room' that need to stay synced, i.e. having similar requirements as VoIP
app
> Sorry if this is a stupid question, but I can't fully understand how
> Live555's Presentation Times are to be applied, *aside* from synchronizing
> parallel media streams.
That's correct. The presentation time indicates the time of each frame,
relative to other frames of the same media type,
Sorry if this is a stupid question, but I can't fully understand how
Live555's Presentation Times are to be applied, *aside* from synchronizing
parallel media streams. Is there any way to use these presentation times
to determine the receiver's time offset from the server? In my case, I'm
trying
