pipewire
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
pipewire [2025/10/10 22:09] – w6vvn | pipewire [2025/10/10 22:11] (current) – w6vvn | ||
---|---|---|---|
Line 13: | Line 13: | ||
</ | </ | ||
- | Other software, like VARA, fldigi, wsjtx ... may all be similarly instructed to use the " | + | Other software, like qsstv, fldigi, |
There is one caveat. A Pipewire-ALSA client typically declares its own name. If you have several direwolf instances running, such as in the case of multiple radios or even FX.25 and IL2P in the same passband, there will be no way to disambiguate which client is which. Therefore, they cannot be (reliably) configured to use a specific sound card or specific volume levels when using the same name. The solution is to use the PIPEWIRE_ALSA environment variable to override parameters of the Pipewire-ALSA plugin. For example, | There is one caveat. A Pipewire-ALSA client typically declares its own name. If you have several direwolf instances running, such as in the case of multiple radios or even FX.25 and IL2P in the same passband, there will be no way to disambiguate which client is which. Therefore, they cannot be (reliably) configured to use a specific sound card or specific volume levels when using the same name. The solution is to use the PIPEWIRE_ALSA environment variable to override parameters of the Pipewire-ALSA plugin. For example, |
pipewire.1760134198.txt.gz · Last modified: by w6vvn