[Feature Request] Adding support to Pipewire? #397

q2dg · 2018-12-29T14:17:13Z

wwmm · 2018-12-29T14:23:47Z

Once it becomes the default in Arch Linux I will definitely try to make PulseEffects working on it. But I wonder if it will be possible. Last time I looked it seemed to me that the audio section of pipewire was still in its infancy. It is not clear to me how pipewire intends to deal with audio effects tools like PulseEffects. They have to provide means for us to intercept applications audio. I hope they implement this better than pulseaudio.

baerbock · 2018-12-30T17:50:22Z

@q2dg Fedora fiddlesticks will never become default in Arch Linux.

AsavarTzeth · 2019-02-23T14:41:58Z

One question; what do you mean by "the default in Arch Linux"? A major point of Arch Linux is that there are almost no defaults. You install the base package group upon first install, but then you can do whatever you want.

You can for example install the pulseaudio package, or not. It might be hard to avoid, since Arch Linux is mainly a binary distribution and many packages depend on it, but still.

wwmm · 2019-02-23T14:49:33Z

You can do almost anything you want. Fair enough. But as soon as you install any desktop over the base install the audio server installed as dependency is Pulseaudio and not Pipewire. It doesn't ask you which one you want. It installs Pulseaudio. And for a good reason. Some programs like Firefox expect Pulseaudio and not Pipewire to be there ~~and as far as I understood Pipewire still needs Pulseaudio for sound and Jack for low latency. It does not play audio on its own.~~

wwmm · 2019-02-23T14:58:17Z

It seems that they have some work on the audio side done https://github.com/PipeWire/pipewire/search?l=C&q=audio

wwmm · 2019-02-23T15:03:08Z

They probably still needs some compatibility layer for Pulseaudio only apps.

I took a look at their api and I could not see a way to replicate what I can do now in Pulseaudio. Things like redirecting apps audio to a custom sink, getting info about the apps playing(sampling rate, format,...), etc

wwmm · 2019-02-23T15:04:37Z

The good thing is that as GStreamer is a first class citizen for Pipewire I doubt we would need any change to the effects chain.

AsavarTzeth · 2019-02-23T15:32:44Z

Okay I completely trust your judgment on whether it is ready for your use cases. I just found that specific statement odd.

I did check my system by the way. It has both pulseaudio and pipewire installed and it does have a pipewire.socket unit that is listening by default. That is in my opinion as default as it gets.

user@host ~> systemctl --user list-unit-files | grep pipewire
pipewire.service                           disabled 
pipewire.socket                            enabled  
user@host ~> systemctl --user status pipewire.socket
● pipewire.socket - Multimedia System
   Loaded: loaded (/usr/lib/systemd/user/pipewire.socket; enabled; vendor preset: enabled)
   Active: active (running) since Sat 2019-02-23 07:43:38 CET; 8h ago
   Listen: /run/user/1000/pipewire-0 (Stream)
   CGroup: /user.slice/user-1000.slice/user@1000.service/pipewire.socket

AsavarTzeth · 2019-02-23T15:38:27Z

Also I'm quite sure that Pipewire does not currently replace the sound server component. It still uses PulseAudio for this, or so I have read. That is why both can be installed at the same time.

wwmm · 2019-02-23T15:47:26Z

At some point mutter and gnome-remote-desktop started to require pipewire as a dependency. I think this was the moment it was installed in my pc.

There is a interesting read here https://github.com/PipeWire/pipewire/wiki/PulseAudio and here https://github.com/PipeWire/pipewire/wiki/FAQ But it is not clear if this is still the current state

zipy124 · 2020-09-10T18:13:24Z

Its been about a year and a half and I was just wondering if there was an update to this?

Note to readers, the above wiki has moved from github to gitlab, now see: https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/FAQ and https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/PulseAudio

wwmm · 2020-09-10T22:26:20Z

Hello! There is no work being done in the Pipewire integration. Honestly it is not clear to me yet if it is even possible to do what we need in Pipewire. I will explain in a few words how PulseEffects applies effects. Maybe it will help a reader more familiar with Pipewire to tell if it evolved enough to our needs.

One of the first steps done now is creating a virtual output device. Or a null sink in Pulseaudio's words. In order to apply effects we move the audio app from the sound card to this virtual output device. The next step is telling GStreamer to get audio from this virtual output device. After the desired effects are applied by GStreamer we tell it to play the result to the sound card.

It is still unclear to me if third party apps have a way to redirect a given audio app sound to some kind of virtual device. Another important point is that different audio contents may have different sampling rate. So this virtual device has to choose a rate and resampling anything that is different. Pulseaudio does that for us. I do not know how Pipewire is handling this.

In my opinion we will have to wait till many audio applications start to use Pipewire directly. Then the answers to these questions might become clear. At this moment I do not see a point in using Pipewire api when audio applications are still talking directly to Pulseaudio.

wwmm · 2020-12-03T18:29:33Z

Today Arch Linux decided to replace Pulseaudio by Pipewire. I will save the time of PulseEffects users and say that PulseEffects is not working in Pipewire. Although Pipewire is a drop-in Pulseaudio replacement for most audio applications this only happens if the application does not need to load Pulseaudio modules. And at this moment PulseEffects relies on Pulseaudio null sinks to redirect applications. I am reading Pipewire API but so far I did not see how Pipewire intends to handle this task. And that doc is even more confusing than the one from Pulseaudio...

Long story short people replacing Pulseaudio by Pipewire may stay without PulseEffects for a while...

Digitalone1 · 2020-12-03T18:31:21Z

Can you please pin this issue?

And please @wwmm, write that statement also in the readme.

wwmm · 2020-12-03T18:32:31Z

Can you please pin this issue?

Done.

bmwalters · 2020-12-04T02:59:50Z

@wwmm Work in Pipewire to support module loading (e.g. via pactl load-module, and especially the null sink) started a month ago and work is ongoing.

I would suggest filing a bug on the Pipewire issue tracker for use cases that aren't working yet.

Edit: Of course to use this you must have the pipewire-pulse daemon running.

And to users I should point out that Pipewire allows using JACK applications and Pulse applications in the same graph. This means that you could use pro-audio effects plugins in a host such as JACK Rack, Carla, or Ardour and graphical routing via a patch bay like Patchmatrix or gjackctl.

Digitalone1 · 2020-12-04T08:04:09Z

And to users I should point out that Pipewire allows using JACK applications and Pulse applications in the same graph. This means that you could use pro-audio effects plugins in a host such as JACK Rack, Carla, or Ardour and graphical routing via a patch bay like Patchmatrix or gjackctl.

This is nice but, I think it's not really the same.

Probably I will be able to set up things on Pipewire to get the same plugins I'm using now on PulseEffects to work and play on my speakers.

Anyway PulseEffects best part is to configure easily audio effect without the need to know anything about calf, lsp, ladspa, lv2, pulseaudio and jack. Everything is in a graphical environment where every plugin has a nice and user friendly interface. And if I need to use a configuration made by another user, I can do it faster just loading its preset file.

So Pipewire is surely a good multimedia module to improve Linux system, but PulseEffects is still needed.

wwmm · 2020-12-04T14:06:25Z

Work in Pipewire to support module loading (e.g. via pactl load-module, and especially the null sink) started a month ago and work is ongoing.

This is good. The lack of module loading support is probably the only reason why Pipewire compatibility layer is not being enough to run PulseEffects right now. In any case I have already made my mind about using Pipewire native API instead of relying on the compatibility layer. Yesterday I created a new branch where I am replacing Pulseaudio API by the one from Pipewire https://github.com/wwmm/pulseeffects/tree/pipewire. But this is going to take much more time than I initially thought. The native PIpewire API is completely different.

@Digitalone1 for some reason Arch Linux is not forcing pipewire-pulse to be installed anymore. Maybe because I have installed and uninstalled it a few times since I started the port. Who knows...

Digitalone1 · 2020-12-04T21:22:55Z

@Digitalone1 for some reason Arch Linux is not forcing pipewire-pulse to be installed anymore. Maybe because I have installed and uninstalled it a few times since I started the port. Who knows...

I can't update if I don't install pipewire-pulse. Maybe I just need to install and uninstall it to reinstall pulseaudio?

Digitalone1 · 2020-12-04T21:40:40Z

I confirm that after installing pipewire-pulse, you can reinstall pulseaudio and pulseaudio-bluetooth, removing pipewire-pulse.

Digitalone1 · 2020-12-17T18:05:45Z

@wwmm I'm glad the porting to Pipewire is going forward.

Which are your plans for the project? Since it is interacting with Pipewire, I suppose "PulseEffects" will not be a suitable name for the application. Will you change it?

And what will it be about the old PulseEffects? I suppose it will be still adopted by other distributions that are not using Pipewire yet.

wwmm · 2020-12-18T14:05:10Z

Will you change it?

No. I thought about this when I started the port and it is not worth it. What will need change are statements like Audio effects for Pulseaudio applications. The name can stay PulseEffects.

And what will it be about the old PulseEffects?

I definitely do not have time to develop 2 PulseEffects. Once the PipeWire branch is ready it will be moved to master and a legacy branch will be created with the current code targeting Pulseaudio. But I have no intention to work on it after moving to PipeWire. Maybe a bugfix for some issue that is really serious. But nothing more.

Digitalone1 · 2020-12-18T16:32:49Z

@wwmm Okay, so after the next 4.8.4 release that will fix issues related to locale and equalizer plugin, I recommend to make a copy of the master branch into a new legacy branch.

Maybe new release for Pipewire could be 5.0.0 and eventually bug fixes to the old legacy version in the future could be backported into 4.8.4.1.

wwmm · 2020-12-20T18:07:31Z

The code in our PipeWire branch is almost fully functional

Effects can be applied both for the input and output of streams. Automatic usage of the current default device selected by the user should also be working. User's custom blocklist might be working too. I did not test it yet. Automatic preset loading still needs more work.

At some point in this week I will create a legacy Pulseaudio branch and move the code in PipeWire branch to the master.

wwmm · 2020-12-20T18:12:25Z

The avoid-resampling feature won't work. This part of PulseEffects code has already been ported. But as can be seen here https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/472 PipeWire devices still have their sampling rate locked to the default rate set in PipeWire configuration file. 48 kHz is the default value.

Digitalone1 · 2020-12-21T14:10:25Z

@wwmm you forgot to release the 4.8.4 version with the latest fixes.

I decided to not switch to Pipewire at the moment and remain on Pulseaudio, so I will use the legacy version. The project is very promising and with high potential, but It's also not mature yet and too soon to adopt it in my opinion. I think it's like Wayland in its first years. I started to use it only in the last months and only because I switched to Gnome.

I'm not able to maintain the code related to the audio server, but since it is stable I think to be able to backport at least future new plugins and severe bugfixes made to the master branch.

If I'll manage to do it, I'll update my repository and find a way to push inside the legacy branch.

wwmm · 2020-12-21T17:31:40Z

you forgot to release the 4.8.4 version with the latest fixes.

Done.

The project is very promising and with high potential, but It's also not mature yet and too soon to adopt it in my opinion

It is young. But I have to say my impressions about PipeWire have changed since I started the port. I was expecting it to be really far behind Pulseaudio in the audio department but from a developer point of view is actually quite close. And with an API that is more comfortable to work with. I have been using it daily and so far only minor issues. But I am not using bluetooth devices.

This is the legacy Pulseaudio branch https://github.com/wwmm/pulseeffects/tree/pulseaudio-legacy. Master is now on PipeWire.

tinywrkb · 2021-01-10T18:06:11Z

I have this working in Flatpak but I had to manually set the client permissions to make it work, maybe I'm doing something wrong.

pw-cli permissions <client-id> -1 0755

edit: That octal number does not make a lot of sense but it seems to work, trying other combinations broke Pipewire.

Here are my changes, note that the rtkit access is just for-the-record, it's broken (and reported).

wwmm · 2021-01-10T21:02:11Z

I do not set any permission to our client. So it should be whatever PipeWire sets as default.

tinywrkb · 2021-01-10T21:25:12Z

@wwmm The problem might be that Pipewire recognizes the app as Flatpak according to the wiki so the app doesn't get write permission.

$ pw-cli get-permissions 68

remote 0 node 68 index 0
  default: r-x-

Note the "pipewire.access": "flatpak"

$ pw-dump 68

[
  {
    "id": 68,
    "type": "PipeWire:Interface:Client",
    "version": 3,
    "permissions": [ "r", "w", "x", "m" ],
    "info": {
      "change-mask": [ "props" ],
      "props": {
        "pipewire.protocol": "protocol-native",
        "pipewire.sec.pid": 1039068,
        "pipewire.sec.uid": 1000,
        "pipewire.sec.gid": 1000,
        "module.id": 2,
        "object.id": 68,
        "default.clock.rate": 48000,
        "default.clock.quantum": 1024,
        "default.clock.min-quantum": 32,
        "default.clock.max-quantum": 8192,
        "default.video.width": 640,
        "default.video.height": 480,
        "default.video.rate.num": 25,
        "default.video.rate.denom": 1,
        "link.max-buffers": 64,
        "mem.allow-mlock": true,
        "cpu.max-align": 32,
        "application.name": "pulseeffects",
        "application.process.binary": "pulseeffects",
        "application.language": "en_US.UTF-8",
        "application.process.id": 2,
        "application.process.user": "*",
        "application.process.host": "*",
        "application.process.session-id": 1,
        "core.version": "0.3.19",
        "core.name": "pipewire-*-2",
        "pipewire.access": "flatpak"
      }
    }
  }
]

edit: maybe pw_client_update_permissions() will work?

diamondburned · 2021-01-19T02:55:21Z

I'm trying tip (commit 0b9ba07) at the moment, and PulseEffects doesn't seem to have any perceivable effect with the Equalizer on for me. pavucontrol reports my audio output, "PulseEffects Sink" and "PulseEffects Source". When I change mpv to use either of those, nothing observable happens except for some console errors:

Console Errors

(pulseeffects:11366): pulseeffects-WARNING **: 18:46:11.835: soe: rtkit: MakeThreadRealtime: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.RealtimeKit1 was not provided by any .service files

(pulseeffects:11366): pulseeffects-WARNING **: 18:46:11.836: soe: rtkit: MakeThreadRealtime: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.RealtimeKit1 was not provided by any .service files
[E][000020561.829940][remote-node.c:411 client_node_set_param()] node 0x7ff5345aa400: set_param Spa:Enum:ParamId:PortConfig (11) 0x55d8240: Input/output error

(pulseeffects:11366): pulseeffects-WARNING **: 18:46:20.597: pipe_manager: Remote error on id:48

(pulseeffects:11366): pulseeffects-WARNING **: 18:46:20.597: pipe_manager: Remote error message:error changing node state: Input/output error
[E][000020570.602078][remote-node.c:411 client_node_set_param()] node 0x7ff5345aa400: set_param Spa:Enum:ParamId:PortConfig (11) 0x55d8240: Input/output error
[E][000020597.474760][remote-node.c:411 client_node_set_param()] node 0x7ff5345aa400: set_param Spa:Enum:ParamId:PortConfig (11) 0x55d8240: Input/output error
[E][000020598.320771][remote-node.c:411 client_node_set_param()] node 0x7ff5345aa400: set_param Spa:Enum:ParamId:PortConfig (11) 0x55d8268: Input/output error

(pulseeffects:11366): pulseeffects-WARNING **: 18:46:58.165: pipe_manager: Remote error on id:66

(pulseeffects:11366): pulseeffects-WARNING **: 18:46:58.165: pipe_manager: Remote error message:error changing node state: Input/output error

I hope this is enough to describe the issue, but I can provide additional information if needed. For the record, the distro is NixOS.

Edit: After tinkering a bit with pw-jack carla, I have managed to make PulseEffects working with this configuration:

This led me to believe that maybe PulseEffects isn't doing the device setting properly (which the errors in the console may have to do with, but I'm not sure).

Edit: I should probably clarify what exactly fixed the issue: mpv was directly connecting to the sound card; I had to wire that to the PulseEffects Sink. This would cause an echo, so I needed to remove another link, but I forgot which. I also noticed that output_F{L,R} were wired to the sound card as well, which didn't seem to have the EQ applied, so I disconnected that and used output_FR-83 and output_FL-107.

wwmm · 2021-01-19T04:26:51Z

Based on the MakeThreadRealtime errors your system does not have RealtimeKit installed. If it is not available in your repositories disable Realtime in PulseEffects settings menu.

wwmm · 2021-01-19T04:29:25Z

It would also help to run in debug mode. Kill the current instance pulseeffects -q and restart it like this G_MESSAGES_DEBUG=pulseeffects pulseeffects. Among many things it will show which PipeWire version you are using. I have been testing with its master branch.

diamondburned · 2021-01-19T04:33:57Z

It would also help to run in debug mode. Kill the current instance pulseeffects -q and restart it like this G_MESSAGES_DEBUG=pulseeffects pulseeffects. Among many things it will show which PipeWire version you are using. I have been testing with its master branch.

Here is the debug output that I got from running your command. I've noticed that I'm getting the same output, but this time when I checked with carla, it seems that PulseEffects wasn't wired up to my sound card.

P/S: I have disabled real-time as you told me to.

Edit: It seems that wiring up PulseEffects Sink's playback_F{L,R} with .pulseeffects-wrapped's output_FL-115 and output_FR-113 (which is the default) caused a high-pitched whining noise.

Edit: For the record, here's the final working configuration:

wwmm · 2021-01-19T13:47:51Z

I think it will be better to open a new issue for your case. You should not be having so many g_dbus_proxy_new errors. This is a sign something is missing in your installation. But it seems to me that the main problem is the connection to .pulseeffects-wrapped.

From PulseEffects point of view .pulseeffects-wrapped is a stream output like any other. As Process All Outputs is enabled by default in our settings menu PulseEffects will try to move this stream to our virtual output device pulseeffects_sink. But pulseeffects_sink has only 2 inputs while .pulseeffects-wrapped has 4 outputs. This is probably the reason why PipeWire is showing a PortConfig error. And even if it worked this isn't what you want.

Your use case is too specific. Either you disable Process All Outputs in our setting and use the per application switch to enable effects for each app or we blocklist .pulseeffects-wrapped so we never try to apply effects to it. Is Carla the one creating .pulseeffects-wrapped? Does it always have this name?

wwmm · 2021-01-19T13:55:01Z

The blocklist is something you can try yourself. When a stream is shown in our applications section it has a button that allows it to be blocklisted

jtojnar · 2021-01-19T14:40:44Z

.pulseeffects-wrapped is just a Nix thing – we wrap programs using shell scripts to avoid the need to install stuff globally (no /usr).

This is what `pulseeffects` contains

$ cat /nix/store/rqhc7v0s02snshb4jpxzkl7gfi36v5qd-pulseeffects-4.8.4/bin/pulseeffects
#! /nix/store/dskh7v2h3ly3kdkfk3xmjlqql1zr0hnw-bash-4.4-p23/bin/bash -e
export GIO_EXTRA_MODULES='/nix/store/ff82al5hzs9lpdzgk8cjjzpxy6qhxx9h-dconf-0.38.0-lib/lib/gio/modules'${GIO_EXTRA_MODULES:+':'}$GIO_EXTRA_MODULES
export GIO_EXTRA_MODULES='/nix/store/ff82al5hzs9lpdzgk8cjjzpxy6qhxx9h-dconf-0.38.0-lib/lib/gio/modules'${GIO_EXTRA_MODULES:+':'}$GIO_EXTRA_MODULES
export GDK_PIXBUF_MODULE_FILE='/nix/store/azyzm1pc4w1vdg5mwiqazvg16fa5m6gg-librsvg-2.50.1/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache'
export XDG_DATA_DIRS='/nix/store/3a81krh4hb5kkl51kfvsprvjr9y393rl-gtk+3-3.24.24/share/gsettings-schemas/gtk+3-3.24.24:/nix/store/cv7wvlhb17l4d2ydq7k85na5b2vfyb3j-pulseaudio-14.0/share/gsettings-schemas/pulseaudio-14.0:/nix/store/0yxfy0mzq96l2bgcb2488f75x7fbb466-gsettings-desktop-schemas-3.38.0/share/gsettings-schemas/gsettings-desktop-schemas-3.38.0:/nix/store/rqhc7v0s02snshb4jpxzkl7gfi36v5qd-pulseeffects-4.8.4/share/gsettings-schemas/pulseeffects-4.8.4'${XDG_DATA_DIRS:+':'}$XDG_DATA_DIRS
export XDG_DATA_DIRS='/nix/store/rqhc7v0s02snshb4jpxzkl7gfi36v5qd-pulseeffects-4.8.4/share'${XDG_DATA_DIRS:+':'}$XDG_DATA_DIRS
export GST_PLUGIN_SYSTEM_PATH_1_0='/nix/store/yc5blhqcks8lrglcpacy1y0lnqg0kvr8-gstreamer-1.18.2/lib/gstreamer-1.0:/nix/store/yg4m4xzfzm0rbbp875v4ycj87b3mb01l-gst-plugins-base-1.18.2/lib/gstreamer-1.0:/nix/store/ps47p6b8xah0v29s632s5bm5adx08k2l-gst-plugins-good-1.18.2/lib/gstreamer-1.0:/nix/store/v4m26sv945ja030f965py10w9348b9kv-gst-plugins-bad-1.18.2/lib/gstreamer-1.0:/nix/store/yc5blhqcks8lrglcpacy1y0lnqg0kvr8-gstreamer-1.18.2/lib/gstreamer-1.0:/nix/store/yg4m4xzfzm0rbbp875v4ycj87b3mb01l-gst-plugins-base-1.18.2/lib/gstreamer-1.0:/nix/store/ps47p6b8xah0v29s632s5bm5adx08k2l-gst-plugins-good-1.18.2/lib/gstreamer-1.0:/nix/store/v4m26sv945ja030f965py10w9348b9kv-gst-plugins-bad-1.18.2/lib/gstreamer-1.0'${GST_PLUGIN_SYSTEM_PATH_1_0:+':'}$GST_PLUGIN_SYSTEM_PATH_1_0
export LV2_PATH='/nix/store/g63mn9sq3bzhsv6s0q9nzkg1l6818djv-calf-0.90.3/lib/lv2:/nix/store/7vlmmfdakavmky79bm4wbvknccpbpm2b-lsp-plugins-1.1.26/lib/lv2'
export LADSPA_PATH='/nix/store/gnclp3zw51j775gsmaj9yhr8r6855rph-rubberband-1.9.0/lib/ladspa:/nix/store/hby5pfmgwk28azh67idh5rzsq4f8nhqp-zam-plugins-3.13/lib/ladspa'
exec -a "$0" "/nix/store/rqhc7v0s02snshb4jpxzkl7gfi36v5qd-pulseeffects-4.8.4/bin/.pulseeffects-wrapped"  "$@"

wwmm · 2021-01-19T14:51:41Z

That is really confusing... Why is there no *-wrapped for mpv and Firefox in the image above?

If pulseeffects-wrapped is just our own stream with a different name because of the wrapping I would expect it to have only 2 output ports and not 4... Something does not make sense here...

wwmm · 2021-01-19T15:01:16Z

We have an internal blocklist that forbids us from trying to apply effects to ourselves. This check is based on PipeWire nodes name. Under normal circunstances our nodes are named pulseeffects. If Nix wrapping is changing this the whole problem is explained. A list of PipeWire's nodes can be obtained through the command pw-cli list-objects Node.

wwmm · 2021-01-19T15:13:34Z

@diamondburned the master branch was updated. It now sets the name of our nodes instead of letting PipeWire setting a default value to it. Maybe this is enough to fix the problem.

wwmm · 2021-01-20T15:46:26Z

I have just released 5.0.0. The first using PipeWire. It was a long and interesting journey. People interested on it can take a look at https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/472. Unless I have missed something all the features that can work on PipeWire are implemented. Let me know if forgot any. There are features that do not work or are bugged because of limitations/problems in Pipewire:

Preset auto loading works. But is bugged for headphones users because plugging/unplugging headphones is not a well supported operation in PipeWire at the moment https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/498
Resampling can not be avoided at the moment. What could be done on PulseEffects side is done. The code is there. But PipeWire still uses a fixed sampling rate on its devices. Once this changes on PipeWire PulseEffects will probably avoid-resampling automatically
We used to show which resampler is being used in each a stream. But as PipeWire has only one resampler this does not make sense anymore
The latency value shown in our titlebar is probably wrong. The reason can be seen here https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/30. pipewiresrc does not seem to be reporting its latency

PacoPemo · 2021-02-11T02:24:38Z

I managed to install Pipewire and Pulseeffects in Manjaro Gnome, and make it work, except when I reboot, convolver (for example), don't . Sound interrupts, laggy, ??? (can't explain).
It only happens with some effects. If I turn effects off, everything is ok.
Best regards, Pemo

wwmm · 2021-02-12T14:36:54Z

Sound interrupts, laggy, ??? (can't explain).

If you are able to record this it would help. In any case try to rrun PulseEffects in debug mode. Kill the current instance pulseeffects -q and restart it as G_MESSAGES_DEBUG=pulseeffects pulseeffects. Maybe something useful will be shown when the problematic plugins are enabled.

wwmm · 2021-02-27T01:38:43Z

We can close this

wwmm added the enhancement label Dec 29, 2018

AsavarTzeth mentioned this issue Feb 23, 2019

Flatpak App: Changing Priority Type, Niceness and Priority Has No Effect #445

Closed

wwmm mentioned this issue Dec 3, 2020

Version 4.8.2 kills sound when activated in Arch Linux #846

Closed

wwmm pinned this issue Dec 3, 2020

AlbinoGeek mentioned this issue Jan 12, 2021

Input plugins have no effect (Fedora 33) #872

Closed

wwmm mentioned this issue Feb 2, 2021

Question: Assistance with Flatpak and 5.0.0 #894

Closed

wwmm unpinned this issue Feb 27, 2021

wwmm closed this as completed Feb 27, 2021

wwmm mentioned this issue Apr 14, 2021

why move to pipewire? #945

Closed

[Feature Request] Adding support to Pipewire? #397

[Feature Request] Adding support to Pipewire? #397

Comments

q2dg commented Dec 29, 2018

wwmm commented Dec 29, 2018

baerbock commented Dec 30, 2018

AsavarTzeth commented Feb 23, 2019

wwmm commented Feb 23, 2019 • edited Loading

wwmm commented Feb 23, 2019

wwmm commented Feb 23, 2019

wwmm commented Feb 23, 2019

AsavarTzeth commented Feb 23, 2019 • edited Loading

AsavarTzeth commented Feb 23, 2019 • edited Loading

wwmm commented Feb 23, 2019

zipy124 commented Sep 10, 2020

wwmm commented Sep 10, 2020 • edited Loading

wwmm commented Dec 3, 2020 • edited Loading

Digitalone1 commented Dec 3, 2020 • edited Loading

wwmm commented Dec 3, 2020

bmwalters commented Dec 4, 2020 • edited Loading

Digitalone1 commented Dec 4, 2020

wwmm commented Dec 4, 2020

Digitalone1 commented Dec 4, 2020

Digitalone1 commented Dec 4, 2020 • edited Loading

Digitalone1 commented Dec 17, 2020

wwmm commented Dec 18, 2020

Digitalone1 commented Dec 18, 2020

wwmm commented Dec 20, 2020

wwmm commented Dec 20, 2020

Digitalone1 commented Dec 21, 2020 • edited Loading

wwmm commented Dec 21, 2020

tinywrkb commented Jan 10, 2021 • edited Loading

wwmm commented Jan 10, 2021

tinywrkb commented Jan 10, 2021 • edited Loading

diamondburned commented Jan 19, 2021 • edited Loading

wwmm commented Jan 19, 2021 • edited Loading

wwmm commented Jan 19, 2021

diamondburned commented Jan 19, 2021 • edited Loading

wwmm commented Jan 19, 2021 • edited Loading

wwmm commented Jan 19, 2021

jtojnar commented Jan 19, 2021

wwmm commented Jan 19, 2021

wwmm commented Jan 19, 2021 • edited Loading

wwmm commented Jan 19, 2021

wwmm commented Jan 20, 2021 • edited Loading

PacoPemo commented Feb 11, 2021

wwmm commented Feb 12, 2021

wwmm commented Feb 27, 2021

wwmm commented Feb 23, 2019 •

edited

Loading

AsavarTzeth commented Feb 23, 2019 •

edited

Loading

AsavarTzeth commented Feb 23, 2019 •

edited

Loading

wwmm commented Sep 10, 2020 •

edited

Loading

wwmm commented Dec 3, 2020 •

edited

Loading

Digitalone1 commented Dec 3, 2020 •

edited

Loading

bmwalters commented Dec 4, 2020 •

edited

Loading

Digitalone1 commented Dec 4, 2020 •

edited

Loading

Digitalone1 commented Dec 21, 2020 •

edited

Loading

tinywrkb commented Jan 10, 2021 •

edited

Loading

tinywrkb commented Jan 10, 2021 •

edited

Loading

diamondburned commented Jan 19, 2021 •

edited

Loading

wwmm commented Jan 19, 2021 •

edited

Loading

diamondburned commented Jan 19, 2021 •

edited

Loading

wwmm commented Jan 19, 2021 •

edited

Loading

wwmm commented Jan 19, 2021 •

edited

Loading

wwmm commented Jan 20, 2021 •

edited

Loading