From: stan <ghjeold_i_mwee@cox.net>
To: Sean McNamara <smcnam@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Software mixer at kernel level
Date: Mon, 09 Feb 2009 20:57:41 -0700 [thread overview]
Message-ID: <4990FB35.8050205@cox.net> (raw)
In-Reply-To: <74eb1fe20902091827w7f6020e2r58f0ba27f651de1f@mail.gmail.com>
Sean McNamara wrote:
> Hi,
>
>
> However, the point about "everybody needs it" is a valid one. If I had
> my druthers, it would be impossible for anyone in usermode to
> initialize an ALSA pcm in a mode which does not provide software
> mixing. We can still provide the software mixing in usermode, but my
> reasoning is that
>
<rant>
I disagree. I have one of those applications that doesn't do softwae mixing, deliberately because I want it to have
good sound (it's a brainwave entrainment app). It calls functions in alsa that *can't* be accessed through pulse, and
allows users to set the frame rate to any hardware rate their card supports (in pulse, one size fits all).
Pulse is great for those who want its functionality, and I would love to see it replace dmix in alsa so that when it
received a request for a function it doesn't support it would have the ability to step aside and allow the application
to take over the sound device.
Linux is about freedom, and I think you are wanting to restrict that freedom for me to use my hardware the way I want.
If you want to put a switch in place that does that, but allows it to be turned off, great, but not hard wired to only
behave a single way. Wait! We already have such a switch, it's called /home/.asoundrc.
You are welcome to do whatever you want on your system, but don't assume that everyone wants what you want.
</rant>
next prev parent reply other threads:[~2009-02-10 3:57 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 [this message]
2009-02-10 5:00 ` Sean McNamara
2009-02-10 16:33 ` stan
2009-02-10 6:50 ` Brendan Pike
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=4990FB35.8050205@cox.net \
--to=ghjeold_i_mwee@cox.net \
--cc=alsa-devel@alsa-project.org \
--cc=smcnam@gmail.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 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.