alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: "Pharaoh ." <pharaoh137@gmail.com>
To: Rene Herman <rene.herman@keyaccess.nl>
Cc: alsa-devel@alsa-project.org
Subject: Re: Audio quality issues with dmix plugin
Date: Wed, 7 Nov 2007 14:19:04 +0530	[thread overview]
Message-ID: <61445c750711070049hf2d0f10r1acaccd6b1e2a928@mail.gmail.com> (raw)
In-Reply-To: <473106E7.9050601@keyaccess.nl>

On 11/7/07, Rene Herman <rene.herman@keyaccess.nl> wrote:
> On 06-11-07 09:16, Pharaoh . wrote:
>
> > When I play a 44Khz file without using any ALSA plugin like
> >
> > #aplay -Dhw:0,0 44k.wav
> >
> > the sound quality is awesome but when I play the same file using dmix,
> > clicks are introduced.
> >
> > #aplay -Dplug:dmix 44k.wav
> >
> > changing period size and buffer size doesn't help. I am testing my ALSA
> > driver on an OMAP850
> > based board.
>
> dmix does 48 kHz by default. Does it sound "awesome" when you play a 48 kHz
> file directly to hw:0,0? If that also clicks, the problem will be your
> driver's handling of the 48 kHz rate -- if not, it'll be the resampling, and
> I'll probably need to bow out...
>
> Rene.
>

Hi Rene,
I changed alsa.conf so that dmix does 44.1kHz and tried, without dmix
44.1 and 48kHz files sound 'awesome' but with dmix some clicks appear
at both the rates. Going ahead, I recorded a 8Khz mono sound using my
driver and played it back without dmix, it plays without any clicks,
but use dmix and clicks appear. So basically,
clicks appear at all the sample rates with dmix and without it I could
play all the sample rate files well since my hw supports hw
upsampling.

-Pharaoh.

  reply	other threads:[~2007-11-07  8:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-06  8:16 Audio quality issues with dmix plugin Pharaoh .
2007-11-07  0:29 ` Rene Herman
2007-11-07  8:49   ` Pharaoh . [this message]
2007-11-07 22:03     ` Rene Herman
2007-11-08  6:49       ` Pharaoh .

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=61445c750711070049hf2d0f10r1acaccd6b1e2a928@mail.gmail.com \
    --to=pharaoh137@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=rene.herman@keyaccess.nl \
    /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;
as well as URLs for NNTP newsgroup(s).