From: Glenn Maynard <g_sf@zewt.org>
To: alsa-devel@lists.sourceforge.net
Subject: Re: EMU10K1 and the extra voice
Date: Sun, 6 Jun 2004 00:54:31 -0400 [thread overview]
Message-ID: <20040606045431.GA3025@zewt.org> (raw)
In-Reply-To: <20040605125936.GA3478@lost.org.uk>
On Sat, Jun 05, 2004 at 12:59:36PM +0000, Chris Purnell wrote:
> For PCM playback the EMU10K1 driver is allocating an extra voice.
> This is somewhat wastefull and I kind of need all 64 voices.
> Is appears to be using it to generate the period interrupts.
> Does anyone know what it would take to rewrite the driver to
> not need this extra voice?
Any relationship to the fact that I can only allocate 21 subdevices with ALSA,
but 31 with DirectSound?
ALSA: Advanced Linux Sound Architecture Driver Version 1.0.4rc2 (Tue Mar 30 08:19:30 2004 UTC).
ALSA Driver: 0: Sound Blaster Live! [Live], device 0: emu10k1 [EMU10K1], 32/32 subdevices avail
ALSA Driver: 0: Sound Blaster Live! [Live], device 3: emu10k1 [EMU10K1 FX8010], 8/8 subdevices avail
ALSA: dsnd_pcm_hw_params: Cannot allocate memory
ALSA: Got 21 hardware buffers
vs
DirectSound Driver: SB Live! Audio [FF80] (ctaud2k.sys)
ID: {bd6dd71a-3deb-11d1-1252b90}
DirectSound sample rates: 4000..191999 (continuous)
Got 31 hardware buffers
--
Glenn Maynard
-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
>From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
next prev parent reply other threads:[~2004-06-06 4:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-05 12:59 EMU10K1 and the extra voice Chris Purnell
2004-06-06 4:54 ` Glenn Maynard [this message]
2004-06-06 10:40 ` Jaroslav Kysela
2004-06-06 18:09 ` Glenn Maynard
2004-06-07 7:21 ` Jaroslav Kysela
2004-06-06 10:38 ` Jaroslav Kysela
2004-06-09 0:35 ` Chris Purnell
2004-06-09 7:21 ` Jaroslav Kysela
2004-06-09 19:16 ` Chris Purnell
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=20040606045431.GA3025@zewt.org \
--to=g_sf@zewt.org \
--cc=alsa-devel@lists.sourceforge.net \
/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.