[Pkg-utopia-maintainers] Bug#1025069: pavucontrol

[Lucas]

On Tue, 11 Apr 2023 14:30:38 +0200 Alban Browaeys
<alban.browaeys at gmail.com> wrote:
> Do you mean it disappeared from pavucontrol when you run JACK from
> ardour ?

Yes, that particular output option from pavucontrol disappeared after
running ardour, and then closing it (Gnome settings shows an empty
unselectable output).  After ardour is closed, jack automatically is
too, and pavucontrol once again displays STUDIO CAPTURE in
Configuration.

> What I meant is that you cannot run pipewire and jackd at the same time
> ? I cannot work as one will prevent the other from accessing the ALSA
> sound device.
> If you want to run JACK application whne running pipewire you can only
> do so by pipewire-jackd and disabling jackd.
> This is not a pipewire bug. jackd also cannot work if the sound device
> is already taken by an alsa program or any other daemon plugging to the
> alsa interface (pipewire, pulseaudio), it could work because for one
> pulseaudio aut suspend itself from time to time so the alsa sound
> device is free when so. But then when pulseaudio will resume and your
> jackd daemon is holding on the alsa sound device pulseaudio will not
> work. This is not supported (for pulseaudio you could use the pasuspend
> tool, still it is  hack).

Yes, I know this should be the case, but pulseaudio seems to be
graceful enough without me suspending it to run ardour's jack.  When
I'm done with that, I also don't have to stop suspending pulseaudio.

>
> Also:
> Gnome Settings Output Device contains nothing to select, while Input
> allows "Analog Input - STUDIO-CAPTURE" and "STUDIO-CAPTURE Pro". The
> only way to have output audio working is to use pavucontrol and select
> either of the STUDIO-CAPTURE Profile Configurations "Multichannel
> Output", or "Pro Audio".
> and:
> That "Multichannel Output" Profile disappeared after I ran JACK
> (ardour), and I only see again now on a fresh startup.
> seems to be two different issue. You should report both in two diffrent
> bug report else it the bug report will get confusing soon.
> My reply was about the second issue (which to me look like a normal
> behavior).
>
>
> For the first one, I am a bit confused. You mean that even in
> pavucontrol if you do not switch to the STUDIO-CAPTURE Profile
> Configurations "Multichannel Output", or "Pro Audio" you cannot set a
> sound output device?

Not quite.  It wasn't disabled before I set pavucontrol's
configuration, but all that was selectable in Gnome settings for
output was a Dummy Audio option, or something to that effect.

> If you bug report upstream you could try to run pipewire built from
> source (you just have to stop pipewire related systemd user services,
> ie systemctl --user stop pipewire.service, etc).
> Also there is a newer pipewire version 0.3.76 in Debian rc-buggy
> (experimental).

I might revisit this after reading up on how to pin experimental for
that one package, but for now I'll work on adding the other debugging
information you suggested, to the bug report.

Thanks for the suggestions!