* default pcm plugin
[not found] <1701875316957022429-webhooks-bot@alsa-project.org>
@ 2023-12-06 15:08 ` GitHub issues - opened
0 siblings, 0 replies; only message in thread
From: GitHub issues - opened @ 2023-12-06 15:08 UTC (permalink / raw)
To: alsa-devel
alsa-project/alsa-lib issue #371 was opened from sylware:
Is there a robust programming way to know if the canonical "default" pcm is actually a pipewire/pulseaudio/jack plugin? That at a device/pcm enumeration time, namely before any pcm is actually being configured.
I was thinking about the "configuration" API, but I am not that sure it "resolves" everything including user-specific/system-specific configurations (asound rc files and env variables).
Issue URL : https://github.com/alsa-project/alsa-lib/issues/371
Repository URL: https://github.com/alsa-project/alsa-lib
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2023-12-06 15:09 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <1701875316957022429-webhooks-bot@alsa-project.org>
2023-12-06 15:08 ` default pcm plugin GitHub issues - opened
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox