-
Notifications
You must be signed in to change notification settings - Fork 306
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
Warn about Pipewire's suspension of sinks might cause troubles #419
base: dev
Are you sure you want to change the base?
Conversation
Thanks for the enhancements. Run mkdir build -- Could NOT find HAMLIB (missing: HAMLIB_LIBRARY HAMLIB_INCLUDE_DIR) -- Configuring incomplete, errors occurred! |
Your new message is in the "not ARM" section so it would not be displayed on a Raspberry Pi. |
The inclusion of this new message into the not ARM section was intentional. I'm not entirely sure how often this message is actually shown on Pi and whether we are not hitting this error more often for some other reasons on Pi platform. I hit this error on both amd64 and Pi platform with PipeWire installed. Indeed, there is no other reason than this for not including it into the ARM section too. Regarding the solution - this is not actually an ALSA issue but rather a PipeWire/Wireplumber issue which is emulating ALSA interface for DireWolf. Solution here is to disable the power saving feature of PipeWire which is suspending audio output sinks after every few secs of inactivity, which then produces this bug in DireWolf when transmitting packets after such suspension. AFAIK such a change of WirePlumber settings cannot be done via any API from within DireWolf, but needs to be done by user, as is roughly described here: https://unix.stackexchange.com/questions/676846/how-do-i-disable-audio-sink-suspend-on-idle-using-wireplumber-in-fedora-35-so-th |
When using Direwolf with recent Linux distributions on amd64 and Pi with PipeWire audio subsystem with Wireplumber in its default settings, audio output sinks are being suspended after several seconds of inactivity, which results in slight delay while warming up again. This results in spitting
Transmit timing error: PTT is on XXXXX mSec too long
error message which is not very helpful. This pull request adds few more hints when running via ALSA subsystem.