From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000935]: M-Audio Delta 1010-LT; S/PDIF out = 0Volts on device open
Date: Wed, 23 Feb 2005 20:09:44 +0100 [thread overview]
Message-ID: <bd1415613484632d799714038606ce9b@bugtrack.alsa-project.org> (raw)
The following issue has been SUBMITTED.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=935>
======================================================================
Reported By: stever8
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 935
Category: PCI - ice1712
Reproducibility: always
Severity: major
Priority: normal
Status: new
Distribution: Redhat Linux 7.3, modified
Kernel Version: 2.4.26
======================================================================
Date Submitted: 02-23-2005 20:09 CET
Last Modified: 02-23-2005 20:09 CET
======================================================================
Summary: M-Audio Delta 1010-LT; S/PDIF out = 0Volts on device
open
Description:
Our original report:
When we first load the alsa drivers, we see a S/PDIF output signal from
the 1010LT
on an oscilloscope. A minidisc player also sees this as a valid signal (it
is all
zeros, silence).
As soon as our program opens the audio device, however, the signal goes
to 0V on the oscilloscope, and the minidisc of course sees "no signal".
We can't output S/PDIF, no matter what settings we try in Envy24control.
Strangely enough, if we do the following, we do get S/PDIF output :
. Plug in an external S/PDIF input source (which is muted so as not to
mix
with our sound).
. In Envy24control, set the Master Clock to "Word Clock". (it doesn't work
if the
master clock is set to "S/PDIF")
Jaroslav Kysela suggested:
Strange. Could you try to comment lines:
//if (reset)
// snd_cs8427_reset(cs8427);
in alsa-kernel/i2c/cs8427.c and test if the signal is present after this
change?
Which I did. The S/PDIF signal no longer goes away (it appears on the
scope, and the minidisc player recognizes it as a valid signal) however it
just contains silence.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
02-23-05 20:09 stever8 New Issue
02-23-05 20:09 stever8 Distribution => Redhat Linux 7.3,
modified
02-23-05 20:09 stever8 Kernel Version => 2.4.26
======================================================================
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next reply other threads:[~2005-02-23 19:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-23 19:09 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-19 8:06 [ALSA - driver 0000935]: M-Audio Delta 1010-LT; S/PDIF out = 0Volts on device open bugtrack
2005-12-30 22:23 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=bd1415613484632d799714038606ce9b@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