From: David Markey <admin@dmarkey.com>
To: xen-devel@lists.xensource.com
Subject: Re: XCP Community Call #2 / confcall audio problems
Date: Fri, 9 Jul 2010 15:56:02 +0100 [thread overview]
Message-ID: <AANLkTilQTHTEyeQepbdwGSoajH5y1gr1DblzPUcwzozd@mail.gmail.com> (raw)
In-Reply-To: <4FA716B1526C7C4DB0375C6DADBC4EA37ACFC7A571@LONPMAILBOX01.citrite.net>
[-- Attachment #1.1: Type: text/plain, Size: 1634 bytes --]
Can I suggest a Gotomeeting for future meetings?
It would be good for the slides, etc also.
2010/7/9 Ian Pratt <Ian.Pratt@eu.citrix.com>
> > > I guess the confcall audio is fine for UK people,
> > > but it is and has been really horrible for me..
> > >
> > > Basicly huge amount of echo, and I can hear like 1/3 of every word,
> > > so it's really difficult to hear/understand anything from the
> confcall..
> > >
> > > I tried muting myself, but that didn't help much.
> > > Other people were complaining (on irc) about the same problem..
> > >
> > > Dunno if there's anything that could be done to fix it..
> >
> > We had an similar experience in Japan.
> >
> > I wonder if its a microphone issue. I can visualise a bunch of people
> > sitting
> > around a table, with a conn-call device in the middle, but people not
> > paying much attention to facing it when they speak.
> >
> > In any case, I managed to make out perhaps 1/2 of the second half of the
> > meeting, which was a vast improvement on what I could hear for the first
> > half.
>
> Sorry to hear the audio quality was poor. The BT bridge is obviously
> struggling with so many people dialled in. Perhaps next time we could try
> with folk explicitly muting their line on the bridge when not talking using
> *6 (repeat to un-mute) -- this works better than simply muting the handset.
>
> We also need to remind folks who are using speaker phones to get close to
> the phone before talking.
>
> Thanks,
> Ian
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>
[-- Attachment #1.2: Type: text/html, Size: 2298 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-07-09 14:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-06 15:57 XCP Community Call #2 Stephen Spector
2010-07-07 12:25 ` Dave Scott
[not found] ` <652FFB2C8F91E3428799B1FFF8B490C9857C25CFB1-7ismNY5x4TfeU4JHVX8hdHnr0TU713UqXqFh9Ls21Oc@public.gmane.org>
2010-07-07 13:42 ` [Xen-devel] XCP Community Call #2 / confcall audio problems Pasi Kärkkäinen
2010-07-09 8:42 ` Simon Horman
[not found] ` <20100709084251.GG24576-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
2010-07-09 14:42 ` [Xen-devel] " Ian Pratt
2010-07-09 14:56 ` David Markey [this message]
2010-07-14 16:19 ` Jonathan Knowles
2010-07-14 17:09 ` David Markey
[not found] ` <AANLkTinYS5fnQMDtEWPNq_KcYGgviRUtpgzXEX7Nwog4-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-07-15 2:28 ` [Xen-devel] " Todd Deshane
2010-07-10 0:05 ` Simon Horman
[not found] ` <AANLkTilSDTdMYMyw9DWLamPOgE9Rh_cCqv6uzNcgRlXm@mail.gmail.com>
2010-07-10 0:04 ` Simon Horman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTilQTHTEyeQepbdwGSoajH5y1gr1DblzPUcwzozd@mail.gmail.com \
--to=admin@dmarkey.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).