From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001188]: quake3 crashes, capture not working
Date: Tue, 3 Jan 2006 12:41:23 +0100 [thread overview]
Message-ID: <71dbdf03c5fdc6a1de85a342f3b39e87@bugtrack.alsa-project.org> (raw)
The following issue has been set as RELATED TO issue 0000373.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1188>
======================================================================
Reported By: gnarlie
Assigned To: jcdutton
======================================================================
Project: ALSA - driver
Issue ID: 1188
Category: PCI - ca0106
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
Distribution: gentoo
Kernel Version: 2.6.8.1 with the voluntary preempt patch
======================================================================
Date Submitted: 06-13-2005 19:41 CEST
Last Modified: 09-10-2005 13:09 CEST
======================================================================
Summary: quake3 crashes, capture not working
Description:
The card is a sb live 24bit pci.
quake3 crashes me after a map has loaded, oddly one map works but crashes
everytime when I finish the map. The sounds in the menus work. Tried my
mic
with the mic-in and all possible mixer settings, no dice.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0000373 Sound in Quake 3 does not work
======================================================================
----------------------------------------------------------------------
jcdutton - 09-10-05 13:09
----------------------------------------------------------------------
The ca0106 based sound card is currently unsuitable for any linux based
games.
The card cannot do 44100 Hz sound, and all games like Doom3 and Quake3 use
44100 Hz sound. I would suggest using a different sound card for now, or
wait until the alsa-lib resamplers have improved in order to support
this.
The improvements needed to the alsa-lib resamplers are rather complicated,
so don't expect it to happen any time soon.
Issue History
Date Modified Username Field Change
======================================================================
06-13-05 19:41 gnarlie New Issue
06-13-05 19:41 gnarlie Distribution => gentoo
06-13-05 19:41 gnarlie Kernel Version => 2.6.8.1 with the
voluntary preempt patch
09-10-05 13:09 jcdutton Note Added: 0006117
01-03-06 12:41 perex Relationship added related to 0000373
======================================================================
-------------------------------------------------------
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-03 11:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-03 11:41 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-13 18:58 [ALSA - driver 0001188]: quake3 crashes, capture not working bugtrack
2006-02-13 18:48 bugtrack
2005-09-10 11:09 bugtrack
2005-06-13 17:41 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=71dbdf03c5fdc6a1de85a342f3b39e87@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