All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Tanu Kaskinen <tanuk@iki.fi>
Cc: alsa-devel@alsa-project.org, frederik <frederik@ofb.net>
Subject: Re: [alsa-devel] parameter for pulse device?
Date: Tue, 17 Sep 2019 14:55:50 +0200	[thread overview]
Message-ID: <s5himprulnt.wl-tiwai@suse.de> (raw)
In-Reply-To: <365e4bcc033c151076140471225db51c80808b7f.camel@iki.fi>

On Tue, 17 Sep 2019 14:51:01 +0200,
Tanu Kaskinen wrote:
> 
> On Tue, 2019-09-10 at 10:33 -0700, frederik@ofb.net wrote:
> > On Mon, Sep 09, 2019 at 07:52:24PM +0200, Takashi Iwai wrote:
> > > It depends on how pcm.pulse is defined.  If it's defined to take an
> > > argument, it can work like that.  (Or sometimes you may need to pass
> > > the argument explicitly like "pulse:{device=mointor}".)
> > > 
> > > The standard pcm.pulse definition provided in alsa-plugins repo
> > > doesn't take the argument, and that can be the reason.
> > 
> > Thank you Takashi. Would it be easy to change alsa-plugins so that it
> > takes an argument? Is there a chance that this change would be
> > accepted?
> > 
> > If you can point me to the section of code in e.g. "plughw" where
> > argument parsing is done, then I would probably end up modifying
> > alsa-plugins myself, just to simplify what I am doing.
> 
> This commit might be instructive:
> https://git.alsa-project.org/?p=alsa-lib.git;a=commitdiff;h=3c199a0d199f0fae78c9c1b19c11878a6134b3a8

Yes, thanks for pointing an example.

Now I took a quick look at the current code, and one remaining problem
is that there is no device parameter value corresponding to the
default (=NULL).  Maybe we should accept the string "default" to be
treated as NULL, for example.

Ditto for the server parameter.


thanks,

Takashi
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2019-09-17 12:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-04 16:47 [alsa-devel] parameter for pulse device? frederik
2019-09-09 17:52 ` Takashi Iwai
2019-09-10 17:33   ` frederik
2019-09-17 12:51     ` Tanu Kaskinen
2019-09-17 12:55       ` Takashi Iwai [this message]
2019-09-17 13:14         ` Tanu Kaskinen
2019-09-17 13:17           ` Takashi Iwai
2019-09-19 21:12             ` frederik
2019-09-20  7:35               ` Tanu Kaskinen
2019-09-20  7:44                 ` Takashi Iwai
2019-10-15 15:52                   ` frederik
2019-10-18  6:17                     ` Takashi Iwai
2019-10-18  6:41                       ` frederik
2019-09-12 15:42 ` [alsa-devel] How to check ALSA version in Linux kernel xinhui zhou
2019-09-15  9:33   ` Takashi Iwai
2019-11-15 23:28   ` [alsa-devel] Number of PCM instance (pcm device file) for one sound card xinhui zhou

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=s5himprulnt.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=frederik@ofb.net \
    --cc=tanuk@iki.fi \
    /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.