All of lore.kernel.org
 help / color / mirror / Atom feed
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: Mon, 17 Nov 2003 14:36:31 -0500	[thread overview]
Message-ID: <200311171936.hAHJaW1B013634@oud.linuxaudiosystems.com> (raw)
In-Reply-To: Your message of "Mon, 17 Nov 2003 20:08:26 +0100." <200311172008.28812.pwk.linuxfan@gmx.de>

>what you say seems to be valid to me, but not if you implement smart dmix the
>way I said =). The way I suggested *every* application would connect to smart
>dmix, and none directly to alsa lib (except those that use devices like hw: -
>and those should never be mixed). Since every stream is connected to smart
>dmix, there is no need to *reroute* anything in the case of needed mixing.
>The only thing that has to happen, is that the new stream, that has to be
>mixed into the existing one due to hardware limitations has to be resampled
>etc. to make mixing possible.

believe or not, i actually think that peter is right here. if dmix
works well enough to be used by any application, then i think it
should be used for all non-hw accesses unless the user configures it
otherwise. if it doesn't work this well, it should :)

--p


-------------------------------------------------------
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

  reply	other threads:[~2003-11-17 19:36 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
2003-11-17 18:50                       ` Jaroslav Kysela
2003-11-17 19:08                         ` Peter Kirk
2003-11-17 19:36                           ` Paul Davis [this message]
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=200311171936.hAHJaW1B013634@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.