FS#75987 - [pipewire-jack] update breaks audio input with Scarlett 18i20 card

Attached to Project: Arch Linux
Opened by Iain (sebinho) - Friday, 23 September 2022, 11:42 GMT
Last edited by Toolybird (Toolybird) - Friday, 25 November 2022, 05:15 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

After a recent system update audio input on Scarlett 18i20 sound card no longer works with pipewire-jack 1:0.3.58-1. All the hardware inputs appear correctly in the PieWire graph, however when an input is connected to the input of a DAW (eg. Ardour) or other audio app (eg. Pd) no audio signal is received. I did not attempt to downgrade the package, however, replacing pipewire-jack with jack2 and making the correct connection with qjackctl solves the problem.

Additional info:
* package version(s)
pipewire-jack 1:0.3.58-1
* config and/or log files etc.
* link to upstream bug report, if any

Steps to reproduce:
sudo pacman -Syu
This task depends upon

Closed by  Toolybird (Toolybird)
Friday, 25 November 2022, 05:15 GMT
Reason for closing:  No response
Comment by Iain (sebinho) - Friday, 23 September 2022, 13:51 GMT
I have since tried downgrading to the cached pipewire-jack 1:0.3.56-1. This however did not fix the problem. I have not used audio input with my card for some months so perhaps a downgrade to an even earlier version is necessary.
Comment by Iain (sebinho) - Friday, 23 September 2022, 13:57 GMT
Comment by Toolybird (Toolybird) - Friday, 23 September 2022, 21:26 GMT
Have you reported this upstream? A quick search turned up these [1][2].

[1] https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2402
[2] https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2640
Comment by Iain (sebinho) - Saturday, 24 September 2022, 11:03 GMT
Thanks, no, I'll do that. I should mention that my card is a Scarlett 18i20 Gen 3. Also that I tried booting with the 5.15.69-1-lts kernel which didn't help.
Comment by Tom (TomRobinsonIO) - Saturday, 24 September 2022, 15:51 GMT
This sounds like it may be the same kernel issue that's being worked on here:

https://bugzilla.kernel.org/show_bug.cgi?id=216500

I submitted a similar issue to pipewire and was directed there.

https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2704
Comment by Toolybird (Toolybird) - Monday, 24 October 2022, 23:05 GMT
If this is the same issue as linked kernel bugzilla above, some folks there are saying this is fixed. Can you confirm?

Loading...