From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001725]: SB Audigy SE Not Working with Quake 4, Doom 3
Date: Sun, 8 Jan 2006 21:48:04 +0100 [thread overview]
Message-ID: <9d0b8afd8cb7bfd42039f03ba4a42722@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1725>
======================================================================
Reported By: malk271
Assigned To: jcdutton
======================================================================
Project: ALSA - driver
Issue ID: 1725
Category: PCI - ca0106
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
Distribution: Fedora Core 3
Kernel Version: 2.6.12-1.1381_FC3
======================================================================
Date Submitted: 01-08-2006 17:35 CET
Last Modified: 01-08-2006 21:48 CET
======================================================================
Summary: SB Audigy SE Not Working with Quake 4, Doom 3
Description:
On FC3, I have compiled and installed alsa-driver-1.0.11rc2 and
alsa-lib-1.0.11rc2 in order to be able to use a recently purchased Audigy
SE.
Regular playback is working (speaker-test and aplay both work, as does
Amarok with Alsa selected for playback). Skype playback does work, but is
horribly choppy (unusable really), unlike my other card, an old SB Live!
1024 player.
However, the Audigy SE does not work with Quake 4 and Doom 3. There is
some output, but it is just a collection of random sounds. I have tried
both stereo and 5.1 configurations. Also, output must be sent through the
plug plugin or the games complain about a sampling mismatch (48KHz found
but 44.1KHz required).
======================================================================
----------------------------------------------------------------------
rlrevell - 01-08-06 21:48
----------------------------------------------------------------------
Can you reproduce the problem with an app we have the source code to?
Issue History
Date Modified Username Field Change
======================================================================
01-08-06 17:35 malk271 New Issue
01-08-06 17:35 malk271 Distribution => Fedora Core 3
01-08-06 17:35 malk271 Kernel Version => 2.6.12-1.1381_FC3
01-08-06 21:48 rlrevell Note Added: 0007527
======================================================================
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next reply other threads:[~2006-01-08 20:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-08 20:48 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-13 18:58 [ALSA - driver 0001725]: SB Audigy SE Not Working with Quake 4, Doom 3 bugtrack
2006-02-13 18:43 bugtrack
2006-01-09 13:41 bugtrack
2006-01-09 10:05 bugtrack
2006-01-09 10:04 bugtrack
2006-01-09 8:48 bugtrack
2006-01-09 8:47 bugtrack
2006-01-08 20:49 bugtrack
2006-01-08 16:35 bugtrack
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=9d0b8afd8cb7bfd42039f03ba4a42722@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox