wwmm / easyeffects

Limiter, compressor, convolver, equalizer and auto volume and many other plugins for PipeWire applications
GNU General Public License v3.0
6.51k stars 269 forks source link

Intermittent startup warnings linking nodes #1793

Open vchernin opened 2 years ago

vchernin commented 2 years ago

I'm not sure if this is a real issue, so feel free to close if not.

On 6.3.0 but also 6.2.8 Flatpak I sometimes see:

(easyeffects:2): easyeffects-WARNING **: 10:46:32.365:  stream_output_effects.cpp:270    link from node 75 to node 105 failed

(easyeffects:2): easyeffects-WARNING **: 10:46:32.365:  stream_output_effects.cpp:270    link from node 75 to node 63 failed

(easyeffects:2): easyeffects-WARNING **: 10:46:32.365:  stream_output_effects.cpp:303    link from node 75 to output device 52 failed

or similar when starting up. It seems to only occur when Fireox is playing audio. There are no output effects being set.

With debug messages (a different run with different node numbers but it seems like the same issue):

(easyeffects:2): easyeffects-DEBUG: 10:49:23.484:   pipe_manager.cpp:1694   node 126 has no output ports yet. Aborting the link

(easyeffects:2): easyeffects-WARNING **: 10:49:23.484:  stream_output_effects.cpp:270    link from node 126 to node 92 failed
(easyeffects:2): easyeffects-DEBUG: 10:49:23.484:   pipe_manager.cpp:1694   node 126 has no output ports yet. Aborting the link

(easyeffects:2): easyeffects-WARNING **: 10:49:23.484:  stream_output_effects.cpp:270    link from node 126 to node 66 failed
(easyeffects:2): easyeffects-DEBUG: 10:49:23.484:   pipe_manager.cpp:1694   node 126 has no output ports yet. Aborting the link

(easyeffects:2): easyeffects-WARNING **: 10:49:23.484:  stream_output_effects.cpp:303    link from node 126 to output device 52 failed
(easyeffects:2): easyeffects-DEBUG: 10:49:23.486:   plugin_base.cpp:289 sie: output_level successfully connected to PipeWire graph
(easyeffects:2): easyeffects-DEBUG: 10:49:23.488:   plugin_base.cpp:289 sie: spectrum successfully connected to PipeWire graph

This is with PipeWire 0.3.56 on Fedora 37. Are the warnings serious? They don't since it seems like it is error handling according to the debug messages.

wwmm commented 2 years ago

node 126 has no output ports yet. Aborting the link

For some reason we did not have information about the node ports at the moment we tried to link. I haven't seen this in a long time. Was there lack of audio because of this? Or was the link automatically done later?