Measuring End To End Latency From the WebRtc client receiving the Video

[Tim McClure]

We have a low latency video architecture working through Wowza that is performing really well - I think our average latency is about 2 seconds end to end. We take the video from a device to Wowza and publish the video over WebRTC using H264. The issue we have is that although our customer is satisfied with the latency they want us to report the exact end-to-end latency on the UI. Have you had other customers who have had this requirement? If so how did they solve this issue? Are do you have any ideas? Is there a can extract the original frame the frame on the browser side using the webRTC internals API? Tim

[Sergio Garcia Murillo]

Well, 2 seconds latency is not "really well" IMHO.. ;)

Anyway, if you can measure end-to-end latency from the same physical location, best you can do is to point the camera at  clock running with milliseconds (a mobile phone with chronometer app would be enough) and take a photo with both the clock and the video of the clock.

It is quite rudimentary, I know, but it is the best and only valid true end-to-end measure I am aware of.

Best regards
Sergio

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/b70c61f9-dba0-4dbd-b6f8-601a3222a3ff%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.