Re: [Alsa-user] alsa-only applications (such as jitsi) via jackd
* Peter P. [2020-04-21 20:20]:
> * Clemens Ladisch via Alsa-user [2020-04-12
> 11:55]:
> > Peter P. wrote:
> > > Can I set pcm device names per application as defaults?
> >
> > If the application does not allow you to set the ALSA device name,
> > you have to replace the device definition that the application used
> > (probably "default").
> Thanks Clemens, just to make sure I get you right: Some applications do
> not allow me to set "PCM devices" but only cards? In that case I can
> only redefine default by changing/creating a .asoundrc?
>
> > It would be possible to create a device definition that reads an
> > environment variable (the "hw" device does this with ALSA_PCM_*),
> > but the "default" device does not do this.
> I am just making my way through alsa terminology, let me ask you if you
> mean a "PCM device" called hw, not the hw as a protocol for accessing
> cards?
I am replying to my last thread here to tell that I finally managed to
make a non-jackified application (jitsi meet application image in my
case) use jack. I did this by installing the libasound2-plugins Debian
package, which provides a jack plugin for alsa. Then I created an
.asoundrc with the below contents which points to the built-in soundcard
hw:0 as a default, but permits any environment variable (ALSAPP for me)
to change this assignment
pcm.!default{
type plug
slave.pcm {
@func getenv
vars [ ALSAPP ]
default "hw:0"
}
}
With jackd running I can now start any application prefixed with that
variable pointing to the jack plugin
$ ALSAPP=jack ffmuc-meet-x86_64.AppImage
If anyone sees something I could improve here I'd be glad to know.
Thanks for the help on this list!
cheers, P
___
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] alsa-only applications (such as jitsi) via jackd
* Clemens Ladisch via Alsa-user [2020-04-12 11:55]: > Peter P. wrote: > > Can I set pcm device names per application as defaults? > > If the application does not allow you to set the ALSA device name, > you have to replace the device definition that the application used > (probably "default"). Thanks Clemens, just to make sure I get you right: Some applications do not allow me to set "PCM devices" but only cards? In that case I can only redefine default by changing/creating a .asoundrc? > It would be possible to create a device definition that reads an > environment variable (the "hw" device does this with ALSA_PCM_*), > but the "default" device does not do this. I am just making my way through alsa terminology, let me ask you if you mean a "PCM device" called hw, not the hw as a protocol for accessing cards? Thanks again! P ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] alsa-only applications (such as jitsi) via jackd
Peter P. wrote: > Can I set pcm device names per application as defaults? If the application does not allow you to set the ALSA device name, you have to replace the device definition that the application used (probably "default"). It would be possible to create a device definition that reads an environment variable (the "hw" device does this with ALSA_PCM_*), but the "default" device does not do this. Regards, Clemens ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
[Alsa-user] alsa-only applications (such as jitsi) via jackd
Dear Alsa-list,
I had asked this on the Linux-Audio-Users a few days ago but am still
waiting for replies. I figured this question might even better suit this
list here, so please allow me to ask it here again
I am trying to use jack for alsa-only applications (jitsi application
image, chromium for videochat in my case) over jack. Following the guide
on https://jackaudio.org/faq/routing_alsa.html I installed the
libasound2-plugins Debian package, which includes the jack pcm plugin
for alsa. This plugin is activated by
/usr/share/alsa/alsa.conf.d/50-jack.conf as a hardware plugin without
conversions, meaning that it is tied to jack's sample rate and bit
resolution. I was able to create a "plug" device which takes care of
this conversion in an otherwise empty ~/.asoundrc as follows
pcm.jackconv{
type plug
slave { pcm "jack" }
hint {description "jack plugin with software conversions" }
aplay -L then lists this device. My next question is, how can I tell
applications to use this device? I want to avoid declaring it the
default in .asoundrc with an
pcm.!default{
type plug
slave { pcm "jack" }
hint {description "default jack plugin with software conversions" }
I found out that there is an environment variable ALSA_PCM_CARD= but
this can only set hardware devices but not pcm device names such as my
jackconv. Then I discovered ALSA_PCM_DEVICE and tried to start jitsi
with
ALSA_PCM_DEVICE=jackconv ~/bin/jitsi-meet-2.0.0-x86_64.AppImage
but no device "jackconv" shows up in jitsi nor are any jack ports
created for it.
Is there something I am doing wrong? Can I set pcm device names per
application as defaults?
Thanks for all ideas!
cheers, P
___
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user
