Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Udo van den Heuvel <udovdh@xs4all.nl>
To: alsa-devel@alsa-project.org
Subject: Emvy24control s/pidf input issue
Date: Mon, 17 Mar 2008 17:32:18 +0100	[thread overview]
Message-ID: <47DE9D12.9030900@xs4all.nl> (raw)

Hello,

I just noticed that S/PDIF input on my Audiophile 2496 does not work.
I see:

[udo@wda ~]$ envy24control
using    --- input_channels: 0
         --- output_channels: 4
         --- pcm_output_channels: 8
         --- spdif in/out channels: 2
Unable to read S/PDIF input switch: No such file or directory

Changing the Digital Input from coax to optical or vice versa
gives:
Unable to write S/PDIF on/off switch: No such file or directory
Unable to write S/PDIF input switch: No such file or directory

This is on Fedora 8 x86_64 with alsa-tools 1.0.12-4 from Fedora Core 7,
envycontrol 0.6.0.
S/PDIF output works without a problem. Did not have S/PDIF input working
before, as far as I remember.

Using -v I do not see signal in the meters.

In the source I see in spdif_input_update:

        if ((card_eeprom.subvendor != ICE1712_SUBDEVICE_DELTADIO2496) &&
            ! card_is_dmx6fire)
                return;
        if ((err = snd_ctl_elem_read(ctl, spdif_input)) < 0)
                g_print("Unable to read S/PDIF input switch: %s\n",
snd_strerror(err));
(etc)

Why does snd_ctl_elem_read fail?
How could I make S/PDIF input work again?

Tips are very welcome!

Kind regards,
Udo

             reply	other threads:[~2008-03-17 16:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-17 16:32 Udo van den Heuvel [this message]
2008-03-17 16:42 ` Emvy24control s/pidf input issue Takashi Iwai
2008-03-17 16:44 ` Udo van den Heuvel
2008-03-17 16:58   ` Takashi Iwai
2008-03-17 17:12     ` Udo van den Heuvel

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=47DE9D12.9030900@xs4all.nl \
    --to=udovdh@xs4all.nl \
    --cc=alsa-devel@alsa-project.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox