From: Doug McLain <doug@nostar.net>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: John Rigg <j@sound-man.co.uk>,
alsa-devel@lists.sourceforge.net,
jackit-devel@lists.sourceforge.net
Subject: Re: [Alsa-devel] Re: Real-world reports on two Delta 1010LTs/ice1712 synched?
Date: Mon, 16 Jan 2006 14:26:59 -0500 [thread overview]
Message-ID: <43CBF383.3000807@nostar.net> (raw)
In-Reply-To: <20060116175652.GM28738@edu.joroinen.fi>
Good timing, I was just about to give a summary of my findings so far:
First of all, the differences in the 1010LT vs the 1010 that are most
relevent here, I believe, is the SPDIF i/o chips (cs8413 receiver,
cs8404 xmitter) used on the 1010 vs the one single transceiver (cs8427)
used on the 1010LT. They also use different ADC/DAC's, but at this
point in the game they dont appear to be relevent to this problem, and
they appear to be completely functional.
Last night I got my oscope back and took a look at the wordclock output
signal, first in windows. As expected, the card outputs at the
frequency the card is running at, wether its via internal clock, SPDIF
in, or word clock input. I checked all three. Also in windows, SPDIF
Out works in all 3 modes as well, as it should.
In Linux, There is no word clock output signal nor an SPDIF signal
unless I either input a word clock signal or an SPDIF signal, and then
the signal stays at the speed of the input signal, even if I switch to
various internal clock speeds. Basically the input clock is just being
passed thru. Also, the card will not sync to an input word clock signal
no way, no how. It will sync to an spdif signal though. This is
actually the only way to get spdif out to work. On a delta 1010LT in
Linux, the only way to get SPDIF out, is if there is a valid SPDIF In
signal, and I am clocked off it.
Knowing this, I am currently able to run two delta 1010LT's synced via
spdif (spdif out of card 1 to spdif of card 2), with JACK (using john
rigg's asoundrc, alsa-lib, and jack patches), with an external spdif
signal coming into card 1's SPDIF In from a digital mixer. I did many
mutitrack recordings of all 16 inputs simultaneously into ardour,
everything worked great. This just confirms that the only thing keeping
the 1010LT's from playing nice together is the clock problem. Otherwise
they are ready to go. A possible option while the clock issue remains
at large, is to use the spdif output from your on board sound card(if so
equipped) as an spdif source to your first delta. I gave this about 5
minutes of my time, and didnt have the best of luck. I couldnt keep the
signal coming out of my via82xx alive all the time, etc. I don't know
it well enough to use alsamixer, etc and I had to keep xmms running (set
to use the alsa driver on the via82xx directly) all the time to keep the
signal alive. I wasnt too interested in getting it working well like
this, but it was an idea.
I've been studying the ice1712 alsa driver closely over the past few
weeks, and comparing all relevent ice1712 control register values in
windows vs linux (in windows I got ahold of this nice program called
PCIScope, a dream for reverse engineering pci hardware!) and I think
(hope) the problem is in the init and configuration of the cs8427 spdif
transceiver. There are differences in bit values on the ice1712's GPIO
data register. So my two areas of concern are deciphering the usage of
the GPIO register and the cs8427 spdif transceiver. The ice1712 talks to
the cs8427 over I2C, which isnt as straightforward to read as regular
i/o registers, so it's more studying ahead. I am focusing on fixing
spdif functionality, since the cs8427 datasheet is very clear about
spdif operation. I am hoping by fixing regular spdif functionality on
the ship, word clock will be fixed too. We'll see.
Doug
--
http://nostar.net/
Pasi Kärkkäinen wrote:
>
> Doug,
>
> Have you found out anything?
>
> - Pasi Kärkkäinen
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_idv37&alloc_id\x16865&op=click
> _______________________________________________
> Jackit-devel mailing list
> Jackit-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jackit-devel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id\x16865&op=click
next prev parent reply other threads:[~2006-01-16 19:26 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 ` Re: [Jackit-devel] " Doug McLain
2005-12-28 21:19 ` 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 [this message]
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=43CBF383.3000807@nostar.net \
--to=doug@nostar.net \
--cc=alsa-devel@lists.sourceforge.net \
--cc=j@sound-man.co.uk \
--cc=jackit-devel@lists.sourceforge.net \
--cc=pasik@iki.fi \
/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