Update to 0.3.30
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2021-29223a7ff9Please login to add feedback.
| 0 | 0 | Test Case PipeWire ALSA backend |
| 0 | 0 | Test Case PipeWire Bluetooth Devices |
| 0 | 0 | Test Case PipeWire Gnome Control Center |
| 0 | 0 | Test Case PipeWire Jack Applications |
| 0 | 0 | Test Case PipeWire Jack Midi Routing |
| 0 | 0 | Test Case PipeWire Pavucontrol Add Remove |
| 0 | 1 | Test Case PipeWire Pavucontrol Basics |
| 0 | 1 | Test Case PipeWire Pavucontrol Mixing |
| 0 | 0 | Test Case PipeWire Pavucontrol Recording |
| 0 | 0 | Test Case PipeWire PipeWire CLI |
| 0 | 0 | Test Case PipeWire PipeWire default |
| 0 | 0 | Test Case PipeWire Selected Applications Playback |
| 0 | 0 | Test Case PipeWire Video Conferencing |
This update has been submitted for testing by wtaymans.
This update's test gating status has been changed to 'failed'.
This update's test gating status has been changed to 'waiting'.
wtaymans edited this update.
This update's test gating status has been changed to 'failed'.
This update's test gating status has been changed to 'passed'.
It turns out that pulseeffects was causing most of my issues. I won't use that again.
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
Works.
This update has been submitted for stable by bodhi.
work here
Fixes Jack issues introduced in 0.3.29.
Ardour and qjackctl now function properly. It seems very stable so far. Only thing that appears off is the Jack latency reporting, especially when using Jamulus after Ardour. (Connected locally at ~60ms with a frame size of 64 is high, without Ardour it is ~20ms where it should be and sounds like ~10ms. With pipewire-jack-audio-connection-kit-0.3.28-1 it reports ~10ms.)
Ah, sorry. The new latency reporting doesn't seem to take into account when the Jack frame size is changed dynamically via dbus (I use Ardour). When changing it before launching new applications, they do see the (supposedly) correct latency (~10ms). Great release so far.
This update has been pushed to stable.