From: Tanu Kaskinen <tanuk@iki.fi>
To: frederik@ofb.net, Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: [alsa-devel] parameter for pulse device?
Date: Fri, 20 Sep 2019 10:35:59 +0300 [thread overview]
Message-ID: <7c81ae80233efb25b25f2d1f941e9c11acb3967b.camel@iki.fi> (raw)
In-Reply-To: <20190919211244.buu3d6ey4k2dxyul@localhost>
On Thu, 2019-09-19 at 14:12 -0700, frederik@ofb.net wrote:
> Thank you for the tips.
>
> I don't know if my input is still needed, but I figured out from
> looking at some of the syntax you linked to that I can put this in
> ~/.asoundrc and it does the job (this is what I had had in mind when
> I asked about "magic with macros", it is somewhat advanced for me):
>
> pcm.!pulse {
> @args [ DEV ]
> @args.DEV {
> type string
> default "default"
> }
> type pulse;
> device $DEV
> }
>
> Now I can set up a filter like this:
>
> ecasound -i alsa,pulse:mic -o alsa,pulse:monitor
>
> Is something like this going into the alsa-plugins repo?
I'm sure something like this will be accepted if you submit a patch. I
got the impression that Takashi isn't willing to write the patch
himself, and nor am I, so you're in the best position to make this
happen.
Note that
default "default"
doesn't do the intended thing with the current pcm_pulse.c code. With
the current code the plugin will request PulseAudio to use a device
named "default", which most likely won't exist and playback or
recording will fail. The plugin code needs to pass NULL as the device
name to pa_stream_connect_playback() and pa_stream_connect_record()
when it detects that the default device is requested, so you'll need to
modify pcm_pulse.c in order to make this work. Instead of "default" as
the special string in the configuration, I suggested using "".
--
Tanu
https://www.patreon.com/tanuk
https://liberapay.com/tanuk
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2019-09-20 7:37 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
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 [this message]
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=7c81ae80233efb25b25f2d1f941e9c11acb3967b.camel@iki.fi \
--to=tanuk@iki.fi \
--cc=alsa-devel@alsa-project.org \
--cc=frederik@ofb.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;
as well as URLs for NNTP newsgroup(s).