From: Pavel Hofman <pavel.hofman@ivitera.com>
To: Jonas Petersen <jnsptrsn1@gmail.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: M-Audio Audiophile 192 (ice1724)'s broken spdif capture
Date: Thu, 31 Jan 2013 10:04:25 +0100 [thread overview]
Message-ID: <510A3399.1010600@ivitera.com> (raw)
In-Reply-To: <5109C6AB.8050407@gmail.com>
On 31.1.2013 02:19, Jonas Petersen wrote:
> Am 29.01.2013 10:44, schrieb Pavel Hofman:
>> On 28.1.2013 22:25, Jonas Petersen wrote:
>>>> Jonas, please could you check if ak4114 pins XTL0/1 (10, 11) are
>>>> connected to logical high? They should be :)
>>> Physically they're both on ground. I don't know what active state that
>>> chip has though.
That would mean the chip is fed 11.2896MHz clock. I do not see any
crystal on
http://www.nix.ru/autocatalog/m_audio_midiman_sound/34397_2245_draft.jpg
. Is it the same card you have, with the crystal position empty? Are you
really sure they are not on power supply?
>> Let 's wait until we get the ak4114 register dump file :)
>
> Can't wait. :)
Did the patch work?
I did a quick test in Windows 7. This driver is able to
> detect the sample rate. If I set the clock source to "spdif in" at the
> control pannel, then I can see the rate changing when I switch to
> another rate on the spdif source.
Did you test 192kHz and 176,4kHz? The receiver can work in two modes.
Either it knows it is fed an independent clock and detects the sample
rate precisely, or it simply reads the sample rate from SPDIF preamble
of the incoming stream. The mode is select by the XTL0,1 pins. Often the
streams do not contain correct information, especially for consumer mode
which does not have room for the larger samplerates code. Could you
please test both consumer and professional modes, all common samplerates?
Thanks,
Pavel.
next prev parent reply other threads:[~2013-01-31 9:04 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-26 16:35 M-Audio Audiophile 192 (ice1724)'s broken spdif capture Jonas Petersen
2013-01-26 19:30 ` Jaroslav Kysela
2013-01-26 21:20 ` Pavel Hofman
2013-01-26 22:37 ` Jonas Petersen
2013-01-27 15:49 ` Jonas Petersen
2013-01-28 9:29 ` Jaroslav Kysela
2013-01-28 12:52 ` Pavel Hofman
2013-01-28 21:25 ` Jonas Petersen
2013-01-29 9:44 ` Pavel Hofman
2013-01-31 1:19 ` Jonas Petersen
2013-01-31 9:04 ` Pavel Hofman [this message]
2013-01-31 20:56 ` Jonas Petersen
2013-01-28 12:36 ` Pavel Hofman
2013-01-29 0:32 ` Jonas Petersen
2013-01-29 9:39 ` Pavel Hofman
2013-01-29 13:10 ` Jonas Petersen
2013-01-30 10:30 ` Pavel Hofman
2013-01-29 19:14 ` Jonas Petersen
2013-01-30 10:26 ` Pavel Hofman
2013-01-30 15:34 ` Pavel Hofman
2013-01-31 0:29 ` Jonas Petersen
2013-01-31 10:33 ` Pavel Hofman
2013-01-31 22:25 ` Jonas Petersen
2013-02-02 1:22 ` Jonas Petersen
2013-02-02 10:44 ` Pavel Hofman
2013-02-02 22:47 ` Jonas Petersen
2013-02-04 16:56 ` Pavel Hofman
2013-02-23 22:13 ` Jonas Petersen
2013-02-25 11:47 ` Pavel Hofman
2013-01-26 21:29 ` Jonas Petersen
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=510A3399.1010600@ivitera.com \
--to=pavel.hofman@ivitera.com \
--cc=alsa-devel@alsa-project.org \
--cc=jnsptrsn1@gmail.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.