W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2017

Re: Planning for TPAC

From: Alastair Campbell <acampbell@nomensa.com>
Date: Wed, 5 Apr 2017 08:10:06 +0000
To: "tink@tink.uk" <tink@tink.uk>, Olli Pettay <olli@pettay.fi>, "public-webapps@w3.org" <public-webapps@w3.org>
Message-ID: <1D5B562F-44A0-4C49-A8F4-F994F88FD46F@nomensa.com>
Léonie Watson wrote:
> We'd need to think about how it was setup at TPAC itself. Lots of people 
> all video conferencing would be a bandwidth killer - but perhaps one 
> machine in the meeting room, with the camera pointed into the room would 
>  suffice?
  
We’ve been experimenting with various setups in our meeting rooms as our clients all use different systems (Google hangouts, Skype, Webex, gotomeeting etc). 

The on-screen content is fairly easy with each of those, the key thing seems to be having one source of audio input & output.

I.e. one computer that the microphone goes into, and the speakers come out of. Partly to prevent feedback loops, but also because all the software systems try to nullify your own input to prevent echo, which means you want the speakers & mic very close (like on a laptop with no external mic/speaker). Otherwise the audio cuts out from the external person’s point of view.

Our most successful setup so far is to have a TV which does audio out, a webcam hooked on the top of the TV that does the audio in, and a laptop taking the HDMI and USB inputs. That’s good for a small room, but because it is at one end of the room the audio input suffers when people are sat more than 4m away.

Another option is a speaker/mic combo which you can put in the middle of the room. There are various devices aimed at conferencing, they tend to be expensive. When travelling I use a Fugoo speaker, good input/output, 40 hour battery life, USB charging. It does use Bluetooth though, so for anything like that, don’t pair the laptop with any other audio devices (like headphones) or it might switch when they come into range.

HTH,

-Alastair

Received on Wednesday, 5 April 2017 08:10:42 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:27:42 UTC