All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miles Lane <miles@megapathdsl.net>
To: "Mike A. Harris" <mharris@opensourceadvocate.org>
Cc: Larry McVoy <lm@bitmover.com>,
	Randolph Bentson <bentson@grieg.holmsjoen.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.5 Workshop RealVideo streams -- next time, please getbetter  audio.
Date: Tue, 17 Apr 2001 11:29:42 -0700	[thread overview]
Message-ID: <3ADC8B96.98C7D543@megapathdsl.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0104170902590.17111-100000@asdf.capslock.lan>

"Mike A. Harris" wrote:
> 
> On Mon, 16 Apr 2001, Miles Lane wrote:
> 
> >> hand someone a mike.
> >
> >I like this idea quite a bit.  It would probably not
> >be terribly expensive to rent/buy the required equipment,
> >it would be easy to use and would not be terribly disruptive
> >to the preceedings.
> >
> >I'm curious, didn't you find that those mikes are too
> >directionally sensitive?  I've noticed that the movement
> >of the speaker by just an inch or two can cause major
> >variations in signal reception (I've only tried that
> >little plastic parabolic eavesdropping "toy" that was
> >all the rage about two Christmasses ago -- there was one
> >floating around my office).
> 
> Just to keep this on topic... the real question is what would be
> the best way to interface this sound system into the Linux
> kernel?

This is not the topic (I don't really care how the audio
recordings get merged or how the final recording is delivered
as RealVideo/RealAudio streams).  The topic is "how do we
get recordings of Linux-related discussions in the future 
that capture all the comments of the participants."  

It would be great if we could get a good approach nailed
down so that it could be used at Linux BOF discusssions
and development team presentations in the future.

OT: It would be great to have a central repository for Linux-
related audio/video streams.  For example, it'd be great to 
get some of the LinuxTag, LinuxWorld, Comdex, CBIT and other
presentations made available on the web.  Perhaps even more
valuable, from a development information dissemination 
standpoint, would be recordings of "birds of a feather" 
discussions.

	Miles

  reply	other threads:[~2001-04-17 18:29 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
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               ` Miles Lane [this message]
2001-04-17 14:23             ` 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=3ADC8B96.98C7D543@megapathdsl.net \
    --to=miles@megapathdsl.net \
    --cc=bentson@grieg.holmsjoen.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.com \
    --cc=mharris@opensourceadvocate.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.