Re: [vmeet] Experience as a remote attendee

2016-04-08 Thread John Leslie
Stewart Bryant  wrote:
> 
> I attended remotely, connecting into a (one) session on pretty
> well every slot. I had one persistent technical problem:
> 
> I was using W10 + Chrome Version 49.0.2623.110 m (64-bit)
> and found that for every session I had to connect, then disconnect
> then reconnect to get the slides.

   I had the same problem on MacOS 10.10.5 and Chrome 49.0.2623.110:
almost without fail _something_ would freeze during the session.

   I tried Opera with an older version, and it seemed better until
Opera decided to update itself (without me asking, of course).

   It got decidedly worse as the week wore on; so I suspect a memory
problem; but for all I know, that may have been in the cable modem,
not the computer. (Usually, I use DSL for connectivity, and haven't
seen this kind of problem.)

   Clearly, being able to restart a substream will really help.

   Also, a couple of times Meetecho folks gave me a slides-only link
which worked well for the remainder of the session.

   By the end of the week, I was usually selecting the HTML5 audio,
and it lasted through the session. (I have many years' experience
without the slides cycling in real-time, so it no longer bothered me
to lose the slides.)

   Serious debugging _during_ IETF-week really doesn't make sense;
but we ought to do it sometime...

--
John Leslie 

___
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html.
https://www.ietf.org/mailman/listinfo/vmeet


[vmeet] getting better...

2016-04-08 Thread Hala Mowafy
I have participated on Meetecho a year ago and it was poor.
There is a definite improvement this time.  I just ran into several snags where 
chunks of the meeting froze and important pieces of the conversation were lost.

Also, it would be useful if you can add one camera focused on the room, just 
like you have one on the front with the speaker.  Helps complete the 
perspective.

But thank you for the improvements.  It is obvious.
Hala






___
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html.
https://www.ietf.org/mailman/listinfo/vmeet


Re: [vmeet] remote presenters without headsets

2016-04-08 Thread Adam Montville

> On Apr 7, 2016, at 6:42 PM, Thomas Watteyne  wrote:
> 
> +1
> 
> I've seen this over and over. I would also warn folks against iPhone-like 
> headphones with a mic on the wire. It's either too low (and the voice sounds 
> too low), or held in front of the presenters mouth, in which case the sound 
> saturates.

Is the sound different for MeetEcho than for, say, WebEx?  I work remotely and 
use my iPhone-like headphones constantly and haven’t received any complaints.

> 
> Nothing beats a headset with a proper mic-on-a-stick, or whatever you call 
> that.
> 
> I've using http://www.logitech.com/en-us/product/wireless-headset-h600 
>  for a year now, 
> works great.
> 
> Thomas
> 
> On Thu, Apr 7, 2016 at 6:15 PM, Michael Richardson  > wrote:
> 
> So there are a number of people who presented remotely who for some reason
> think that the:
> 
>   Use a headset
> 
> does not apply to them.  The audio from them was almost universally unuseable.
> 
> I also think that the chairs have not made "send slides early" clear enough.
> 
> They might as well have not bothered to present at all.
> If headsets are too expensive for some, I will buy them for people.
> 
> --
> Michael Richardson >, 
> Sandelman Software Works
>  -= IPv6 IoT consulting =-
> 
> 
> 
> 
> 
> 
> --
> ___
> 
> Thomas Watteyne, PhD
> Research Scientist & Innovator, Inria
> Sr Networking Design Eng, Linear Tech
> Founder & co-lead, UC Berkeley OpenWSN
> Co-chair, IETF 6TiSCH
> 
> www.thomaswatteyne.com 
> ___



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html.
https://www.ietf.org/mailman/listinfo/vmeet


Re: [vmeet] Suggestion

2016-04-08 Thread Dave Crocker

On 4/8/2016 10:03 AM, Ray Pelletier wrote:

I really like the idea of the chair cockpit.  For example, we could get 
Meetecho to pre-load the slides that have been loaded in to the tools site (and 
all of the associated drafts), have their laptop connected to both projectors, 
and have their laptop be the place where you navigate the decks.  The meetecho 
team was fantastically helpful this week, springing into action whenever you 
said their name in the jabber channel.  That could be made more discoverable in 
a tweaked UI.



In practical terms, this needs one person focused on running the meeting 
and a second person, sitting next to the first, running the meeting's 
integrated tech cockpit.


More generally:

 We should formulate basic operational scenarios for each relevant 
actor (chair running the meeting, chair operating the cockpit, 
presenters in the room, presenters not in the room, audience in the 
room, audience not in the room.


 And we should formulate templates for how they interact.

I think we are remarkably close to being able to make things work quite 
well.  Maybe not reaching the magical 'seamlessly', but quite well.


From my experience this week, the biggest deficiency is queue 
management.  The virtual queue, for remote participants, worked 
usefully, but have in-room folk be in a separate queue creates a 
juggling problem operationally.  Things will get far simpler if/when  we 
figure out a workable way to get in-room folk also be listed in the 
virtual queue.[*]


I suspect there is also an issue with the virtual queue, in terms of 
remote hubs, if they also have in-room microphones.


Anyhow, defining the scenarios we want to support and targeting them is 
what we should do.  And if we want this to be real for IETF 100, we'd 
better target a serious dress rehearsal for IETF 98.


d/

[*] I suspect we are also going to want two or more cameras in a room, 
so that folk can see chairs, in-room speaker, and audience-at-microphone 
simultaneously.


--

  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

___
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html.
https://www.ietf.org/mailman/listinfo/vmeet