From: Jonas Petersen <jnsptrsn1@gmail.com>
To: alsa-devel <alsa-devel@alsa-project.org>
Cc: Pavel Hofman <pavel.hofman@ivitera.com>
Subject: Re: M-Audio Delta 1010LT: S/PDIF clock source not working
Date: Sun, 07 Apr 2013 02:52:42 +0200 [thread overview]
Message-ID: <5160C35A.8020403@gmail.com> (raw)
In-Reply-To: <515EEF10.1020007@gmail.com>
Am 05.04.2013 17:34, schrieb Jonas Petersen:
> I am trying to capture from S/PDIF. I get a signal but the clocking is
> broken somehow.
>
> I have 'Multi Track Internal Clock' on 'ICE958 Input'.
>
> 'Word Clock Status' and 'Word Clock Sync' are 'Off'.
>
> What happens is the following: It captures what comes in on S/PDIF but
> it seems it will always use the internal clock with the setting from
> 'Multi Track Internal Clock Default'.
>
> So even though 'Multi Track Internal Clock' is on 'ICE958 Input', the
> setting of 'Multi Track Internal Clock Default' will clock the signal.
>
> A 1 kHz sine wave at 48 kHz samplerate captured with 'Multi Track
> Internal Clock Default' on 96 kHz will result in a 2 kHz sine. When
> the sample frequency rates are matched, it will capture at correct
> rate but with hiccups due to the rates not perfectly aligned.
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.
I did tests on 2 very different systems: a) AMD with Xubuntu 12.10, b)
Intel with Ubuntu 12.10.
- Jonas
next prev parent reply other threads:[~2013-04-07 0:52 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 [this message]
2013-04-07 17:03 ` Gabriel M. Beddingfield
2013-04-07 20:35 ` Alan Horstmann
2013-04-08 22:56 ` Jonas Petersen
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=5160C35A.8020403@gmail.com \
--to=jnsptrsn1@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=pavel.hofman@ivitera.com \
/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.