From: Takashi Iwai <tiwai@suse.de>
To: Alex Stanoev <alex@astanoev.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] ALSA: ca0106: Disable IZD on SB0570 DAC to fix audio pops
Date: Mon, 29 Oct 2018 16:59:25 +0100 [thread overview]
Message-ID: <s5hy3agg2w2.wl-tiwai@suse.de> (raw)
In-Reply-To: <20181028165512.24474-1-alex@astanoev.com>
On Sun, 28 Oct 2018 17:55:12 +0100,
Alex Stanoev wrote:
>
> The Creative Audigy SE (SB0570) card currently exhibits an audible pop
> whenever playback is stopped or resumed, or during silent periods of an
> audio stream. Initialise the IZD bit to the 0 to eliminate these pops.
>
> The Infinite Zero Detection (IZD) feature on the DAC causes the output
> to be shunted to Vcap after 2048 samples of silence. This discharges the
> AC coupling capacitor through the output and causes the aforementioned
> pop/click noise.
>
> The behaviour of the IZD bit is described on page 15 of the WM8768GEDS
> datasheet: "With IZD=1, applying MUTE for 1024 consecutive input samples
> will cause all outputs to be connected directly to VCAP. This also
> happens if 2048 consecutive zero input samples are applied to all 6
> channels, and IZD=0. It will be removed as soon as any channel receives
> a non-zero input". I believe the second sentence might be referring to
> IZD=1 instead of IZD=0 given the observed behaviour of the card.
>
> This change should make the DAC initialisation consistent with
> Creative's Windows driver, as this popping persists when initialising
> the card in Linux and soft rebooting into Windows, but is not present on
> a cold boot to Windows.
>
> Signed-off-by: Alex Stanoev <alex@astanoev.com>
Applied (with Cc to stable) now. Thanks.
Takashi
next prev parent reply other threads:[~2018-10-29 15:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-28 16:55 [PATCH] ALSA: ca0106: Disable IZD on SB0570 DAC to fix audio pops Alex Stanoev
2018-10-29 15:59 ` Takashi Iwai [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-10-20 0:33 Alex Stanoev
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=s5hy3agg2w2.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alex@astanoev.com \
--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 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.