Re: [103attendees] A/V in Bangkok (was: Re: [Thanks, Bangkok !)

[Ted Lemon <[e-mail]>]

At least one of the presentations was someone who had supposedly done the
meetecho prep.   The commenter whose mic didn't work probably hadn't.   I
would argue that it should be mandatory to do a mic test if you are going
to join meetecho as a possible commenter not to be punitive, but simply
because people often assume that things will Just Work, and then they don't.

On Fri, Nov 9, 2018 at 3:29 PM John C Klensin <[e-mail]> wrote:

>
>
> --On Friday, November 9, 2018 15:06 -0500 Ted Lemon
> <[e-mail]> wrote:
>
> > There were a lot of cases, particularly early on, when remote
> > presenters' audio clipped badly, making it painful to sit in
> > the room.   That seemed to improve over the course of the
> > week, but the gain on remote presenters in every single remote
> > presentation I heard was still too high, again making it
> > painful to sit in the room.
> >
> > Quite a few times when someone wanted to comment remotely they
> > couldn't, because their microphone wasn't working.   This
> > wasn't necessarily meetecho's fault in a direct way, but we
> > have to figure out how to get this right if we're serious
> > about remote participation.
>
> Ted,
>
> Very helpful.  Thanks.  Wrt the remote presenters and borrowing
> from some earlier comments from one of the Meetech team, is
> there any way to differentiate how many of those problems with
> remote presenters of whom Meetecho was notified well in advance
> and with whom they have an opportunity to test and debug (as
> they have been requesting for several years) and those who
> simply used the remote queue facilities as if they were just
> making a comment?
>
> thanks,
>    john
>
>