From: Paul Davis <paul@linuxaudiosystems.com>
To: Peter Kirk <pwk.linuxfan@gmx.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: smart and automatic use of dmix and dsnoop - feature suggestion.
Date: Fri, 14 Nov 2003 07:21:52 -0500 [thread overview]
Message-ID: <200311141221.hAECLqlT003018@oud.linuxaudiosystems.com> (raw)
In-Reply-To: Your message of "Fri, 14 Nov 2003 02:43:37 +0100." <200311140246.14873.pwk.linuxfan@gmx.de>
>So, these are two numbers - and basicly all is fine as long as you dont wan=
>t=20
>to excede them, but if you do, you need to use dmix or dsnoop. Why not use=
>=20
>dmix and dsnoop automaticly when necessary ? Wouldnt it be possible to have=
because it would be catastrophic, or, well, at least very bad, for
applications that want to "sit close to the metal".
this is a user-space configuration issue, not something that alsa-lib
should do by default. if the user (or the distributor) defines "dmix"
to be the default device type, then every conformant ALSA application
will do the right thing. apps like JACK that want to "site close to
the metal" will still use "hw:N" unless you tell it otherwise, but
consumer apps will use "default" (that's what i mean by conformant)
and get dmix behaviour.
--p
-------------------------------------------------------
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn firsthand the latest
developments in Apache, PHP, Perl, XML, Java, MySQL,
WebDAV, and more! http://www.apachecon.com/
next prev parent reply other threads:[~2003-11-14 12:21 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-14 1:43 smart and automatic use of dmix and dsnoop - feature suggestion Peter Kirk
2003-11-14 12:21 ` Paul Davis [this message]
2003-11-14 13:01 ` Peter Kirk
2003-11-14 13:20 ` Takashi Iwai
2003-11-14 15:11 ` Mark Hubbard
2003-11-14 15:31 ` Takashi Iwai
2003-11-15 2:46 ` Peter Kirk
2003-11-17 1:37 ` Mark Hubbard
2003-11-17 9:56 ` Frank Barknecht
2003-11-17 10:32 ` Takashi Iwai
[not found] ` <200311171434.50285.pwk.linuxfan@gmx.de>
2003-11-17 14:33 ` Takashi Iwai
2003-11-17 17:16 ` Mark Hubbard
2003-11-17 18:23 ` Peter Kirk
2003-11-17 18:50 ` Jaroslav Kysela
2003-11-17 19:08 ` Peter Kirk
2003-11-17 19:36 ` Paul Davis
2003-11-17 20:05 ` Jaroslav Kysela
2003-11-17 20:28 ` Peter Kirk
2003-11-17 21:58 ` James Courtier-Dutton
2003-11-18 5:51 ` Peter Kirk
2003-11-18 7:30 ` Paul Davis
2003-11-17 20:32 ` Paul Davis
2003-11-17 18:18 ` Peter Kirk
2003-11-17 18:49 ` Takashi Iwai
2003-11-17 19:16 ` Peter Kirk
2003-11-17 19:40 ` Paul Davis
2003-11-17 19:48 ` Peter Kirk
2003-11-17 20:34 ` Paul Davis
2003-11-17 20:04 ` Florian Schmidt
2003-11-17 18:30 ` Peter Kirk
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=200311141221.hAECLqlT003018@oud.linuxaudiosystems.com \
--to=paul@linuxaudiosystems.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=pwk.linuxfan@gmx.de \
/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.