All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonas Petersen <jnsptrsn1@gmail.com>
To: Alan Horstmann <gineera@aspect135.co.uk>
Cc: alsa-devel@alsa-project.org,
	"Gabriel M. Beddingfield" <gabrbedd@gmail.com>
Subject: Re: M-Audio Delta 1010LT: S/PDIF clock source not working
Date: Tue, 09 Apr 2013 00:56:23 +0200	[thread overview]
Message-ID: <51634B17.3050907@gmail.com> (raw)
In-Reply-To: <201304072135.45811.gineera@aspect135.co.uk>

Am 07.04.2013 22:35, schrieb Alan Horstmann:
> On Sunday 07 April 2013 18:03, Gabriel M. Beddingfield wrote:
>> On 04/06/2013 05:52 PM, Jonas Petersen wrote:
>>> It seems it's related to the ICE1712... I now tried the Audiophile 2496.
>>> Same behaviour! There is no way to clock from external (S/PDIF). The
>>> 'Multi Track Internal Clock Default' setting will always override the
>>> external clock rate and mess up the capturing.
>> Well, it /should/ work -- according to the 1010's manual.  I'll bet it's
>> some register setting that's missing on the ice1712 -- but I have no
>> access to the specs/datasheets/schematics on these things.
>>
>> I wonder -- did this ever work on Linux?

Yes! I while ago I was doing stuff with the Delta 66 and things were 
fine. That was back with Ubuntu 10.04 and Alsa 1.0.22 and also 1.0.23.
I just grabbed an old Ubuntu 10.04 ISO which contains Alsa 1.0.22 and 
live booted it on my machine. Tests show that it's working as expected 
with the 1010LT: It's properly externally clocked.


> However I do seem to remember some relatively recent changes related 
> to external wordclock on the 1010; maybe it has been broken?

I found commit b8b1a4cb6842fb33769be1ad636f062d31d588c3 from Jan 17 
23:20:03 2011. It's a patch on delta.c and it's regarding a clock issue 
(though not exactly wordclock). I reverted that patch and recompiled but 
no success.

I'm going to continue later on that topic. At least there must have been 
some change that broke it since 1.0.23.

> @Jonas - are you using 'envy24control' to toggle the settings?

I suppose this shouldn't make any difference. I'm using alsamixer, 
amixer and API calls most of the time. Sometimes envy24control, mostly 
for (visual) input feedback. Tried only using envy24control, but didn't 
make any difference.

- Jonas

  reply	other threads:[~2013-04-08 22:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-05 15:34 M-Audio Delta 1010LT: S/PDIF clock source not working Jonas Petersen
2013-04-07  0:52 ` Jonas Petersen
2013-04-07 17:03   ` Gabriel M. Beddingfield
2013-04-07 20:35     ` Alan Horstmann
2013-04-08 22:56       ` Jonas Petersen [this message]
2013-04-09 14:21         ` Pavel Hofman
2013-04-11  7:23           ` Jonas Petersen
2013-04-12 14:53           ` Jonas Petersen
2013-04-15  7:35             ` Pavel Hofman

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=51634B17.3050907@gmail.com \
    --to=jnsptrsn1@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=gabrbedd@gmail.com \
    --cc=gineera@aspect135.co.uk \
    /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.