No audio output #2952
Comments
A lot has changed between this version and the latest release
Based on the logs your attempt to update PipeWire still resulted in a very old release. EasyEffects may not be compatible with it anymore. |
|
I don't use flatpak or snap packages. I think the pipewire package has failed to update properly after adding the additional repository. 0.3.65 is the version in the debian repository, so I'll see what I can do about fixing that. Additionally, I was able to compile rnnoise without issue on debian, so I'll see what I can do about compiling easyeffects too. If I get this all working, I'll write up a debian-specific guide. Edit: There may be no need for any of the above, pipewire 1.0.3 is seemingly available in backports, so I may try this first |
|
OK, I now have Pipewire 1.0.3 alongside whatever is the most recent EasyEffects release, but putting this all together has been so very convoluted, and may actually break the licensing restrictions that prevent rnnoise being available for Debian. However, I can tentatively confirm that, at least for the ten or fifteen minutes I have had it installed, the latest versions of these packages appear to play nicely together on Debian - including passthrough and audio effects. In light of the horrendous way I had to make this work (which included forcibly breaking dependencies and installing from backports, possibly as a result of me installing from that repo which I am now going to edit from my original post, as well as installing rnnoise twice in two different ways), I'm of the opinion that it would be easier to petition whomever maintains Debian stable to expedite the release of newer versions. |
EasyEffects Version
7.0.0
What package are you using?
Other (specify below)
Distribution
Debian 12 (Bookworm)
Describe the bug
Under Debian 12, no audio is present when applications start outputting. Very occasionally, I might be able to get some output from Firefox when reloading a page that plays audio, but this is uncommon. So far on the KDE distribution of Debian, I have not been able to accomplish this - this issue was also present on Debian 12 xfce.
I have a USB DAC (a Cambridge Audio DACMagic 100), as well as the expected internal sound card. Neither of these sound devices produce audio. Manually selecting the DAC as the output device for the application source results in audio, but audio that has not been processed by easyeffects.
This hardware configuration functioned properly on the most recent releases of Manjaro and EndeavourOS, both arch-based distributions, complete with Pipewire and EasyEffects. I was able to add filters and effects, and observe their changes as expected.
I have followed the Pipewire installation instructions as provided on the Debian wiki here: https://wiki.debian.org/PipeWire
Additionally, I have tried an updated repository for pipewire and wireplumber (and associated packages for jack and alsa) here: https://github.com/pipewire-debian/pipewire-debianDO NOT RECREATE WHAT I DID, IT BREAKS PACKAGES HORRIBLY AND MAY RESULT IN SOME DE PACKAGES BEING REMOVEDNone of the steps above have resulted in audio working properly. Audio functioned normally prior to the installation of easyeffects - on both releases of Debian 12 (xfce and KDE).
In the EasyEffects log posted below, there are a significant number of entries that suggest an audio device may be busy, or that the context in which a pipewire listener is called is incorrect. The log covers a two or three minute period, after starting EasyEffects, playing some audio from Winamp, and then closing EasyEffects.
Debug Log
Debug Log
Additional Information
Here is a screenshot of qpwgraph, denoting the (terribly messy) connections between outputs, processing effects, and outputs:
Additionally, here is the list of audio elements as shown in the KDE audio devices applet, in the settings manager. This is during "playback" of an audio track from winamp.
The text was updated successfully, but these errors were encountered: