pipewire issueshttps://gitlab.freedesktop.org/pipewire/pipewire/-/issues2023-05-25T18:04:03Zhttps://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3245Pipewire vs. snd-usb-audio lowlatency vs Avantree Leaf2023-05-25T18:04:03ZJesse LittonPipewire vs. snd-usb-audio lowlatency vs Avantree Leaf<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`): compiled with 0.3.71
- Distribution and distribution version (`PRETTY_NAME` from `/...<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`): compiled with 0.3.71
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Ubuntu Mantic Minotaur (development branch)
- Desktop Environment: KDE Plasma
- Kernel version (`uname -r`): 6.3.3-060303-generic
## Description of Problem:
Using the Avantree Leaf USB audio device, there are issues with playback when using Pipewire (pipewire-pulse in my testing), *unless* I set lowlatency=0 in my snd-usb-audio module options. When lowlatency=0 is set, the issues described below go away.
Case 1: Apps hang initializing sound unless any other app is playing sound.
Case 2: Apps hang initializing sound when WINE apps are already running.
## How Reproducible:
100%
### Steps to Reproduce:
Case 1a:
1. Start the VICE Commodore 64 emulator (x64 or x64sc).
2. It will immediately hang after initializing sound (no error in terminal).
Case 1b:
1. Start playing sound with another app (I used the Plasma Advance Radio widget).
2. Start the VICE Commodore 64 emulator (x64 or x64sc).
3. App runs as expected - can even produce sound.
Case 2a:
1. Start any game via WINE.
2. Try to play a YouTube video in Chrome.
3. Chrome will never start the video.
Case 2b:
1. Close the WINE game.
2. Try to play a YouTube video in Chrome.
3. Chrome plays video fine.
### Actual Results:
Apps hang while initializing sound.
### Expected Results:
Apps should not block on sound, nor be blocked by by other apps that have initialized it.
# Additional Info (as attachments):
- `pw-dump > pw-dump.log`:https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1339Phone connected to BT audio-gateway does not show up correctly in pavucontrol2021-06-25T22:20:45ZhexchainPhone connected to BT audio-gateway does not show up correctly in pavucontrol## Bluetooth Radio, Bluetooth Headset, Desktop Environment, Distribution, Version (Bluez, Kernel, and PipeWire):
Adapter: 01:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX200 [8086:2723] (rev 1a)
BT device: Pixel 2 XL
Des...## Bluetooth Radio, Bluetooth Headset, Desktop Environment, Distribution, Version (Bluez, Kernel, and PipeWire):
Adapter: 01:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX200 [8086:2723] (rev 1a)
BT device: Pixel 2 XL
Desktop: KDE Plasma 5.22
Distribution: Arch
Versions:
```
bluez 5.59-2
linux-zen 5.12.12.zen1-1
pipewire 1:0.3.30-2
```
## Description of Problem:
I am using my computer as my mobile phone's audio output through Bluetooth A2DP, but the profile is not correctly exposed in PulseAudio tools.
`pavucontrol` shows a device with a single profile "Off", and doing anything to this device in the UI breaks audio connection until reconnecting.
`pactl` shows two profiles: `off` and `audio-gateway`, but the latter has 0 sinks and 0 sources, and it seems switching profiles does not have any effect.
## How Reproducible:
Always.
## Steps to Reproduce:
1. Connect a mobile phone to computer using Bluetooth, and make sure "Media audio" on the phone is turned on.
2. Open `pavucontrol` and switch to the "Configuration" page
## Actual Results:
Despite A2DP audio is working, the UI looks like the device is disabled:
![image](/uploads/c3752b7343cdfe2035821475852e6617/image.png)
## Expected Results:
The selection should at least contain the profile current in use.