From: Takashi Iwai <tiwai@suse.de>
To: Paul Davis <paul@linuxaudiosystems.com>
Cc: Ove Kaaven <ovek@transgaming.com>, alsa-devel@lists.sourceforge.net
Subject: Re: PCM hw mixing with volume
Date: Tue, 09 Mar 2004 15:59:33 +0100 [thread overview]
Message-ID: <s5hn06qukve.wl@alsa2.suse.de> (raw)
In-Reply-To: <200403091426.i29EQv9o016723@dhin.linuxaudiosystems.com>
At Tue, 09 Mar 2004 09:26:56 -0500,
Paul Davis wrote:
>
> >And by that time, games will be even more demanding than before, and
> >still want to use those cycles for itself rather than software sound
> >processing, so just sitting idle waiting for the ultimate
> >infinite-megahertz cpu, that can do everything in no time, gains nobody
> >anything... at least our business won't.
>
> but don't you also want to be able to sell as many copies as possible
> to as many satisfied customers as possible? if so, you have to pay
> attention to whatever standards can be found for the domain at
> hand. in this case, the AC97 codec spec (and its recent successor
> whose name i forget) is about the most relevant thing i can think
> of. AFAIK, AC97 etc. say nothing about the kinds of gain control and
> mix routing that exist for multiple PCM streams. ergo, there is no
> standard way to do this that will work across a significant fraction
> of the installed and/or potential user base.
BTW, the USB audio is another headache.
the current ALSA PCM model isn't perfectly suitable for the devices
like USB audio. (well, the current JACK implementation has the same
problem, too ;)
just an off-topic here, though...
> so, either ALSA can come up with such a thing, which might be
> interesting but the manpower available to work on it is very limited,
> or parties that have a vested interest in it can use an existing API
> (SDL springs to mind, though i've never looked at it) or develop a new
> one that provides a standard mechanism for doing wat you want.
>
> i mean, even at the most basic level, the audio interface that is
> built into my laptop motherboard (some intel nonsense) cannot do any
> sample rate other than 48kHz! this is a high end laptop (HP Pavilion
> zd7000, 3GHz processor, 1440x900 display, etc) ... think of the cycles
> that will be spent *resampling* your audio independently of the mixing
> step. this type of BS seems to be growing more and more common. if i
> was in your position (specifically, if i have to assume that my user
> base spent a (comparatively) lot of money on a graphics card, maybe
> even paid for a 5.1 speaker setup, but are still using the
> factory-provided audio interface, i would assume the absolute worst
> capabilities for that interface that i could: single sample rate,
> single PCM stream, no mixer.
>
> and btw, i wasn't suggesting that you just "sit there waiting". my
> point was that the time you might spend working on this could be spent
> working on something else, and by the time you're done, CPU speed
> increases will have done this particular task for you.
i guess that the special implementation for sb live! would be
relatively easy once when the API is defined. it's nothing but a
reduced version of PCM streams, so the h/w control is already in the
driver.
the most difficult part is the definition of the (somehow) generic but
effective API. the same is true for 3D audio API.
it'd be appreciated if app developers have a concrete wish list of API
design about these stuffs, or even better a proposal of the API.
Takashi
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
next prev parent reply other threads:[~2004-03-09 14:59 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-07 14:51 PCM hw mixing with volume Ove Kaaven
2004-03-07 16:36 ` Manuel Jander
2004-03-07 16:41 ` Jaroslav Kysela
2004-03-08 16:20 ` Paul Davis
2004-03-08 21:29 ` Ove Kaaven
2004-03-09 14:26 ` Paul Davis
2004-03-09 14:59 ` Takashi Iwai [this message]
2004-03-09 17:31 ` USB audio devices Jaroslav Kysela
2004-03-10 8:26 ` Clemens Ladisch
2004-03-10 9:08 ` Jaroslav Kysela
2004-03-10 9:41 ` Takashi Iwai
2004-03-10 20:04 ` Karsten Wiese
2004-03-11 0:13 ` Patrick Shirkey
2004-03-11 8:09 ` Clemens Ladisch
2004-03-10 9:41 ` Clemens Ladisch
2004-03-10 16:34 ` Takashi Iwai
2004-03-10 17:46 ` Clemens Ladisch
2004-03-11 8:14 ` Clemens Ladisch
2004-03-09 17:25 ` PCM hw mixing with volume Ove Kaaven
2004-03-09 20:24 ` Manuel Jander
2004-03-10 9:46 ` Giuliano Pochini
2004-03-10 14:16 ` Ove Kaaven
2004-03-10 14:40 ` Ove Kaaven
2004-03-10 14:53 ` Paul Davis
2004-03-10 15:08 ` Takashi Iwai
2004-03-10 16:05 ` Ove Kaaven
2004-03-10 15:55 ` Giuliano Pochini
2004-03-10 16:56 ` Ove Kaaven
2004-03-11 9:24 ` Giuliano Pochini
2004-03-10 17:28 ` Takashi Iwai
2004-03-10 18:47 ` James Courtier-Dutton
2004-03-11 5:15 ` Manuel Jander
2004-03-11 7:13 ` snd_intel8x0 fails after ACPI sleep gte654n
2004-03-13 18:13 ` Christoph Lukas
2004-03-11 5:00 ` PCM hw mixing with volume Manuel Jander
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=s5hn06qukve.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=ovek@transgaming.com \
--cc=paul@linuxaudiosystems.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.