From: Takashi Iwai <tiwai@suse.de>
To: Paul Davis <paul@linuxaudiosystems.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: s/pdif controls
Date: Mon, 10 Mar 2003 14:21:21 +0100 [thread overview]
Message-ID: <s5hel5f5pda.wl@alsa2.suse.de> (raw)
In-Reply-To: <200303081500.h28F0K405680@linuxaudiosystems.com>
At Sat, 8 Mar 2003 10:00:20 -0500,
Paul Davis wrote:
>
> how are users supposed to set various s/pdif bits?
>
> the existing control formats involve massive bitfields that are
> totally impenetrenable to almost everyone.
>
> what is the strategy here? if someone wants to turn the pro/consumer
> bit on/off, what are they supposed to do?
a good question - there has not been much discussions there.
the iec958 status bits are passed usually through AESx arguments of
iec958 (aka spdif) pcm interface. and i think it's a good way,
because it's general and applicable to different cards in a uniform
way.
so far, almost only AC3-passthru was the case which needs to change
such a configuration, and the status bits are likely known for such.
so, there was no big complans about this. but, surely the way above
is for end-users.
well, we'll need a kind of iec958-status-bit-composer, which is
implemented on envy24control. but i believe it should be a user-land
solution, anyway.
Takashi
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2003-03-10 13:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-08 15:00 s/pdif controls Paul Davis
2003-03-10 13:21 ` Takashi Iwai [this message]
2003-03-11 13:54 ` Paul Davis
2003-03-11 19:25 ` Dan Hollis
2003-03-11 20:59 ` Benny Sjostrand
2003-03-11 20:46 ` Dan Hollis
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=s5hel5f5pda.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=paul@linuxaudiosystems.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.