From: Simon Horman <horms@verge.net.au>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Stephen Spector <stephen.spector@citrix.com>,
"xen-api@lists.xensource.com" <xen-api@lists.xensource.com>
Subject: Re: XCP Community Call #2 / confcall audio problems
Date: Fri, 9 Jul 2010 17:42:54 +0900 [thread overview]
Message-ID: <20100709084251.GG24576@verge.net.au> (raw)
In-Reply-To: <20100707134208.GC17817@reaktio.net>
On Wed, Jul 07, 2010 at 04:42:08PM +0300, Pasi Kärkkäinen wrote:
> On Tue, Jul 06, 2010 at 11:57:29AM -0400, Stephen Spector wrote:
> > Tomorrow is the XCP Community Call which will be dial-up as well as IRC
> > chat, information below:
> >
> >
>
> Stephen:
>
> 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.
next prev parent reply other threads:[~2010-07-09 8:42 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 [this message]
[not found] ` <20100709084251.GG24576-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
2010-07-09 14:42 ` Ian Pratt
2010-07-09 14:56 ` David Markey
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=20100709084251.GG24576@verge.net.au \
--to=horms@verge.net.au \
--cc=pasik@iki.fi \
--cc=stephen.spector@citrix.com \
--cc=xen-api@lists.xensource.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).