From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001211]: type dmix produces noise, type plug slave.pcm "dmix" does not on SB EXtigy
Date: Sat, 25 Jun 2005 13:20:27 +0200 [thread overview]
Message-ID: <cb2c8b30cee042269aacdc3418aa3e2a@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1211>
======================================================================
Reported By: andersin
Assigned To: Clemens Ladisch
======================================================================
Project: ALSA - driver
Issue ID: 1211
Category: USB - usb-audio
Reproducibility: always
Severity: minor
Priority: normal
Status: assigned
Distribution:
Kernel Version: 2.6.11
======================================================================
Date Submitted: 06-24-2005 00:02 CEST
Last Modified: 06-25-2005 13:20 CEST
======================================================================
Summary: type dmix produces noise, type plug slave.pcm "dmix"
does not on SB EXtigy
Description:
I recently noticed crackling sound when using the dmix plugin. While the
simple case { type plug; slave.pcm "dmix" } works, { type dmix; slave.pcm
"extigy" } (where extigy is the pcm for the card) produces a crackling
sound. (I observe the same problem with my build in ICH4 card, but AFAIR
this has been reported already).
I have tried a variety of buffering and period settings that I found in
various documentations on the web, but all attempts were unsuccessful.
======================================================================
----------------------------------------------------------------------
andersin - 06-24-05 16:56
----------------------------------------------------------------------
At the moment, when the extigy is not connected, I am not able to reproduce
any of the distortion on the INTEL chip I was talking about. Strange
indeed. Once I get back to the extigy, I will report back, if the error
surfaces again.
----------------------------------------------------------------------
andersin - 06-25-05 13:20
----------------------------------------------------------------------
Now that I tested the setup again, I am unable to reproduce this issue. I
am not sure what caused it and will try my best to reproduce it and give a
more detailed explanation on what caused it. Unitl then, I think the issue
can be closed.
Issue History
Date Modified Username Field Change
======================================================================
06-24-05 00:02 andersin New Issue
06-24-05 00:02 andersin Kernel Version => 2.6.11
06-24-05 11:11 tiwai Note Added: 0005210
06-24-05 13:40 andersin Note Added: 0005219
06-24-05 14:55 tiwai Note Added: 0005222
06-24-05 16:56 andersin Note Added: 0005237
06-25-05 13:20 andersin Note Added: 0005257
======================================================================
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
next reply other threads:[~2005-06-25 11:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-25 11:20 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-27 14:20 [ALSA - driver 0001211]: type dmix produces noise, type plug slave.pcm "dmix" does not on SB EXtigy bugtrack
2005-06-24 14:56 bugtrack
2005-06-24 12:55 bugtrack
2005-06-24 11:40 bugtrack
2005-06-24 9:11 bugtrack
2005-06-23 22:02 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=cb2c8b30cee042269aacdc3418aa3e2a@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