From: Peter Kirk <pwk.linuxfan@gmx.de>
To: Mark Hubbard <mark@egghead.free-online.co.uk>,
Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: smart and automatic use of dmix and dsnoop - feature suggestion.
Date: Mon, 17 Nov 2003 19:23:54 +0100 [thread overview]
Message-ID: <200311171924.40388.pwk.linuxfan@gmx.de> (raw)
In-Reply-To: <200311171716.35418.mark@egghead.free-online.co.uk>
WARNING: Unsanitized content follows.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am Montag, 17. November 2003 18:16 schrieb Mark Hubbard:
> Peter Kirk has an important point. Default dmix ("smart" could be a
> misnomer) will only work as the default pcm, therefore if one application
> is set-up to use surround51 and another set-up to use default, then nothing
> is going to be mixed. It would be better, for the sake of simplicity and
> ALSA's target user, to abandon the various pcm definitions and only use
> default which would work with all set-ups....I believe this is what Peter
> means by "smart".
Well,
no smart dmix is no "misnomer". What I mean with it is: a implementation of
dmix that only starts to mix if there is a need to do it - as long as the
soundcard can handle streams without mixing the smart dmix will not do
anything, except pass untouched streams to the hardware...when the first
stream that would exceed hardware limitation is sent to the sound device,
smart dmix would start mixing this stream into one of the existing ones.
You name a device I didnt know... "surround51". But, since this is what I call
a "consumer app device", smart dmix would lure behind that too, and apply
mixing magic if necessary.
Peter
- --
Don't vote -- it only encourages them!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQE/uRI6g2ieGvTmHiURAuJaAKCR3AR0xOCmTkC8sOig3kDkXgjB3gCeOtiD
Kp2fH2zKr+oLw3YAEECud9A=
=oGcT
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF. Net email is sponsored by: GoToMyPC
GoToMyPC is the fast, easy and secure way to access your computer from
any Web browser or wireless device. Click here to Try it Free!
https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl
next prev parent reply other threads:[~2003-11-17 18:23 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
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 [this message]
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=200311171924.40388.pwk.linuxfan@gmx.de \
--to=pwk.linuxfan@gmx.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=mark@egghead.free-online.co.uk \
--cc=tiwai@suse.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.