From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Audigy2 in SNDRV_PCM_FMTBIT_S32_LE mode.
Date: Tue, 18 May 2004 17:03:17 +0100 [thread overview]
Message-ID: <40AA33C5.6090808@superbug.demon.co.uk> (raw)
In-Reply-To: <s5h3c5x3f5c.wl@alsa2.suse.de>
Takashi Iwai wrote:
> At Tue, 18 May 2004 16:47:01 +0100,
> James Courtier-Dutton wrote:
>
>>What would I need to change in the emu10k1 driver, to get alsa-lib to
>>send it 32bit audio samples.
>>I tried just adding the SNDRV_PCM_FMTBIT_S32_LE to the playback options,
>>but that did not work.
>>
>>When I did that, everything just played at half speed.
>>
>>Can anyone give me any pointers as to where else I should change things
>>in order to get 32bit audio to the Audigy2 DSP.
>
>
> AFAIK, emu10k1 engine processes only 16bit PCM.
> or do you know the register (or anything else) to handle 32bit data
> for audigy?
>
>
> Takashi
>
>
The SB Live DSP can only handle 16bit PCM.
The SB Audigy DSP can handle 24/32 bit PCM.
I am working from what someone has told me to get 24bit sound. Send it
to the Audigy inside a 32bit value: -
For playback:
You can use voice grouping - alloc 4 FX busses for 1 stereo stream
or use TRAM.
Does this help you ?
-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
next prev parent reply other threads:[~2004-05-18 16:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-18 15:47 Audigy2 in SNDRV_PCM_FMTBIT_S32_LE mode James Courtier-Dutton
2004-05-18 15:53 ` Takashi Iwai
2004-05-18 16:03 ` James Courtier-Dutton [this message]
2004-05-19 10:32 ` Takashi Iwai
[not found] <200405191119.i4JBJANj002233@www3.pobox.sk>
2004-05-19 13:17 ` Takashi Iwai
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=40AA33C5.6090808@superbug.demon.co.uk \
--to=james@superbug.demon.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
--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.