`pw-dump` output does not reflect changed parameters during runtime
I believe this is a regression in pipewire 1.0.2, as the issue does not happen with 1.0.1.
I use libpipewire-module-filter-chain
to load a ladspa plugin. I then use pw-dump
and pw-cli set-param
to programatically change settings of the ladspa plugins.
However, this stopped working in pipewire 1.0.2 (and 1.0.3). Using pw-cli set-param
to change a parameter works, but pw-dump
will still show the initial value of the parameter:
% pw-cli set-param 38 Props '{ params = [ "loudComp:Output volume (dB)" -10.00 ] }'
% pw-dump 38 | grep -A1 loudComp:Output
"loudComp:Output volume (dB)",
-20.000000, /* <-- XXX: should be -10.00 */
For reference, here is the expected behaviour in 1.0.1:
% pw-cli set-param 38 Props '{ params = [ "loudComp:Output volume (dB)" -10.00 ] }'
% pw-dump 38 | grep -A1 loudComp:Output
"loudComp:Output volume (dB)",
-10.000000,
% pw-cli set-param 38 Props '{ params = [ "loudComp:Output volume (dB)" -15.00 ] }'
% pw-dump 38 | grep -A1 loudComp:Output
"loudComp:Output volume (dB)",
-15.000000,