From: Ben Stanley <Ben.Stanley@exemail.com.au>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: SPDIF audio / non-audio bit
Date: Sat, 16 Aug 2008 00:45:33 +1000 [thread overview]
Message-ID: <1218811533.32652.33.camel@localhost> (raw)
In-Reply-To: <s5hmyjfzks2.wl%tiwai@suse.de>
On Thu, 2008-08-14 at 17:19 +0200, Takashi Iwai wrote:
> Some drivers have the independent PCM IEC958 status bits while many
> have only the default IEC958 status bits. In the former case, the
> driver resets automatically the status bits after closing the PCM
> stream. Your case is the latter one, which doesn't reset. In this
> case, usually alsa-lib takes the old setting back. But when the
> program crashes (or aborted unexpectedly), the new setting is kept
> even after that, as you described in the above.
Could you please clarify
'independent PCM IEC958 status bits' vs
'default IEC958 status bits',
perhaps by pointing out some drivers implementing each type?
>
> > Could someone set me straight here so that I can try to produce a
> > permanent fix for this?
>
> You can change the status easily via iecset program in alsa-utils.
I note here that iecset does not accept --device=hw:0,1 for example. Any
reason for this?
>
> Maybe it's safer to have an independent PCM iec958 setting on all
> drivers. But this requires the change in alsa-lib (system) config,
> i.e. it may cause an incompatibility with older alsa-lib configs.
> This is an only drawback, I think.
I will try to figure this out after I have validated and submitted my
44100Hz patch for ca0106.
Ben.
next prev parent reply other threads:[~2008-08-15 14:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-14 14:48 SPDIF audio / non-audio bit Ben Stanley
2008-08-14 15:19 ` Takashi Iwai
2008-08-15 14:45 ` Ben Stanley [this message]
2008-08-15 14:59 ` Takashi Iwai
2008-08-15 15:56 ` Ben Stanley
2008-08-15 16:01 ` Takashi Iwai
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=1218811533.32652.33.camel@localhost \
--to=ben.stanley@exemail.com.au \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.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.