From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0002258]: nForce4 + intel8x0 + Dolby Digital 5.1 + S/PDIF = crackle at start of playback
Date: Tue, 11 Jul 2006 18:54:26 +0200 [thread overview]
Message-ID: <a667e2b91e9c47ea793e05abfb2f26ea@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2258>
======================================================================
Reported By: Human
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 2258
Category: PCI - intel8x0
Reproducibility: always
Severity: major
Priority: normal
Status: new
Distribution: KnoppMyth
Kernel Version: 2.6.17-chw-2
======================================================================
Date Submitted: 07-05-2006 22:12 CEST
Last Modified: 07-11-2006 18:54 CEST
======================================================================
Summary: nForce4 + intel8x0 + Dolby Digital 5.1 + S/PDIF =
crackle at start of playback
Description:
Playing stereo audio never causes a crackle. However, playback of 5.1
Dobly Digital content (standalone audio or audio embedded in video) causes
a quick but very loud sub-second audio crackle before playback continues,
when the previous playback was _not_ also multi-channel content. The
problem always happens when the card is being asked to _switch_ to
multichannel audio _from_ either stereo or a non-initialized state. The
crackle happens on both coaxial and optical S/PDIF connections to the
nForce4 (CK804) onboard soundcard.
The same receiver has not had a problem with S/PDIF with a different card
(Chaintech AV-710 / ice1724).
======================================================================
----------------------------------------------------------------------
tiwai - 07-11-06 18:38
----------------------------------------------------------------------
It's a known problem of SPDIF on nForce chipsets. SPDIF non-audio output
doesn't work well because of lack of proper SPDIF status bit setting.
Since SPDIF is transmitted directly from the audio chip, the changing
register in AC97 codec doesn't help.
Unfortuantely, we have no datasheet to fix this...
----------------------------------------------------------------------
Human - 07-11-06 18:54
----------------------------------------------------------------------
Hi, tiwai. I don't understand the cause fully, but maybe I can still help.
Is a workaround possible? Half a second of silence would be far better
than half a second of static. Perhaps muting the line, then using the
buggy procedure, then unmuting? Or is the problem that the receiver is
being asked to switch to multichannel mode in such a way that the receiver
interprets part of the switch request as audible noise, so muting the
source would not help? Is any workaround possible?
As for a real fix, has nVidia refused to provide the necessary datasheet
for the nForce4 chipset when asked? If you tell me what specifically
would help fix the problem, I will do what I can to provide it. I don't
exactly have an "in" with nVidia, but as a vendor who sells nVidia
products, they have assigned Linux troubleshooting techs to my requests in
the past.
Finally, if you point me to the relevant code in which the S/PDIF status
bit is set, couldn't I iterate through all possible settings and
eventually find the right one? If the solution space is small enough, it
may be feasible. Are we talking a 4-bit value or a 16-bit value?
If it's not appropriate to keep conversing back and forth in this bug
report, we can switch to email.
Issue History
Date Modified Username Field Change
======================================================================
07-05-06 22:12 Human New Issue
07-05-06 22:12 Human File Added: asound.conf
07-05-06 22:12 Human Distribution => KnoppMyth
07-05-06 22:12 Human Kernel Version => 2.6.17-chw-2
07-05-06 22:13 Human Issue Monitored: Human
07-11-06 18:34 Human Note Added: 0010977
07-11-06 18:38 tiwai Note Added: 0010978
07-11-06 18:54 Human Note Added: 0010979
======================================================================
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
next reply other threads:[~2006-07-11 16:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-11 16:54 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-19 18:42 [ALSA - driver 0002258]: nForce4 + intel8x0 + Dolby Digital 5.1 + S/PDIF = crackle at start of playback bugtrack
2006-07-11 16:38 bugtrack
2006-07-11 16:34 bugtrack
2006-07-05 20:12 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=a667e2b91e9c47ea793e05abfb2f26ea@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 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.