pipewire issueshttps://gitlab.freedesktop.org/pipewire/pipewire/-/issues2022-09-24T11:18:49Zhttps://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2676[Bluetooth] Regression: HFP/HSP profile is unavailable until restart2022-09-24T11:18:49Zcodethief[Bluetooth] Regression: HFP/HSP profile is unavailable until restart- PipeWire version (`pipewire --version`): 0.3.48
- Wireplumber version: 0.4.8-4
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Ubuntu 22.04.1 LTS
- Desktop Environment: none (XServer with i3)
- Kernel ve...- PipeWire version (`pipewire --version`): 0.3.48
- Wireplumber version: 0.4.8-4
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Ubuntu 22.04.1 LTS
- Desktop Environment: none (XServer with i3)
- Kernel version (`uname -r`): 5.15.0-47-generic
- BlueZ version (`bluetoothctl --version`): 5.64
- `lsusb`:
```
$ lsusb
…
Bus 003 Device 005: ID 8087:0026 Intel Corp. AX201 Bluetooth
…
```
- Bluetooth devices:
```
$ bluetoothctl devices
Device 00:1B:66:0D:6C:39 MOMENTUM 3
Device 00:1B:66:F2:AD:24 MOMENTUM TW 2
Device F4:B6:88:8C:14:1D Poly VFOCUS2 Series
```
## Description of Problem:
This seems to be a regression of #503 or #1683. Depending on the position of the stars and the state of the universe as a whole, HFP/HSP profile/codecs are available for my Poly Voyager Focus 2 or they are not. Correspondingly, if they are not available, Wireplumber will also not automatically switch to HFP when connecting to a Teams or Zoom meeting. (When they are available this works fine.) Restarting Wireplumber (`systemctl --user restart wireplumber`) usually fixes this issue temporarily. I had experienced the same issue before, though, when I was still using pipewire-media-session, so this is why I'm filing the bug with PipeWire.
Note that the issue is not restricted to the Poly Voyager Focus 2. I have had this issue with my other Bluetooth headsets (Sennheiser Momentum 3, Sennheiser Momentum True Wireless 2 – see above) as well.
## How Reproducible:
Unclear. It happens every now and then.
# Additional Info (as attachments):
- `pw-dump > pw-dump.log` (while HFP is working/available): [pipewire-pw-dump-hfp-working.log](/uploads/d068046960f91705c0227798c55ced1f/pipewire-pw-dump-hfp-working.log)
- `pw-dump > pw-dump.log` (while HFP is not working/unavailable): [pipewire-pw-dump-hfp-not-working.log](/uploads/64d6d225de1c88b5eb3af7b0b37dc6e1/pipewire-pw-dump-hfp-not-working.log)
- Bluetooth debug log, see [here](https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/Troubleshooting#bluetooth): Will provide this as soon as I can reproduce the issue reliably.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2675Enabling wireplumber makes microhpne dissappear2022-09-07T21:08:16ZTomáš HnykEnabling wireplumber makes microhpne dissappearI installed pipewire followign this guide: https://pipewire-debian.github.io/pipewire-debian/#add-the-launchpad-ppa
When I enabled wireplumber with
systemctl --user disable --now pipewire-media-session.service
systemctl --user ...I installed pipewire followign this guide: https://pipewire-debian.github.io/pipewire-debian/#add-the-launchpad-ppa
When I enabled wireplumber with
systemctl --user disable --now pipewire-media-session.service
systemctl --user enable --now wireplumber.service
My microphone stops working and stops being visible to all applications using pipewire. Reversing the commands above fixes the situation.
`arecord --duration=2 --format=dat --device=hw:0,0 test-mic.wav` records sound though.
I am on Lenovo X1 Extreme gen 2 and on Kubuntu 22.04
I am not ruling out I did something stupid to my sound configuration, but I am not aware of anything. I installed the latest release of Alsa from github (I was trying to test a feature I suggested from that release) and I poked around wireplumber configuration files but I think I have not changed anything as I truthfully didn't know what I was looking at. I am on 0.3.57.r4.gf957435-1~ubuntu22.04 but this was also happening with the previous release.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2672Audio completely glitching out when audio is stopped and started again.2023-09-22T10:48:23ZAustin AllmanAudio completely glitching out when audio is stopped and started again.I have encountered this problem in 2 separate occasions. The first time was in chrome when I was writing tool in javascript to capture my screen and audio and play it back so that I could do a browser-discord screen capture with audio. I...I have encountered this problem in 2 separate occasions. The first time was in chrome when I was writing tool in javascript to capture my screen and audio and play it back so that I could do a browser-discord screen capture with audio. If I disconnected the mic that the page was capturing and playing back using qjackctl BEFORE connecting a new source to that input it would completely glitch out. I was able to work around this and everything was good.
The situation I cannot work around however is using UxPlay to mirror my iphone screen. UxPlay functioned absolutely perfectly in pulse but I tried it again after having switched to pipewire and it is having the exact same problem as above except there is literally nothing I can do to prevent it. Every time my phone stops outputting audio for even a second the audio gets COMPLETELY screwed up when it resumes.
Here is a video of what is happening in UxPlay
https://www.youtube.com/watch?v=BeI1MQwQ4xg
If anyone has any suggestions on things I can try on my end to fix this or if there is any further information I can provide to help in diagnosing the issue let me know.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2669USB Camera always opened2024-02-04T16:24:42ZGuilhem LettronUSB Camera always openedWhen digging for consumption on my laptop.
I see that my camera was 100% on, making use of USB bus.
Digging, I see that was pipewire that was opening `/dev/video0` all the time (even if not used):
```
$ powertop
100,0% ...When digging for consumption on my laptop.
I see that my camera was 100% on, making use of USB bus.
Digging, I see that was pipewire that was opening `/dev/video0` all the time (even if not used):
```
$ powertop
100,0% Device USB device: Integrated_Webcam_HD (CN03GGY48LG0016CB21WA01)
$ fuser /dev/video0
/dev/video0: 2473
$ ps 2473
PID TTY STAT TIME COMMAND
2473 ? S<sl 4:37 /usr/bin/pipewire
```https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2658PipeWire creates a fake microphone which causes issues2022-09-05T08:13:34ZArtur RudenkoPipeWire creates a fake microphone which causes issues<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
<!-- If you can, test also with Pulseaudio and list `pulseaudio --version`. -->
- pulseaudio doesn't create the fake microphon...<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
<!-- If you can, test also with Pulseaudio and list `pulseaudio --version`. -->
- pulseaudio doesn't create the fake microphone (pulseaudio 16.1-1)
- PipeWire version (`pipewire --version`):
Compiled with libpipewire 0.3.56
Linked with libpipewire 0.3.56
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Arch Linux
- Desktop Environment: KDE
- Kernel version (`uname -r`): 5.19.3-arch1-1
- BlueZ version (`bluetoothctl --version`):bluetoothctl: 5.65
- `lsusb`:
```
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 1ea7:1005 SHARKOON Technologies GmbH Gaming Mouse
Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. KB212-B Quiet Key Keyboard
Bus 001 Device 006: ID 8087:0026 Intel Corp. AX201 Bluetooth
Bus 001 Device 005: ID 048d:5702 Integrated Technology Express, Inc. ITE Device
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
```
- Bluetooth devices:
```
Device 5C:FB:7C:59:43:AD JBL TUNE205BT
```
## Description of Problem:
When there's no microphones, pipewire creates a fake one (with name "*output_name* + *MAC adress* + ad2p.sink.monitor"), which streams audio from desktop. It also causes bluetooth headphones to not switch profile to Headset Unit, because it thinks there's already another microphone and it's unnecessary. I thought it could be some program or script which I tried in past and it changed config, but removing everything pipewire related in ~/.config and ~/.local/state didn't help
## How Reproducible:
### Steps to Reproduce:
1. Open discord (or any other chromium based app with microphone support)
2. In voice settings, there's a fake microphone (in my case it's "alsa_output.pci-0000_00_1f.analog_stereo.monitor")
3. Connect bluetooth headphones and open voice channel
4. It will change the input to something like "bluez_output.5C:FB:7C:59:43:AD.a2dp_sink.monitor"
### Actual Results:
Profile is not automatically switched to Headset Unit because there's a fake input device and it think profile switching is unnecessary. However, it works perfectly after switching to this profile manually, and after that, fake microphone disappears.
### Expected Results:
There's no fake input device and profile switches automatically
# Additional Info (as attachments):
- `pw-dump > pw-dump.log`: [pw-dump.log](/uploads/b391f07fad236c006663ebc8ef229656/pw-dump.log)
- Bluetooth debug log, see [here](https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/Troubleshooting#bluetooth): [pipewire-bluez.log](/uploads/7b7ec76d97b6e144354e2228e68c0bd1/pipewire-bluez.log)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2657USB soundcard crakling ( bit redux ) and then no audio. Ports switch on their...2022-12-14T09:03:02ZCcUSB soundcard crakling ( bit redux ) and then no audio. Ports switch on their own
pipewire
Compiled with libpipewire 0.3.56
Linked with libpipewire 0.3.56
Manjaro Linux
KDE plasma
5.19.1-3-MANJARO
## Description of Problem:
When playing with audio inputs->processing->output, after a random a...
pipewire
Compiled with libpipewire 0.3.56
Linked with libpipewire 0.3.56
Manjaro Linux
KDE plasma
5.19.1-3-MANJARO
## Description of Problem:
When playing with audio inputs->processing->output, after a random amount of time there is a screech sound after which the sound turns off. Sounds like bit reduction at times or ringing.
Then usually after that the outputs switch. Normally motu mk4 output to main would be on playback_AUX0, but it changes to playback_AUX16 (not the connections but when manually patching it to 16 17 the sound its there till it crashes again)
Same goes for the capture port, it varies between capture_AUX0 and capture_AUX16
## How Reproducible:
Install pipewire-* , setup the configs. Fire up Carla at 128/48000. Play for a bit and wait for the crashes to happen
### Actual Results:
Audio breaks partially (distorsion , ringing...) or completely and switches AUX
# Additional Info (as attachments):
- `pw-dump > pw-dump.log`:[pw-dump.log](/uploads/a066d5acaf30ba94b19c1ccaf00350af/pw-dump.log)
![image](/uploads/60f8d7f9e831a0659b6e550fa7540279/image.png)
![image](/uploads/e924e8ab76622e02805496b8d089c6db/image.png)
```
lsusb
Bus 001 Device 006: ID 1bcf:2c6e Sunplus Innovation Technology Inc. Laptop Integrated WebCam HD
Bus 001 Device 005: ID 0489:e046 Foxconn / Hon Hai BCM20702A0
Bus 001 Device 004: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth
Bus 001 Device 003: ID 07fd:0005 Mark of the Unicorn UltraLite-mk4
Bus 001 Device 002: ID 8087:8000 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
inxi -A
Audio:
Device-1: Intel Haswell-ULT HD Audio driver: snd_hda_intel
Device-2: Intel 8 Series HD Audio driver: snd_hda_intel
Device-3: Mark of the Unicorn UltraLite-mk4 type: USB
driver: snd-usb-audio
Sound Server-1: ALSA v: k5.19.1-3-MANJARO running: yes
Sound Server-2: PipeWire v: 0.3.56 running: yes
```
Tried to use the configs, changing sample rate & buffer. nothing seems to work.
I've also noticed how plasma-pa appears and disappears when opening the volume control panel on KDE
Tried also to compile from the repository with no difference
### some logs from journal
```
Aug 24 11:45:03 xTx pipewire[1681]: jack-device 0x55708d224318: can't open client: Input/output error
Aug 24 11:45:06 xTx pipewire[1681]: spa.loop: 0x55708d0fe0b0: failed to read timer fd 15: Resource temporarily unavailable
Aug 24 11:45:06 xTx pipewire[1681]: spa.loop: 0x55708d0fe0b0: failed to read timer fd 15: Resource temporarily unavailable
Aug 24 11:45:09 xTx pipewire[1681]: spa.loop: 0x55708d0fe0b0: failed to read timer fd 15: Resource temporarily unavailable
Aug 24 11:45:57 xTx pipewire[1681]: spa.loop: 0x55708d0fe0b0: failed to read timer fd 15: Resource temporarily unavailable
Aug 24 11:46:09 xTx pipewire[1681]: spa.alsa: hw:1,0: follower delay:51 target:512 thr:128, resync
Aug 24 11:48:11 xTx pipewire[1681]: spa.alsa: hw:1,0: follower delay:80 target:512 thr:128, resync
Aug 24 11:48:11 xTx pipewire[1681]: spa.alsa: hw:1,0: follower delay:128 target:512 thr:128, resync
Aug 24 11:48:11 xTx pipewire[1681]: spa.alsa: hw:1,0: follower delay:800 target:512 thr:128, resync
Aug 24 11:48:11 xTx pipewire[1681]: spa.loop: 0x55708d0fe0b0: failed to read timer fd 15: Resource temporarily unavailable
```
Please tell me if I can provide any further details since I would love to work with my motu ultralite mk4 on my systemhttps://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2656AptX Adaptive Bluetooth codec support2023-03-20T19:24:31ZRobbert van der HelmAptX Adaptive Bluetooth codec supportIs there any status on AptX Adapative support? I searched through this repo and issue tracker on GitLab but I didn't get any hits. I just got some Beyerdynamic Free BYRDs for use with the Steam Deck, and enabling the low latency mode on ...Is there any status on AptX Adapative support? I searched through this repo and issue tracker on GitLab but I didn't get any hits. I just got some Beyerdynamic Free BYRDs for use with the Steam Deck, and enabling the low latency mode on my phone before connecting them to the Deck does bring the latency down a lot, but they still use the regular AptX profile. Right now PipeWire supports AptX and the deprecated AptX-LL and AptX-HD codecs. What needs to be done for PipeWire to support AptX Adaptive?https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2653No sound in most apps after re-assigning speakers sink to headphones port (Ma...2022-09-06T10:23:47ZLaurențiu NicolaNo sound in most apps after re-assigning speakers sink to headphones port (Matebook 14s hack)This is a weird one, I don't even know how to phrase the title. I've got a laptop on my hands which has some issues with the jack detection: it's "inverted", so that the audio plays in the speakers only when a jack is inserted.
The Arch...This is a weird one, I don't even know how to phrase the title. I've got a laptop on my hands which has some issues with the jack detection: it's "inverted", so that the audio plays in the speakers only when a jack is inserted.
The Arch wiki has [a nice workaround](https://wiki.archlinux.org/title/Huawei_MateBook_14s#PulseAudio):
```
pactl set-sink-port alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__hw_sofhdadsp__sink '[Out] Headphones'
```
(the port name might be different on PipeWire)
I haven't tried this in PulseAudio, but with PipeWire it _almost_ works. I can hear the "volume changed" sounds when dragging the volume slider in `pavucontrol`, but no other apps can play sound. I don't remember exactly if I can't move the apps to the sink, or if I can but there's no sound.
Tested on Fedora 36 (PipeWire 0.3.56).https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2645Crackling sound sound if input/output devices are the same2023-08-01T18:10:29ZRobin FourcadeCrackling sound sound if input/output devices are the same- PipeWire version:
```
pipewire
Compiled with libpipewire 0.3.56
Linked with libpipewire 0.3.56
```
- Distribution and distribution version: `Pop!_OS 22.04 LTS`
- Desktop Environment: `GNOME 42.2`
- Kernel version (`uname -r`): `5.18.10...- PipeWire version:
```
pipewire
Compiled with libpipewire 0.3.56
Linked with libpipewire 0.3.56
```
- Distribution and distribution version: `Pop!_OS 22.04 LTS`
- Desktop Environment: `GNOME 42.2`
- Kernel version (`uname -r`): `5.18.10-76051810-generic`
## Description of Problem:
I have a Rode NT-USB I use as both input and output device.
I also have a StreamCam webcam I use only as a camera, but it also has a (bad) microphone.
If I use my Rode as both output (analogue) and input (digital), I get a horrible crackling sound. However, if I switch the input source to the StreamCam, I get a crystal clear sound. Sometimes, the crackling doesn't happen when I switch the device, but when I start using it in any app.
I've had this issue for a few weeks now, didn't have it before. I guess it came after an update, but I'm not sure when.
Any idea from where it could come from ?
Thanks
[pw-dump.log](/uploads/7cf25c3b5eb7ccb5c5df88b461750247/pw-dump.log)
Here's pw-top output, I don't know if it helps.
`pw-top` with **no** crackling issue:
```
S ID QUANT RATE WAIT BUSY W/Q B/Q ERR NAME
! 28 0 0 0.0µs 0.0µs 0.00 0.00 0 Dummy-Driver
! 29 0 0 0.0µs 0.0µs 0.00 0.00 0 Freewheel-Driver
! 39 0 0 0.0µs 0.0µs 0.00 0.00 0 Midi-Bridge
! 48 0 0 0.0µs 0.0µs 0.00 0.00 0 v4l2_input.pci-0000_2d_00.3-usb-0_2_1.0
! 54 0 0 0.0µs 0.0µs 0.00 0.00 0 alsa_output.pci-0000_2b_00.1.hdmi-stereo
55 2048 48000 61.9µs 4.2µs 0.00 0.00 0 alsa_output.usb-RODE_Microphones_RODE_NT-USB-00.analog-stereo
74 3307 44100 9.4µs 44.2µs 0.00 0.00 0 + Firefox
! 56 0 0 0.0µs 0.0µs 0.00 0.00 0 alsa_input.usb-RODE_Microphones_RODE_NT-USB-00.iec958-stereo
! 32 0 0 0.0µs 0.0µs 0.00 0.00 0 alsa_input.usb-046d_Logitech_StreamCam_86A5FA25-02.analog-stereo
! 53 0 0 0.0µs 0.0µs 0.00 0.00 0 alsa_output.pci-0000_2d_00.4.iec958-stereo
```
And **with** crackling issue:
```
S ID QUANT RATE WAIT BUSY W/Q B/Q ERR NAME
! 28 0 0 0.0µs 0.0µs 0.00 0.00 0 Dummy-Driver
! 29 0 0 0.0µs 0.0µs 0.00 0.00 0 Freewheel-Driver
! 39 0 0 0.0µs 0.0µs 0.00 0.00 0 Midi-Bridge
! 48 0 0 0.0µs 0.0µs 0.00 0.00 0 v4l2_input.pci-0000_2d_00.3-usb-0_2_1.0
! 54 0 0 0.0µs 0.0µs 0.00 0.00 0 alsa_output.pci-0000_2b_00.1.hdmi-stereo
55 512 48000 26.1µs 2.8µs 0.00 0.00 0 alsa_output.usb-RODE_Microphones_RODE_NT-USB-00.analog-stereo
74 3307 44100 5.6µs 10.0µs 0.00 0.00 0 + Firefox
90 1024 48000 14.8µs 2.9µs 0.00 0.00 0 + Brave
83 512 48000 17.7µs 1.3µs 0.00 0.00 0 + Brave
56 256 48000 13.1µs 0.2µs 0.00 0.00 0 alsa_input.usb-RODE_Microphones_RODE_NT-USB-00.iec958-stereo
100 480 48000 6.6µs 3.1µs 0.00 0.00 0 + Brave input
! 32 0 0 0.0µs 0.0µs 0.00 0.00 0 alsa_input.usb-046d_Logitech_StreamCam_86A5FA25-02.analog-stereo
! 53 0 0 0.0µs 0.0µs 0.00 0.00 0 alsa_output.pci-0000_2d_00.4.iec958-stereo
```https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2643Issue with profile and volume on Pop_OS using USB interface2022-11-18T13:33:07ZVivantartIssue with profile and volume on Pop_OS using USB interfaceHi!
Something weird is happening when I'm using PopOS with Pipewire(0.3.56) + Wireplumber(0.4.11) or below.
I can't select Pro Audio profile even through pavucontrol. It detects my interface like Direct or Line A/Line B
My Behringer UM...Hi!
Something weird is happening when I'm using PopOS with Pipewire(0.3.56) + Wireplumber(0.4.11) or below.
I can't select Pro Audio profile even through pavucontrol. It detects my interface like Direct or Line A/Line B
My Behringer UMC204HD works with Pro Audio profile on Ubuntu (even with upstream ppa), Fedora, etc. but Pop_OS is the only one that can't use pro audio.
I have to choose Line A instead Direct profile because after reboot my volume will be very low even showing 100% everywhere if Direct profile is set.
After switch between profile volume works properly, but if I restart wireplumber service while using Direct profile the volume issue come back.
Where should I start?
I always had Pro Audio set and working wonderfully.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2641Streaming over ROC delays audio by a full second2023-06-08T13:29:13ZBart RibbersStreaming over ROC delays audio by a full secondAs the title says. Both the server and client are running PipeWire with ROC support enabled. They connect to each other just fine and audio plays, but delayed by a full second. A bit strange for a protocol that's supposed to enable real-...As the title says. Both the server and client are running PipeWire with ROC support enabled. They connect to each other just fine and audio plays, but delayed by a full second. A bit strange for a protocol that's supposed to enable real-time audio streaming :sweat_smile:https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2640Focusrite Scarlett 18i20 Gen 1 output disappeared Jack2022-08-14T04:55:42ZSymdebFocusrite Scarlett 18i20 Gen 1 output disappeared JackFor some reaon today all the outputs of this audio interface did not show up in Jack graph anymore. (the whole playback section did not show up). Though, The input section was visible. Stop/starting PW, rebooting the system, changing USB...For some reaon today all the outputs of this audio interface did not show up in Jack graph anymore. (the whole playback section did not show up). Though, The input section was visible. Stop/starting PW, rebooting the system, changing USB ports, power on/off the device etc..nothing worked. An 18i20 Gen 2 interface did show up it's in and outputs and worked. Reverted back to legacy jack to be able to use the audio interface again. Ubuntu 22.04 Low latency. Linux H3 5.15.0-46-lowlatency #49-Ubuntu SMP PREEMPT Thu Aug 4 18:56:09 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2632Ability to select webcam resolution2022-12-24T00:07:46Zmalaksyan64Ability to select webcam resolutionIt would be really useful if PipeWire provided an easy way to select a resolution/framerate or at least a flag to capture the highest possible.It would be really useful if PipeWire provided an easy way to select a resolution/framerate or at least a flag to capture the highest possible.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2622Microphone does not react to sound (but is detected and looks okay)2022-09-16T08:09:19ZKonstantin KharlamovMicrophone does not react to sound (but is detected and looks okay)- PipeWire version:
```
pipewire
Compiled with libpipewire 0.3.56
Linked with libpipewire 0.3.56
```
- Distribution and distribution version: *Fedora Linux 36 (Workstation Edition)*
- Desktop Environment: *Plasma + i3*
- Kernel...- PipeWire version:
```
pipewire
Compiled with libpipewire 0.3.56
Linked with libpipewire 0.3.56
```
- Distribution and distribution version: *Fedora Linux 36 (Workstation Edition)*
- Desktop Environment: *Plasma + i3*
- Kernel version: *5.18.15-lqx2.0.fc36.x86_64*
## Description of Problem:
Works with PulseAudio, so a PipeWire-specific problem.
Opening `pavucontrol` and going to "Input Device" would reveal a "Internal Microphone". It has a noise-slider below, which wobbles, as if it detects a micro noise. But then, if you start making actual noise, that slider won't react to it at all.
Needless to say, Skype detects no sound as well.
Workaround: going back to PulseAudio makes it work.
### Steps to Reproduce:
1. Open `pavucontrol` and go to "Input Device" tab
2. Start watching the noise-slider, which wobbles a bit
3. Make noise by clapping your hands
### Actual Results:
The slider will remain low as if nothing happening
### Expected Results:
The slider would go up as you making noise
# Additional Info (as attachments):
- `pw-dump > pw-dump.log`: [pw-dump.log](/uploads/bd24c2e955bebbcb37050e034175fffd/pw-dump.log)
- the system is a new week-old Fedora 36 installation
- laptop: Lenovo ideapad 320-15ISKhttps://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2619USB devices sometimes play back noise or loud and distorted audio2024-01-15T12:12:24ZNiklāvs KoļesņikovsUSB devices sometimes play back noise or loud and distorted audioSometimes USB audio devices will produce noise (presumably either white or pink) which is often highly unpleasant and potentially dangerously loud. It's been encountered by multiple people, though only officially mentioned in #2614 (but ...Sometimes USB audio devices will produce noise (presumably either white or pink) which is often highly unpleasant and potentially dangerously loud. It's been encountered by multiple people, though only officially mentioned in #2614 (but there might be more mentioned somewhere else).
The known:
1. noise volume is likely correlated with the PCM volume of the relevant device
2. the intended audio signal can often be heard either "over" or "under" the noise
3. people reporting this all seem to have either explicitly allowed multiple sample rates or are implicitly using them due to SPA ALSA plugin thinking the HW can't use the one configured rate, so the device gets reconfigured at some point (#2620)
4. the noise can suddenly begin in the middle of a stream that has played without user interruption for for 1-2 minutes
5. all reported devices that exhibit this issue have so far been USB devices
6. at least at default log level no obvious or corroborating error messages have been observed or reported
7. sometimes (possibly due to a HW node reconfigure) the stream and subsequent device node suspend will clear the fault but most often the only solution is to execute `systemctl --user restart pipewire{,-pulse}.socket`
8. the noise plays even when there is no active client stream until the ALSA HW node itself is closed by PW (and it may resume once the node is re-opened without PW/WP daemon restart)
This is likely a bug in a lower layer such as the driver or even FW/HW itself but perhaps PW can do things differently to avoid triggering it, so it's probably better than not having any official issue at all.
As of early 2023 I'm now mostly getting loud and distorted or maybe clipping audio instead of the noise (in late 2022 it was also modulating the noise). I'll tentatively consider it part of the same issue as the two seem to confound and probably happen together.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2618Issue with teamspeak sound output and pipewire 0.3.562023-11-09T11:37:24ZEmmanuel PacaudIssue with teamspeak sound output and pipewire 0.3.56- pipewire 0.3.56-1
- updated fedora 36
- GNOME
- Teamspeak from flathub
- kernel 5.18.13-200.fc36.x86_64
## Description of Problem:
I have a hard time to make Teamspeak works with a Jabra speaker and pipewire 0.3.56
Almost every time,...- pipewire 0.3.56-1
- updated fedora 36
- GNOME
- Teamspeak from flathub
- kernel 5.18.13-200.fc36.x86_64
## Description of Problem:
I have a hard time to make Teamspeak works with a Jabra speaker and pipewire 0.3.56
Almost every time, I'm not able to make Teamspeak emit any sound to my Jabra Speak 510 speaker. It works fine with the integrated audio output of my Dell Latitude 5300 laptop. Microphone always work fine, either the integrated one, or the Jabra one.
When I'm selecting either Analog Jabra 510 or Digital Jabra 510 in GNOME settings, then launch Teamspeak, I have noticed 2 things:
- the log is filled with `pipewire[6250]: spa.alsa: iec958:1: snd_pcm_avail after recover: Relais brisé (pipe)` lines
- the output test in GNOME settings application does not work. When I click on one of the 2 test buttons, nothing happen, until I disconnect the Jabra speaker (The test sound is emitted as soon as the Jabara is disconnected, I don't have to click again on the test button).
Downgrading to pipewire 0.3.49 (dnf downgrade pipewire) seemed to fix the issue.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2613ALSA: UCM - no hardware volume control for the private alsa-lib configuration2023-09-07T04:00:21ZJaroslav KyselaALSA: UCM - no hardware volume control for the private alsa-lib configurationThe ALSA UCM configuration can also offer the mixer devices with the private prefix. Those mixer devices (starting with `_ucmXXXX.`) works only in the context where the UCM handle is opened (similarly to the PCM devices). It seems that s...The ALSA UCM configuration can also offer the mixer devices with the private prefix. Those mixer devices (starting with `_ucmXXXX.`) works only in the context where the UCM handle is opened (similarly to the PCM devices). It seems that something is missing in the current code, because the hardware volume cannot be changed using those mixer devices:
Example:
```
Got PlaybackPCM for device Line2: _ucm0001.umc204hd_stereo_out:U192k,0,2,3
Got PlaybackMixer for device Line2: _ucm0001.default:U192k
```
spa-acp-tool:
```
Enable ucm device Line2
Activating path Line B
Path Line B (null), direction=1, priority=0, probed=yes, supported=yes, has_mute=yes, has_volume=yes, has_dB=yes, min_volume=0, max_volume=127, min_dB=-127, max_dB=0
Element 'Line B', direction=1, switch=1, volume=1, volume_limit=-1, enumeration=0, required=0, required_any=0, required_absent=0, mask=0x6, n_channels=2, override_map=00
Hardware volume ranges from -127.00 dB to 0.00 dB.
Fixing base volume to 0.00 dB
Using hardware volume control. Hardware dB scale supported.
Using hardware mute control.
New hardware volume: min:44649 max:44649
0: 44649
1: 44649
Check device Line1 conformance with 0 other devices
First device in combination, number 1
Port [Out] Line1 direction output, priority 200
Adding profile HiFi to port [Out] Line1.
>>>ld
device 0: direction:playback name:"Direct: hw:U192k: sink" prio:1000 flags:00000008 devices: "hw:U192k"
device 1: direction:capture name:"Direct: hw:U192k: source" prio:1000 flags:00000008 devices: "hw:U192k"
* device 2: direction:playback name:"HiFi: umc204hd_stereo_out:U192k,0,2,3: sink" prio:100 flags:0000000f devices: "umc204hd_stereo_out:U192k,0,2,3"
* device 3: direction:playback name:"HiFi: umc204hd_stereo_out:U192k,0,0,1: sink" prio:200 flags:0000000f devices: "umc204hd_stereo_out:U192k,0,0,1"
* device 4: direction:capture name:"HiFi: umc204hd_mono_in:U192k,0,1: source" prio:100 flags:0000000f devices: "umc204hd_mono_in:U192k,0,1"
* device 5: direction:capture name:"HiFi: umc204hd_mono_in:U192k,0,0: source" prio:200 flags:0000000f devices: "umc204hd_mono_in:U192k,0,0"
>>>set-volume 2 0.1
Set hardware volume: min:38326 max:38326
0: 38326
1: 38326
Requested volume: 38326
Got hardware volume: 39794
Calculated software volume: 63118 (accurate-enough=no)
*** volume HiFi: umc204hd_stereo_out:U192k,0,2,3: sink changed to 0.200005
```https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2604Line-In audio with pw-loopback gets extremely distorted2023-03-07T18:25:05ZZawakenLine-In audio with pw-loopback gets extremely distorted<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`): 0.3.56
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`...<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`): 0.3.56
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): "Arch Linux"
- Desktop Environment: XMonad
- Kernel version (`uname -r`): 5.18.14-zen1-1-zen
## Description of Problem:
When using Line-In from another device to get playback from them (Line-In plugged into Monitor with PS5 audio for example), with pw-loopback the audio from Line-in gets extremely distorted/choppy. Especially when having pavucontrol/obs open.
## How Reproducible:
Every time I use pw-loopback or helvum/other patchbays to link the Line In to my sound output. Does not happen at all with arecord, to record my Line-In
### Steps to Reproduce:
1. Start pw-loopback and select right device in pavucontrol/link line-in to output device in a patchbay
2. Start playback on connected device.
3. Wait a few seconds.
### Actual Results:
Audio is completely distorted/choppy, especially when having pavucontrol/obs/any other recording program open.
### Expected Results:
Audio from line in being looped back to my output device sucessfully, without distortion or any choppiness.
# Additional Info (as attachments):
- [pipewire-dump.log](/uploads/f5c784efca41e6412eabdacfeaef67e5/pipewire-dump.log)
- **OBS RECORDING VOLUME WARNING, I'D RECOMMEND LESS THAN 20% SOUND**
- ![2022-07-27_14-09-02](/uploads/f8a89fc84c906dfe61d2db68cdaa8aad/2022-07-27_14-09-02.mp4)
The "Line In from Gigabyte Motherboard" is this device in `arecord -l`
```
card 2: Generic [HD-Audio Generic], device 0: ALC1220 Analog [ALC1220 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
```
Edit: removed the arecord file because of possible copyright, the OBS recording is the same song, but it is very distorted, let me know if that is still an issue.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2601Crackling sound during high CPU load in QEMU/KVM VM solved by reducing proces...2022-07-29T07:32:32ZVladimir GaristovCrackling sound during high CPU load in QEMU/KVM VM solved by reducing process niceness (nice-level -10)- PipeWire version (`pipewire --version`):
```
pipewire
Compiled with libpipewire 0.3.56
Linked with libpipewire 0.3.56
```
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Arch Linux
- Desktop Environment:...- PipeWire version (`pipewire --version`):
```
pipewire
Compiled with libpipewire 0.3.56
Linked with libpipewire 0.3.56
```
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Arch Linux
- Desktop Environment: KDE Plasma
- Kernel version (`uname -r`): 5.15.55-2-lts
## Description of Problem:
I've struggled with audio issues in QEMU/KVM for a long time. When the CPU is stressed by the VM, for example by playing a game, the audio starts to crackle. Recently I noticed that the crackling also applies to sounds produced by the host OS. This made me realise that the issue probably is not with the communication between the VM and pipewire as I suspected but with something else. So I decided to try reducing pipewire's process niceness by 10. It worked. It's not ideal, there still are ocasional crackles but only once every couple of minutes and during VM startup. Problem solved, right? Yeah, sort of, but I noticed this in `journalctl -b`:
```
Jul 26 16:48:33 vladoPCarch systemd[755]: Started PipeWire Multimedia Service.
Jul 26 16:48:33 vladoPCarch systemd[755]: Started Multimedia Service Session Manager.
Jul 26 16:48:33 vladoPCarch pipewire[1054]: mod.rt: RTKit error: org.freedesktop.DBus.Error.ServiceUnknown
Jul 26 16:48:33 vladoPCarch pipewire[1054]: mod.rt: could not set nice-level to -11: No such file or directory
Jul 26 16:48:33 vladoPCarch pipewire[1054]: mod.rt: RTKit error: org.freedesktop.DBus.Error.ServiceUnknown
Jul 26 16:48:33 vladoPCarch wireplumber[1056]: RTKit error: org.freedesktop.DBus.Error.ServiceUnknown
Jul 26 16:48:33 vladoPCarch wireplumber[1056]: could not set nice-level to -11: No such file or directory
Jul 26 16:48:33 vladoPCarch wireplumber[1056]: RTKit error: org.freedesktop.DBus.Error.ServiceUnknown
Jul 26 16:48:33 vladoPCarch wireplumber[1056]: RTKit error: org.freedesktop.DBus.Error.ServiceUnknown
Jul 26 16:48:33 vladoPCarch wireplumber[1056]: RTKit error: org.freedesktop.DBus.Error.ServiceUnknown
Jul 26 16:48:33 vladoPCarch wireplumber[1056]: could not make thread 1059 realtime using RTKit: No such file or directory
Jul 26 16:48:33 vladoPCarch pipewire[1054]: mod.rt: RTKit error: org.freedesktop.DBus.Error.ServiceUnknown
Jul 26 16:48:33 vladoPCarch pipewire[1054]: mod.rt: RTKit error: org.freedesktop.DBus.Error.ServiceUnknown
Jul 26 16:48:33 vladoPCarch pipewire[1054]: mod.rt: could not make thread 1060 realtime using RTKit: No such file or directory
```
It appears that pipewire tries to set it's niceness even lower than what I set it to but it fails to do so. And there's this issue: #2034. Pipewire used to run with -11 niceness until someone complained and it was changed to 0. Perhaps there was a good reason to run with -11 niceness?
At this point I'm not sure what to do. I don't really have a problem as I'm happy to run pipewire with reduced niceness and managed to configure my system to set it automatically after login (more difficult than expected). I wished to inform you that reduced niceness fixes some crackling issues and you could just undo the changes in the commit that fixes issue #2034. However, you may have your reasons to not want low process niceness. If that's the case, should I open an issue about the crackling problem?https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2590Mic produces wind noise (Logitech G Pro X)2023-11-26T13:41:22ZLockBlock-devMic produces wind noise (Logitech G Pro X)<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`): pipewire 0.3.56
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os...<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`): pipewire 0.3.56
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Arch Linux
- Desktop Environment: Plasma 5.25.3
- Kernel version (`uname -r`): 5.18.12-arch1-1
## Description of Problem:
When using the USB DAC of my Logitech G Pro X (wired) the audio plays normally but the mic produces only a "wind" sound.
I switched to pulseaudio and it now works perfectly. I guess this issue is hardware related, but I wanted to leave a record of it as I found 0 related issues online.
## How Reproducible:
Try to record a sound with this hardware in any app (Discord, arecord, ...).
### Actual Results:
"Wind" sound or no sound.
### Expected Results:
Your recorded voice.