From: Takashi Iwai <tiwai@suse.de>
To: Thomas Charbonnel <thomas@undata.org>
Cc: Jesse Chappell <jesse@essej.net>,
ALSA development <alsa-devel@alsa-project.org>
Subject: Re: Alsa handling of spdif bits (was Re: Questions to HDSP users)
Date: Mon, 09 Feb 2004 11:52:25 +0100 [thread overview]
Message-ID: <s5hn07s7ceu.wl@alsa2.suse.de> (raw)
In-Reply-To: <4023E72C.5040904@undata.org>
At Fri, 06 Feb 2004 20:12:44 +0100,
Thomas Charbonnel wrote:
>
> >> so I'm back with my
> >>question concerning amixer : all the 'value' fields of IEC ctls show a
> >>question mark. Is this a problem with the driver ? If not what would be
> >>the syntax to access those ctls ?
> >
> >
> > amixer doesn't handle IEC958 status properly.
> >
> >
>
> IIUC, this ctl is supposed to be used for example by DVD playing
> applications so that the fact they may temporary require the Non-Audio
> bit to be set for AC3 passthru does not interfere with the user settings ?
yes and no. these bits are set as the parameters of PCM hook plugin.
you can open an spdif PCM with parameters like
iec958:{AES0=XXX,AES1=XXX,AES2=XXX,AES3=XXX}
to pass the proper status bits (this will change "IEC958 Plaback PCM
Stream" usually). xine and mplayer pass these parameters at the open
time.
but my statement above means that amixer doesn't display/parse
correctly this data type (iec958). it's just a missing feature of
amixer. it'd be better if amixer handles it correctly.
> If so I'll keep this ctl and implement it properly.
>
> Anyway thanks for clarifying, it was much needed :)
well, this should be more better documented.
(the patch to the doc is also welcome, BTW ;)
ciao,
Takashi
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
next prev parent reply other threads:[~2004-02-09 10:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-28 15:29 Questions to HDSP users Thomas Charbonnel
2004-01-28 19:22 ` Jesse Chappell
2004-01-29 13:51 ` Alsa handling of spdif bits (was Re: Questions to HDSP users) Thomas Charbonnel
2004-02-05 14:34 ` Takashi Iwai
2004-02-05 19:08 ` Jesse Chappell
2004-02-06 11:22 ` Thomas Charbonnel
2004-02-06 11:53 ` Takashi Iwai
2004-02-06 13:14 ` Thomas Charbonnel
2004-02-06 13:32 ` Takashi Iwai
2004-02-06 19:12 ` Thomas Charbonnel
2004-02-09 10:52 ` Takashi Iwai [this message]
2004-01-29 14:34 ` Questions to HDSP users Justin Cormack
2004-02-05 1:04 ` alsa-devel
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=s5hn07s7ceu.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=jesse@essej.net \
--cc=thomas@undata.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 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.