Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@keyaccess.nl>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-user <alsa-user@lists.sourceforge.net>,
	alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: [alsa-devel] /usr/share/alsa/alsa.conf :and file extention
Date: Mon, 17 Mar 2008 13:34:11 +0100	[thread overview]
Message-ID: <47DE6543.9000909@keyaccess.nl> (raw)
In-Reply-To: <s5hmyoxu66g.wl%tiwai@suse.de>

On 17-03-08 09:05, Takashi Iwai wrote:
> At Mon, 17 Mar 2008 04:18:15 +0100,
> Rene Herman wrote:

>> Don't do it there. Use /etc/asound.conf or $HOME/.asoundrc ...
> 
> Or /etc/asound.conf.  It's the additional place for the system-wide
> definitions.

That's what I said. What happened? Alexander also completely missed that...

>> Exactly why you need that slave definition I'm not sure either, but it seems 
>> you do.
> 
> The file plugin requires the slave for its configuration and as the
> timing source.  Using "null" is just to accept any config and feed the
> data as fast as possible.  If you need to save the data as if it's
> being played, use the kernel dummy driver as the slave.

I see, thanks.

>> Also note that /tmp/pcm.out will be headerless PCM and is recreated 
>> for individual opens. I don't believe there's an append mode or anything 
>> (and you'd need to make sure that everyone plays the same format) so not 
>> toot sure if this is what you need to have a catch all audio-sink...
> 
> Recently I added a new option "truncate" to file plugin.  As default,
> it's set to true (for compatibility reason), and the plugin overwrite
> the existing file if reopened.  When it's set to false, a new file is
> created with a different suffix (up to 1000 files) at each time.

That sounds useful...

Rene.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

  reply	other threads:[~2008-03-17 12:34 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
2008-03-17  8:05   ` Takashi Iwai
2008-03-17 12:34     ` Rene Herman [this message]
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=47DE6543.9000909@keyaccess.nl \
    --to=rene.herman@keyaccess.nl \
    --cc=alsa-devel@alsa-project.org \
    --cc=alsa-user@lists.sourceforge.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox