Hi Guga,
Good job! Pretty cool to see H.264 working on BigBlueButton! :)
I've done some analysis on the delay among BigBlueButton 0.8 and the current master branch with H.264 enabled. The 0.8 version is running in a dedicate server in the local network, while the development version is running in a virtual machine. I've attached an image to illustrate how I did measure the end-to-end delay. A webcam is pointed to the stopwatch, and the remote video (the stopwatch image which goes to the server and comes back) is captured as well. From this configuration I've got some snapshots (5 from h.264 and 11 from h.263).
The result is that the average delay on H.263 was 202ms, while on H.264 the result was 1334ms. It means that the video delay increases more than 1 second when using H.264. The increase of delay will result in a bad experience related to the lip sync, since BigBlueButton doesn't implement any synchronization mechanism between voice and video.
Of course, the H.264 parametrization was the default one, so maybe there are parameters to be tuned. I just would like to start this conversation on how to reduce the delay.
About the bandwidth, I've done a quick experiment using the webcam pointed to the stopwatch (so the image is changing all the time), and the resolution used was 320x240. The bandwidth measured was as follows:
H.263 => 220Kb/s (Kilobits)
H.264 => 100Kb/s (Kilobits)
Great reduce of bandwidth, and probably a better image quality. Let's do some effort now to reduce the delay. :)
That's it. Best regards,
--
Felipe Cecagno Mconf Development Team