From: Lee Revell <rlrevell@joe-job.com>
To: James Courtier-Dutton <James@superbug.co.uk>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Multi-seated machine.
Date: Sat, 21 Oct 2006 19:21:12 -0400 [thread overview]
Message-ID: <1161472872.20231.14.camel@mindpipe> (raw)
In-Reply-To: <453AA8C7.4050408@superbug.co.uk>
On Sun, 2006-10-22 at 00:09 +0100, James Courtier-Dutton wrote:
> Hi,
>
> As linux can now be used in a mode whereby one has one base box, and
> then multiple keyboard/mouse/screen
Is this possible OOTB on any distro? Last I heard it required kernel
and/or X patches? Got a link?
> , how might one separate the sound?
> I.e. Sound card 0 for screen 0, sound card 1 for screen 1 etc.
> Or one might want "Front" for screen 0, "Rear" for screen 1 etc.
>
> How would we achieve this in ALSA?
> I expect we would need a different asoundrc for each screen, but I don't
> know how well this might work or not.
AFAICT it should work now with Gnome and multiple soundcards as long as
each screen logs in as a separate user - gnome-soundcard-properties just
modifies the .asoundrc to set the default soundcard. If Gnome could be
made aware of this multiple-console-user mode then it seems like it
could be made plug and play...
With a single soundcard it seems like it would be very tricky and
hardware-dependent, because Front and Rear are not independent on most
devices?
Lee
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
prev parent reply other threads:[~2006-10-21 23:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-21 23:09 Multi-seated machine James Courtier-Dutton
2006-10-21 23:21 ` Lee Revell [this message]
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=1161472872.20231.14.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=James@superbug.co.uk \
--cc=alsa-devel@lists.sourceforge.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