All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@keyaccess.nl>
To: Krzysztof Helt <krzysztof.h1@poczta.fm>
Cc: Alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: [PATCH 1/2] opti93x: add support for Opti93x codec in cs4231-lib
Date: Sun, 15 Jun 2008 21:50:30 +0200	[thread overview]
Message-ID: <48557286.701@keyaccess.nl> (raw)
In-Reply-To: <20080615193325.6fac815d.krzysztof.h1@poczta.fm>

On 15-06-08 19:33, Krzysztof Helt wrote:

> I have tried to reproduce this on an opti930 card. I do not hear any
> difference. I tried at 100% and 75% (both PCM and Master) levels. I
> used the script which reloaded an old and new driver and played a wav
> file. I run it in a loop. The thing I noticed is that the old driver
> often produced noise (say more than 1 in 4 tries) instead of the
> sound. The new driver (cs4231) never. The old and new driver produced
> a click before playing the sound (50% probability).
> 
> I have checked the mixer code. It is not changed.
> 
> What do you do to get a different sound level? (card model, level
> settings).

I've restested (quite extensively by now...) and have not been able to 
reproduce. I do have quit a few 931 and 933 cards, all alike physically 
but likely not all the same post the onboard amp. What MAY have happened 
is that I mistakingly grabbed another one during testing while I was 
busy switching 930, 931 and 933 cards (and kernels).

Doubt it a bit but well, I'm just not reproducing now. I do believe it 
was a 931 on which I observed the level difference; let's just conclude 
this must have been an error on my part.

Rene.

      reply	other threads:[~2008-06-15 19:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-09 21:07 [PATCH 1/2] opti93x: add support for Opti93x codec in cs4231-lib Krzysztof Helt
2008-06-09 23:21 ` Rene Herman
2008-06-10  5:04   ` Krzysztof Helt
2008-06-15 17:33   ` Krzysztof Helt
2008-06-15 19:50     ` Rene Herman [this message]

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=48557286.701@keyaccess.nl \
    --to=rene.herman@keyaccess.nl \
    --cc=alsa-devel@alsa-project.org \
    --cc=krzysztof.h1@poczta.fm \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.