All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
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 19:49:51 +0100	[thread overview]
Message-ID: <s5hzneuj0ds.wl@alsa2.suse.de> (raw)
In-Reply-To: <200311171918.54453.pwk.linuxfan@gmx.de>

At Mon, 17 Nov 2003 19:18:49 +0100,
Peter Kirk wrote:
> 
> WARNING: Unsanitized content follows.
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Am Montag, 17. November 2003 15:33 schrieb Takashi Iwai:
> > At Mon, 17 Nov 2003 14:34:14 +0100,
> >
> > Peter Kirk wrote:
> > > WARNING: Unsanitized content follows.
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > > Hash: SHA1
> > >
> > > Am Montag, 17. November 2003 11:32 schrieb Takashi Iwai:
> > > > At Mon, 17 Nov 2003 01:37:02 +0000,
> > > >
> > > > Mark Hubbard wrote:
> > > > > On Friday 14 Nov 2003 15:31, Takashi Iwai wrote:
> > > > > > At Fri, 14 Nov 2003 15:11:22 +0000, Mark Hubbard wrote:
> > > > > > > On Friday 14 Nov 2003 13:20, Takashi Iwai wrote:
> > > > > > > > as a future plan, we'll define dmix as default for el-cheapo
> > > > > > > > soundcards, but e.g. not for sb live, which supports such a
> > > > > > > > function on hardware.
> > > >
> > > > ok, let me correct:  which users most likely want as dmix plugin :)
> > >
> > > Hmmm,
> > >
> > > sorry if I cant realy follow your reasoning. I have understood that using
> > > dmix on every device is stupid - since some applications like jack want
> > > low level access to the hardware. But these applications should use the
> > > hw: device, if I understand everything right. If this is so, you have yet
> > > to come up for any reason why a user would NOT want a smartdmix running
> > > behind devices like "default" "rear" front" (and all others that I dont
> > > know about, but that are consumer application devices) ?
> > >
> > > Please enlighten me on this.
> >
> > i personally think using dmix would be nice even for such "high-end"
> > cards.  but the smart dmix can still result in resampling or format
> > conversion if the first and the second applications use different
> > sample rates or formats.  in the case of cheap soundcards, it's not a
> > big problem because the quality is anyway cheap, too.  however, in the
> > case of high-end cards, people might not like that it happens.
> 
> if I understand it right, then "high-end" cards should be able to play 
> multiple streams in hardware...meaning the smart dmix wouldnt even do 
> anything else than pass on the streams to the soundcard (no resampling, no 
> mixing, no nothing). Only if you play two streams on a soundcard that can 
> only handle playing one, then it would mix (and resample if necessary for the 
> mixing).

well, my concern is that with the high-end cards, people tend to stick
with the quality of sounds.  that means, any reason to reduce the
quality wouldn't be acceptable for some people.  since dmix will do it
silently (if needed), it might be unacceptable.

anyway, it's just a concern.  the answer for this question would be
just a questionary to users (and a good documentation or user-friendly
GUI tool to configure).


Takashi


-------------------------------------------------------
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 18:49 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
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 [this message]
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=s5hzneuj0ds.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --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.