EasyEffects apply effects to Virtual Channels

[Kathund]

I have recently been experimenting with pipeweaver to allow having virtual channels of audio. Since it uses virtual channels it doesn't seem possible to get easyeffect to apply effects to the virtual channel. Since I rely on easyeffects a lot to be able to use both my inputs and outputs it makes any real chance of me being able to use pipweaver basically impossible.

Pipeweaver currently doesn't have LV2 plugin support but apparently it's coming. This might be able to fix some of the issues when it comes, but currently i'm looking for any ideas of if using pipewaver and easyeffect is currently possible

I have added a video that "hopefully" better explains/showcases the issues that I have since pipeweaver uses virtual channels

2026-01-22_15-30-33.mp4

[FrostyCoolSlug]

Hi there, I'm the developer of Pipeweaver. I use a lot of filters and virtual nodes to provide a 'streamer friendly' setup which is similar to the GoXLR, Steelseries Sonarr, Elgato Wavelink, etc, a more complex layout would be this:

Because all the mixing and routing is handled in software via pipewire, all the app nodes are virtual which seems to prevent them from being picked up by easyeffects. Is there an opportunity to allow an interaction with the virtual input nodes?

[wwmm]

Strange. We already take virtual sources into account https://github.com/wwmm/easyeffects/blob/master/src/tags_pipewire.hpp. If I understood correctly the idea is being able to use a virtual source as input device in EasyEffects. This was supposed to work. I wonder if there was a regression.

[wwmm]

all the app nodes are virtual which seems to prevent them from being picked up by easyeffects.

Do you want those nodes to be visible in EasyEffects Players and Recorders tabs? In these tabs we show Stream/Output/Audio and Stream/Input/Audio. In other words we only show streams there. Not input/output devices.

[FrostyCoolSlug]

The nodes are created as Audio/Sink and Audio/Source/Virtual, so my general expectation would be the have them work in the same way a physical device would (apologies, I'm not hugely familiar with how easy effects works under the hood). If they're supposed to work that way already, then it's certainly possible that there's a regression.

[wwmm]

The nodes are created as Audio/Sink and Audio/Source/Virtual

The ones created as Audio/Sink are visible in EasyEffects list of sinks. I installed pipeweaver and I see PipeWeaver Browser and PipeWeaver System there. But the one created as Audio/Source/Virtual is not in the source list indeed. I have to add this tag to the same places Audio/Source is.

[wwmm]

I've updated our master branch. Now pipeweaver virtual source is visible in EasyEffects source device list. There should be no difference between Audio/Source/Virtual and Audio/Source now. As I did not really understand how to use pipeweaver it would be nice if someone that does tested our master branch.

[Kathund]

I've updated our master branch. Now pipeweaver virtual source is visible in EasyEffects source device list. There should be no difference between Audio/Source/Virtual and Audio/Source now. As I did not really understand how to use pipeweaver it would be nice if someone that does tested our master branch.

I personally tried building from source but had issues (probs missing packages) but i asked a friend and apparently it works fine for them