mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Morton <chromi@cyberspace.org>
To: "Mike A. Harris" <mharris@opensourceadvocate.org>,
	Miles Lane <miles@megapathdsl.net>
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 get   better audio.
Date: Tue, 17 Apr 2001 15:23:48 +0100	[thread overview]
Message-ID: <l03130302b70202006529@[192.168.239.105]> (raw)
In-Reply-To: <Pine.LNX.4.33.0104170902590.17111-100000@asdf.capslock.lan>
In-Reply-To: <3ADBC170.EB7F1511@megapathdsl.net>

>>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.
>
>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?
>
>;o)

Not a problem.  :)  Simply fit a machine with several ALSA-compatible
soundcards with mic-level inputs and use it as the recording medium.
Actually, I forget - do OSS-type soundcard drivers handle multiple cards
sensibly too?

--------------------------------------------------------------
from:     Jonathan "Chromatix" Morton
mail:     chromi@cyberspace.org  (not for attachments)
big-mail: chromatix@penguinpowered.com
uni-mail: j.d.morton@lancaster.ac.uk

The key to knowledge is not to rely on people to teach you it.

Get VNC Server for Macintosh from http://www.chromatix.uklinux.net/vnc/

-----BEGIN GEEK CODE BLOCK-----
Version 3.12
GCS$/E/S dpu(!) s:- a20 C+++ UL++ P L+++ E W+ N- o? K? w--- O-- M++$ V? PS
PE- Y+ PGP++ t- 5- X- R !tv b++ DI+++ D G e+ h+ r++ y+(*)
-----END GEEK CODE BLOCK-----



  parent reply	other threads:[~2001-04-17 14:39 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-17  0:45 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               ` Kernel 2.5 Workshop RealVideo streams -- next time, please getbetter audio Miles Lane
2001-04-17 14:23             ` Jonathan Morton [this message]
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='l03130302b70202006529@[192.168.239.105]' \
    --to=chromi@cyberspace.org \
    --cc=bentson@grieg.holmsjoen.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.com \
    --cc=mharris@opensourceadvocate.org \
    --cc=miles@megapathdsl.net \
    /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

all inboxes | Powered by JetHome®