From: Miles Lane <miles@megapathdsl.net>
To: Larry McVoy <lm@bitmover.com>
Cc: Randolph Bentson <bentson@grieg.holmsjoen.com>,
linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.5 Workshop RealVideo streams -- next time, please get better audio.
Date: Mon, 16 Apr 2001 20:54:03 -0700 [thread overview]
Message-ID: <3ADBBE5B.A3A3C0C@megapathdsl.net> (raw)
In-Reply-To: <3ADB922B.4DE1F9A4@megapathdsl.net> <20010416185305.B22650@grieg.holmsjoen.com> <3ADBBC99.8B389B9E@megapathdsl.net> <20010416204858.B17655@work.bitmover.com>
Larry McVoy wrote:
>
> On Mon, Apr 16, 2001 at 08:46:33PM -0700, Miles Lane wrote:
> > Randolph Bentson wrote:
> > >
> > > On Mon, Apr 16, 2001 at 05:45:31PM -0700, Miles Lane wrote:
> > > > There is one major shortcoming of the recordings.
> > > > Usually, only the comments of the presenter(s)
> > > > can be heard.
> > >
> > > I've heard of conferences where a wireless audience
> > > microphone was put inside a Nerf ball. It could
> > > then be tossed to the audience member who wished
> > > to speak.
> >
> > Alternatively, you could hold your discussion on a
> > classical music performance stage. They usually
> > have about ten or twenty suspended microphones over
> > the stage. Then, you'd just need to mix the audio.
>
> As one of the guys who was passing the mike around, I am a fan of the
> directional mike. If you have ever used one of those, they are quite
> nice and I think would solve the problem.
Are you talking about one of those "eavesdropper"
parabolic microphones? Are you thinking of having
someone on stage redirecting the microphone as
each speaker starts talking? It could work well,
but you'd either lose the first few words each
person in the audience said or need to go to a
"hand raising/acknowledgement" to create a pause
during which the microphone could be redirected.
Miles
next prev parent reply other threads:[~2001-04-17 3:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-17 0:45 Kernel 2.5 Workshop RealVideo streams -- next time, please get better audio Miles Lane
2001-04-17 0:53 ` David S. Miller
2001-04-17 1:37 ` Miles Lane
2001-04-18 0:57 ` Theodore Tso
2001-04-18 1:08 ` Miles Lane
2001-04-18 2:22 ` Joel Jaeggli
2001-04-18 2:46 ` Albert D. Cahalan
2001-04-18 11:58 ` Alan Cox
2001-04-18 15:07 ` Andrea Arcangeli
2001-04-17 1:53 ` Randolph Bentson
2001-04-17 1:56 ` Ben Ford
2001-04-17 3:43 ` Miles Lane
2001-04-17 4:47 ` Kernel 2.5 Workshop RealVideo streams -- next time, please get Albert D. Cahalan
2001-04-17 3:46 ` Kernel 2.5 Workshop RealVideo streams -- next time, please get better audio Miles Lane
2001-04-17 3:48 ` Larry McVoy
2001-04-17 3:54 ` Miles Lane [this message]
2001-04-17 3:56 ` Larry McVoy
2001-04-17 3:01 ` David Lang
2001-04-17 4:07 ` Miles Lane
2001-04-17 13:03 ` Mike A. Harris
2001-04-17 18:29 ` Kernel 2.5 Workshop RealVideo streams -- next time, please getbetter audio Miles Lane
2001-04-17 14:23 ` Kernel 2.5 Workshop RealVideo streams -- next time, please get better audio Jonathan Morton
2001-04-17 14:51 ` Kernel 2.5 Workshop RealVideo streams -- next time, please Alan Cox
2001-04-18 12:34 ` Kernel 2.5 Workshop RealVideo streams -- next time, please get better audio Eric W. Biederman
2001-04-18 12:44 ` Alan Cox
2001-04-18 18:29 ` Tim Wright
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=3ADBBE5B.A3A3C0C@megapathdsl.net \
--to=miles@megapathdsl.net \
--cc=bentson@grieg.holmsjoen.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.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