Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crackly audio on PipeWire output #131

Open
ruby-R53 opened this issue May 18, 2024 · 3 comments
Open

Crackly audio on PipeWire output #131

ruby-R53 opened this issue May 18, 2024 · 3 comments

Comments

@ruby-R53
Copy link

For some reason, the PipeWire output is not working properly here. The sound is all crackly, and when I quit the player, I get these two lines:

'loop->recurse > 0' failed at ../pipewire-1.0.6/src/pipewire/thread-loop.c:426 pw_thread_loop_wait()
'this->recurse > 0' failed at ../pipewire-1.0.6/src/pipewire/thread-loop.c:63 do_unlock()

Running with -qq also reveals these other error messages that appear every time I pause and unpause the player:

*** pw_stream_set_active called from wrong context, check thread and locking: Operation not permitted
*** impl_ext_end_proxy called from wrong context, check thread and locking: Operation not permitted

Changing the sample rate has no effect, and then I have to choose a different audio output. I feel like this could be due to how PipeWire is configured in my host because of the Operation not permitted errors, but I'm not really sure.

@mmitch
Copy link
Owner

mmitch commented May 18, 2024

I'd guess that there are incompatibilities between pipewire 0.x and 1.x.
I'm using Debian Bookmark, so the pipewire plugin was developed and tested using pipewire 0.3.65.
We even have an #ifdef version guard in plugout_pipewire.c because the pipewire in the GitHub CI pipeline is even older than that.

@ruby-R53
Copy link
Author

ahh i see

@ruby-R53
Copy link
Author

any ideas so far?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants