Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
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: Fri, 24 Jun 2005 13:40:24 +0200	[thread overview]
Message-ID: <d4c79e2ca20d63317620df201f1cceab@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-24-2005 13:40 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.
======================================================================

----------------------------------------------------------------------
 tiwai - 06-24-05 11:11 
----------------------------------------------------------------------
This might depend on what dmix parameters you use.  The parametes used in
slave.pcm "dmix" is different from the default ones of dmix.

----------------------------------------------------------------------
 andersin - 06-24-05 13:40 
----------------------------------------------------------------------
Even if I do not specify any parameters in my asound.conf, I can observer
the effect. I might be wrong, but I assume, that the default settings of
plug dmix and type dmix match.

Where can I find out, which parameters the default dmix uses so that I can
test it with that setup?

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                          
======================================================================




-------------------------------------------------------
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

             reply	other threads:[~2005-06-24 11:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-24 11:40 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-25 11:20 bugtrack
2005-06-24 14:56 bugtrack
2005-06-24 12:55 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=d4c79e2ca20d63317620df201f1cceab@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