From: Doug McLain <doug@nostar.net>
To: John Rigg <j@sound-man.co.uk>
Cc: alsa-devel@lists.sourceforge.net, jackit-devel@lists.sourceforge.net
Subject: Re: Re: [Jackit-devel] Real-world reports on two Delta 1010LTs/ice1712 synched?
Date: Tue, 27 Dec 2005 15:50:02 -0500 [thread overview]
Message-ID: <43B1A8FA.8080408@nostar.net> (raw)
In-Reply-To: <20051227130029.GB3770@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1483 bytes --]
>
> With 2.6.14 or later kernel, starting envy24control (from alsa-tools-1.0.10)
> from xterm resulted in a slew of error messages saying "Unable to determine
> word clock status" scrolling off the xterm. The patch fixed that. Maybe that
> only happens with the 1010 not the 1010LT. It's possible that with the broken
> word clock on the 1010LT it wasn't even trying to determine word clock
> status so it didn't trigger the bug.
>
> John
I asked that before I started studying the mixer and driver code
closely. I now have a good understanding of what the patch does, and
why the 1010LT isnt working. I also don't need any tests done by anyone
that I was asking for.
It looks like the driver is the root of the problem. There doesnt
appear to currently be any facility provided for the 1010LT to set and
check word clock as the master clock source, and SPDIF In only works by
accident.
#define ICE1712_DELTA_1010LT_WORDCLOCK 0x80 /* sample clock source: 0 =
Word Clock Input, 1 = S/PDIF Input ??? */
Doesn't appear to be correct, as SPDIF Input works wether I send a 1 or
a 0 to the word_clock_sync snd_ctl_elem. I'm going to keep plugging
away at this when I get time to get back on it. For now, here's a patch
that should fix the problem of having to press spdif before word clock.
If it does work for you on the regular 1010, then the comments for
both the 1010 and 1010lt are backwards (where 0 = word clock and 1 = spdif).
Doug
--
http://nostar.net/
[-- Attachment #2: envy24control-wcselect.diff --]
[-- Type: text/x-patch, Size: 626 bytes --]
Index: hardware.c
===================================================================
RCS file: /cvsroot/alsa/alsa-tools/envy24control/hardware.c,v
retrieving revision 1.17
diff -u -r1.17 hardware.c
--- hardware.c 5 Dec 2005 21:03:06 -0000 1.17
+++ hardware.c 27 Dec 2005 20:47:24 -0000
@@ -128,6 +128,7 @@
} else if (!strcmp(what, "SPDIF")) {
internal_clock_set(13);
} else if (!strcmp(what, "WordClock")) {
+ internal_clock_set(13); // Hack
master_clock_word_select(1);
} else {
g_print("internal_clock_toggled: %s ???\n", what);
next prev parent reply other threads:[~2005-12-27 20:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20051223225430.GA4995@localhost.localdomain>
[not found] ` <43AC826C.1040405@nostar.net>
[not found] ` <20051223233816.GA5102@localhost.localdomain>
[not found] ` <43AC8990.7040900@nostar.net>
[not found] ` <20051224124823.GA4183@localhost.localdomain>
[not found] ` <20051224144548.GA4306@localhost.localdomain>
[not found] ` <20051224165610.GA4484@localhost.localdomain>
[not found] ` <43AE9FA6.2020207@nostar.net>
[not found] ` <20051226130327.GA4763@localhost.localdomain>
[not found] ` <43B059A3.2050302@nostar.net>
[not found] ` <20051227000428.GA3805@localhost.localdomain>
2005-12-27 2:34 ` [Jackit-devel] Real-world reports on two Delta 1010LTs/ice1712 synched? Doug McLain
2005-12-27 2:34 ` Doug McLain
[not found] ` <43B0A83F.1040907@nostar.net>
2005-12-27 5:06 ` Doug McLain
2005-12-27 5:06 ` Doug McLain
2005-12-27 13:00 ` [Alsa-devel] " John Rigg
2005-12-27 20:50 ` Doug McLain [this message]
2005-12-28 21:19 ` Re: [Jackit-devel] " John Rigg
2006-01-01 12:55 ` Doug McLain
2006-01-01 19:58 ` John Rigg
2006-01-16 17:56 ` [Alsa-devel] " Pasi Kärkkäinen
2006-01-16 19:26 ` Doug McLain
2006-01-16 20:07 ` Re: [Jackit-devel] " Lee Revell
2006-01-18 10:56 ` Alan Horstmann
2006-01-18 14:48 ` Alan Horstmann
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=43B1A8FA.8080408@nostar.net \
--to=doug@nostar.net \
--cc=alsa-devel@lists.sourceforge.net \
--cc=j@sound-man.co.uk \
--cc=jackit-devel@lists.sourceforge.net \
/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