From: Rene Herman <rene.herman@keyaccess.nl>
To: Alexander Indenbaum <alexander.indenbaum@gmail.com>
Cc: alsa-user <alsa-user@lists.sourceforge.net>,
alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: /usr/share/alsa/alsa.conf :and file extention
Date: Mon, 17 Mar 2008 13:31:08 +0100 [thread overview]
Message-ID: <47DE648C.4070401@keyaccess.nl> (raw)
In-Reply-To: <cab05a880803162035o1c4d077erf289dcae4371969f@mail.gmail.com>
On 17-03-08 04:35, Alexander Indenbaum wrote:
> On Mon, Mar 17, 2008 at 5:18 AM, Rene Herman <rene.herman@keyaccess.nl
> Don't do it there. Use /etc/asound.conf or $HOME/.asoundrc ...
>
>
> Generally I'd agree with you that $HOME/.asoundrc is way to go if it was
> my desktop workstation. But this is an embedded system, so I'd like to
> force it on system level.
As I said, use /etc/asound.conf
> Still it does not work ( I still use system alsa.conf though ).
That's the reason.
> You touching here an interesting point. How indeed I could get an PCM
> header?
You don't really need one if you know the format. Ie, with aplay (and
foo.wav being CD format):
aplay foo.wav
aplay -D hw:0 -f cd /tmp/pcm.out
Rene.
next prev parent reply other threads:[~2008-03-17 12:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-17 2:57 /usr/share/alsa/alsa.conf :and file extention Alexander Indenbaum
2008-03-17 3:18 ` [alsa-devel] " Rene Herman
2008-03-17 3:35 ` Alexander Indenbaum
2008-03-17 12:31 ` Rene Herman [this message]
2008-03-17 8:05 ` Takashi Iwai
2008-03-17 12:34 ` [alsa-devel] " Rene Herman
2008-03-17 15:07 ` Takashi Iwai
2008-03-17 16:01 ` [alsa-devel] " Rene Herman
2008-03-18 0:27 ` Alexander Indenbaum
2008-03-18 0:45 ` Lee Revell
2008-03-18 1:36 ` Alexander Indenbaum
2008-03-18 1:42 ` Rene Herman
2008-03-18 2:06 ` Alexander Indenbaum
2008-03-18 4:28 ` Alexander Indenbaum
2008-03-18 12:44 ` Rene Herman
2008-03-18 13:02 ` [alsa-devel] " Sergei Steshenko
2008-03-18 13:12 ` [Alsa-user] " Rene Herman
2008-03-18 13:15 ` [alsa-devel] " 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=47DE648C.4070401@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=alexander.indenbaum@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=alsa-user@lists.sourceforge.net \
/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