One IETF meeting that I was "attending" remotely, I measured the audio
stream delay at about 30 seconds. I found that quite often by the time I
typed in a question into jabber to be channeled to the microphone, the
speakers were often a 2-3 issues/slides/topics beyond what my question
was related to.
The sessions that used meetecho were NOT delayed as much.
I think it would be worth investing some effort into improving the delay
on the audio stream.
Tony Hansen
On 3/11/14, 11:07 AM, Tom Pusateri wrote:
I was listening to one of the sessions through the live audio
streaming feature of the iPhone IETFers app this week while I was in
the session to just verify the streaming was working from the app.
There was about a 10 second delay between the live audio and the
streaming audio. Joel noted that in addition to audio processing and
conversion, the audio was sent from London to Washington State where
it was replicated back to London.
The delays are important to any form of remote participation. If you
want remote participants to interact with live participants, you must
keep the delay as low as possible or the live participants will give
up on the remote participants. This actually quite difficult to do
well while also scaling to reach lots of remote participants.
It will require extra audio engineering work for each location as well
as delay sensitive network testing.
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html.
https://www.ietf.org/mailman/listinfo/vmeet
