From: Takashi Iwai <tiwai@suse.de>
To: Abramo Bagnara <abramo.bagnara@libero.it>
Cc: Jaroslav Kysela <perex@suse.cz>,
Alsa dev List <alsa-devel@lists.sourceforge.net>
Subject: Re: Single process freeze when opening capture device
Date: Mon, 02 Jun 2003 13:09:20 +0200 [thread overview]
Message-ID: <s5hbrxgpwgv.wl@alsa2.suse.de> (raw)
In-Reply-To: <3ED60767.6060502@libero.it>
At Thu, 29 May 2003 15:13:11 +0200,
Abramo Bagnara wrote:
>
> Jaroslav Kysela ha scritto:
> > On Thu, 29 May 2003, Abramo Bagnara wrote:
> >
> >
> >>What about a "dir" field in common section of pcm configuration?
> >>
> >> dir STR # PCM allowed directions "playback", "capture", "both" (default)
> >
> >
> > I'd like to solve the problem with same names, but different
> > configurations for streams.
> >
> > I have an idea like:
> >
> > pcm.name {
> > ... global configuration ...
> > playback {
> > ... playback configuration ...
> > }
> > capture {
> > ... capture configuration ...
> > }
> > }
>
> I'm far from convinced that to have same name for different things is a
> good idea, and in this case I'd propose to have:
>
> pcmc.name {
> }
>
> pcmp.name {
> }
>
> then specifying different namespaces for different things.
>
> This also permits to leave current
> pcm.name {
> }
>
> unmodified (although with lower priority wrt pcmc and pcmp).
i would accept both ideas.
IIRC, the pcm is looked up through the definition in
/usr/share/alsa/alsa.conf, so if we have pcmc and pcmp definitions,
we'll need to rewrite (add) these look-up, too?
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
next prev parent reply other threads:[~2003-06-02 11:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-29 3:24 Single process freeze when opening capture device Arthur Peters
2003-05-29 7:10 ` Jaroslav Kysela
2003-05-29 8:56 ` Abramo Bagnara
2003-05-29 11:53 ` Jaroslav Kysela
2003-05-29 12:38 ` hdsp9652+alsamixer -> kernel panic d
2003-05-29 12:59 ` Paul Davis
2003-05-29 14:14 ` d
2003-05-29 15:32 ` Paul Davis
2003-05-29 15:57 ` Kai Vehmanen
2003-05-29 16:27 ` Paul Davis
2003-05-29 16:46 ` d
2003-05-29 17:14 ` Paul Davis
2003-05-31 11:15 ` Kai Vehmanen
2003-05-31 11:30 ` Jaroslav Kysela
2003-06-02 11:02 ` Takashi Iwai
2003-06-02 11:19 ` Kai Vehmanen
2003-05-29 17:27 ` Jaroslav Kysela
2003-05-29 17:44 ` Paul Davis
2003-05-29 13:13 ` Single process freeze when opening capture device Abramo Bagnara
2003-06-02 11:09 ` Takashi Iwai [this message]
2003-05-29 13:49 ` James Courtier-Dutton
2003-05-29 14:05 ` Jaroslav Kysela
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=s5hbrxgpwgv.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=abramo.bagnara@libero.it \
--cc=alsa-devel@lists.sourceforge.net \
--cc=perex@suse.cz \
/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.