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: Mon, 25 Feb 2013 12:47:54 +0100 [thread overview]
Message-ID: <512B4F6A.1070505@ivitera.com> (raw)
In-Reply-To: <51293F16.6030209@gmail.com>
On 23.2.2013 23:13, Jonas Petersen wrote:
>
>>> Ok, why not adding a control for that. But first explain something to
>>> me. I see these 15 control definitions "snd_ak4114_iec958_controls[]" in
>>> ak4114.c. How are they accessed? Where can I read for example the
>>> "IEC958 External Rate" value? In the proc dir they do not show up.
>>> Neither at Juli nor at AP192. Are these only API functions?
>> see output of amixer contents. They are defined as PCM-type controls
>> (not MIXER type and do not apper e.g. in alsamixer.
>
> Thanks, found it. Would that help in finding out how the card is
> detecting rate without any clue?
Hopefully. It shows you values of all ak4114 registers. The same
information as available to the windows driver.
Now can you please look at the regs if you can spot any hint of the
incoming sample rate from Juli (specifically the spdif channel status
regs and the incoming fs regs)? Thanks.
>
> I once read somwhere about a kind of hackish way of detecting sampling
> frequency by just capturing some samples (at a fixed rate) and
> calculating by comparing what you get to what you're supposed to get (or
> something like that, don't remember exactly). Can't find it anywhere
> right now though.
>
> Might it be that the windows driver is doing something like that as a
> fallback (or even always) when there is no channel status?
Well, it is certainly feasible but I very much doubt the driver does it.
>
> I'd like to once send the card a - let's say - 44.1 kHz signal with a -
> let's say - 96 kHz info in the channel status and see what the windows
> driver says. :)
Take a look at the iecset utility. It sets the IEC958 channel status
bits of the spdif transmitter (e.g. of your Juli or AP192). I would
start a 44.1kHz stream and try to rewrite the values using iecset. You
can check in regs list of your ice1724 card in
/proc/asound/yourcard/ice1724 if the change took place (register MT3C).
The playback may lock the IEC958 channel status controls. If it is the
case, try to comment out the IEC958 Playback Default "lock true" in
/usr/share/alsa/cards/ICE1724.conf.
Instead of iecset you can use amixer to manipulate IEC958 Playback
Default directly, but you will have to figure out correct bit values.
Good luck and thanks for the patch you sent :)
Pavel.
next prev parent reply other threads:[~2013-02-25 11:47 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
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 [this message]
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=512B4F6A.1070505@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.