Dear Maintainer,

I moved from PulseAudio (using also jack) to pipewire. I have a
firewire interface (M-Audio Firewire 410) here and everytime I launch
pavucontrol or qjackctl to adjust settings or connections tha system
hangs with a kernal panic message on any open X-terminal.

I used to use ardour to record instruments through the F410, with
qjackctl to set the connections properly. If the card is connected,
but not turned on, sometimes the system recognizes in duplicity some
of my soundcards. Here is the output of aplay -l

**** List of PLAYBACK Hardware Devices ****
card 0: F410 [FW 410], device 0: BeBoB [FW 410 PCM]
  Subdevices: 1/1
    Subdevice #0: subdevice #0
card 1: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 2: Generic_1 [HD-Audio Generic], device 0: ALC892 Analog [ALC892 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 2: Generic_1 [HD-Audio Generic], device 1: ALC892 Digital [ALC892 Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

and the output of arecord -l:

card 0: F410 [FW 410], device 0: BeBoB [FW 410 PCM]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 2: Generic_1 [HD-Audio Generic], device 0: ALC892 Analog [ALC892 Analog]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 2: Generic_1 [HD-Audio Generic], device 2: ALC892 Alt Analog [ALC892 Alt Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 3: i1300 [iSlim 1300], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

I can run some further tests/debugging here if it helps, but need some
guidance on how to do it. I also have pipewire-audio-client-libraries
and pipewire-media-session installed here.

Thanks!

Best, Alexandre

Hello Alexandre,

My apologies for not responding earlier.

Do you still have these problems with pipewire or have they been solved
with the new versions?

Best,
Dylan

Hello, Dylan!

Things are going much better with the new releases: 996367 seems to be
solved, but 997915 persists. For the latter it seems to be something
like capturing sources with different sample rates (like 48Khz and
44Khz). This guess is due to the resulting sound: the "default"
recording device (as selected with pavucontrol - have pipewire, pulse
and jack installed here! more on this later) have nice sound and the
other sounds like playing a standard 33rpm vinyl in 45rpm (revealing my
age here) with a lot of clips.

To make things tidy and clean here I would like to know if there is a
way to keep just pipewire running here (over ALSA, probably) and if
there are some mixer software to use with pipewire (ffado-mixer stopped
working with M-Audio 410 here).

Best,
Alexandre

===============================================================================
Alexandre Lymberopoulos - lymber@gmail.com
===============================================================================

Alexandre, could you close this bug report as you told it to
be solved?

See https://www.debian.org/Bugs/Developer#closing
That is, if you know the version that fixed the issue, add the pseudo-
header
Version: <replace with the version that fixed the issue>
if you do not know the version, do not include this Version pseudo-
header.

If you know what fixed the bug tell in the email body.


and then send this email to 996367-done@bugs.debian.org to close this
bug.
 

Cheers,
Alban


On Fri, 18 Nov 2022 19:33:34 -0300 Alexandre Lymberopoulos <lymber@gmail.com> wrote:
be
my
stopped
=======================================================================
========
=======================================================================
========

Dear Alban,

Unfortunately I can't remember the exact point where the bug I reported
was solved, it was more than one year between my bugreport and the
answer of the maintainer, and almost five months from that answer to
your message.

I'll close this bug now. Thanks for writing.

Cheers, Alexandre

Package: pipewire-pulse

Dear all,

As mentioned in a message sent on Fri, 18 Nov 2022 19:33:34 -0300, the
bug reported under the number 996367 (version 0.3.38-2) seems to be
solved at that moment (version 0.3.60-1). I'm sorry but can't figure out
which version implemented the solution after so long.

I must express my gratitude for the guys here working hard on pipewire.

Best, Alexandre

Package: pipewire-pulse

Dear all,

As mentioned in a message sent on Fri, 18 Nov 2022 19:33:34 -0300, the
bug reported under the number 996367 (version 0.3.38-2) seems to be
solved at that moment (version 0.3.60-1). I'm sorry but can't figure out
which version implemented the solution after so long.

I must express my gratitude for the guys here working hard on pipewire.

Best, Alexandre