From: Jon <jon@seniorblanco.com>
To: Clemens Ladisch <clemens@ladisch.de>, alsa-devel@alsa-project.org
Subject: Re: trouble using S/PDIF input on CMI8738-MC6: C-Media CMI8738 (model 55)
Date: Wed, 20 Aug 2014 17:20:28 -0700 [thread overview]
Message-ID: <53F53B4C.20905@seniorblanco.com> (raw)
In-Reply-To: <53EB9C3B.2070602@seniorblanco.com>
On 08/13/2014 10:11 AM, Jon wrote:
> On 08/13/2014 08:14 AM, Clemens Ladisch wrote:
>> jon wrote:
>>> Simple mixer control 'IEC958 In Record',0
>>> Mono: Playback [off]
>>
>> Shouldn't this be on?
>
> Yes, it should, and actually it automatically turns itself on
> automatically when the arecord command is started, and then back off
> after the i/o error. Note that this is one of the toggles that only
> appeared in alsamixer after the source code change of the two "#if 0"
> lines to "#if 1".
>
>>
>>> Simple mixer control 'IEC958 In Select',0
>>> Mono: Playback [on]
>>
>> IIRC this selects between two different inputs.
>> Try both settings.
>
> Yes, the documentation I have read suggests it should toggle between the
> internal CDROM when off and the external digital input when on, however
> I have tried both settings and there is no apparent change in behavior.
> I still get an i/o error and a 44 byte file either way.
>
>>
>>
>> Regards,
>> Clemens
>>
Thanks by the way for the reply. I appreciate it. I wish I had more
informed data to provide. Its probably also worth noting that before
and after enabling the "IEC958 In Record" switch to be visible in
alsamixer, I also tried literally dozens of other combinations of on/off
states for the SPDIF switches, and other things in alsamixer, to no
avail. The outcome is always the same i/o error and resulting 44-byte
file of silence.
Is there perhaps any way to output some better diagnostic issue from the
driver that might hint at a solution? As I'm perusing the source code
right now I see that there are a bunch of "#define"s right near the
beginning, some commented as "model 037" and "model 039" after which
there are two adjacent to comments "model 055?" (the model I have, but
note the question mark) and I'm wondering if this problem could be
really just as simple as someone having guessed wrong about the correct
value there having not had this particular model on hand to test with?
Thanks,
Jon
next prev parent reply other threads:[~2014-08-21 0:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 16:29 trouble using S/PDIF input on CMI8738-MC6: C-Media CMI8738 (model 55) jon
2014-08-13 15:14 ` Clemens Ladisch
2014-08-13 17:11 ` Jon
2014-08-21 0:20 ` Jon [this message]
2014-08-21 10:31 ` Clemens Ladisch
2014-08-21 22:07 ` Jon
2014-08-22 8:50 ` Clemens Ladisch
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=53F53B4C.20905@seniorblanco.com \
--to=jon@seniorblanco.com \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
/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.