Dimitris Papaioannou

Quantum is reasonable on everything so there's no need to try other quantums in your config. It's most definitely a bug. Unrelated suggestion: You seem to be rerouting audio manually...

In fact, could you try with a JACK Input Client source next time? The code I'm suspecting to be the problem is pretty much the same in both, I want...

They should show up in qpwgraph if you have `pipewire-jack` installed

Taking a shot in the dark. Can you try with [this build](https://github.com/dimtpap/obs-pipewire-audio-capture/files/14123771/linux-pipewire-audio.zip)? Diff: ```patch diff --git a/src/pipewire-audio.c b/src/pipewire-audio.c index 95ee923..b43c936 100644 --- a/src/pipewire-audio.c +++ b/src/pipewire-audio.c @@ -177,7 +177,17 @@ static...

Can you try the latest commit? [Build here](https://github.com/dimtpap/obs-pipewire-audio-capture/files/14749334/linux-pipewire-audio-5c47e1a.tar.gz)

@oparada1988 `PIPEWIRE_LATENCY` is an [environment variable](https://wiki.archlinux.org/title/Environment_variables). The [PipeWire README](https://gitlab.freedesktop.org/pipewire/pipewire#usage) explains it.

Can you try with a build from [here](https://github.com/dimtpap/obs-pipewire-audio-capture/actions/runs/10677235821)? Under "artifacts"

This plugin requires the `--filesystem=xdg-run/pipewire-0` permission to be set for OBS Studio. Currently it is set by upstream, but it can be removed at anytime and break the plugin as...

> If Flatpak extensions can set additional flags on the host application then this can be considered They can't

Can someone having this issue check if OBS's PipeWire Screen/Window capture sources work properly?