All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brendan Pike <spike@spykes.net>
To: alsa-devel@alsa-project.org
Subject: Re: Software mixer at kernel level
Date: Tue, 10 Feb 2009 01:50:54 -0500	[thread overview]
Message-ID: <20090210015054.24a5f522@darius> (raw)
In-Reply-To: <4990FB35.8050205@cox.net>

Sean McNamara wrote:
> 
> You are welcome to do whatever you want on your system, but don't assume that everyone wants what you want.
> </rant>
> _______________________________________________


Or you could just avoid all this mess with Linux audio for the time
being and use a hardware mixing device instead. I realize laptop users
are going to bitchslap me for saying that but its true.

The whole buggy software mixing situation with regards to applications
not working correctly or as intended is frustrating. OSS4 does it at
the kernel level because it tries to be transparent to all the
applications which think the device has hardware mixing capabilities. I
realize OSS4 can be buggy for some but its implementation is far more
compatible instead of the cocktail of sound servers and software
mixing routines we have in ALSA right now.

Some apps out there require direct access to /dev/dsp or whatever, what
are we going to do? Hope somebody updates the program? (usually not
going to happen with older closed source games or whatnot). Take UT99
for example, rarely does this ever work with any software mixing period.

  parent reply	other threads:[~2009-02-10  6:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-10  2:02 Software mixer at kernel level Mauricio Nuñez
2009-02-10  2:27 ` Sean McNamara
2009-02-10  3:57   ` stan
2009-02-10  5:00     ` Sean McNamara
2009-02-10 16:33       ` stan
2009-02-10  6:50     ` Brendan Pike [this message]
2009-02-10  8:10       ` Takashi Iwai
2009-02-10 20:47     ` Colin Guthrie
2009-02-10  2:51 ` Lee Revell

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=20090210015054.24a5f522@darius \
    --to=spike@spykes.net \
    --cc=alsa-devel@alsa-project.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.