Feature Request: Improve config parsing and feedback
Hello,
playing around with Pipewire is actually quite fun, once you understand the basics. Thanks a lot for making and continuing to work on it! :)
I'm still making some config mistakes tho, and I'm sure others do aswell. These aren't always obvious or caught/communicated by Pipewire, but important for a "solid" feeling software. Config management ist probably an area that could use a little improvement ;)
Concrete examples:
-
Forget the closing
]
for the nodes list in libpipewire-module-filter-chain'sfilter.graph
. The filter chain starts without complaint, but the sink will fail to show up (duh). Ideally the parser shold catch this kind of mistake, show an error and bail out. -
Definining a non-existent
node.target
in capture/playback props. Pipewire will silently ignore it and use the fallback sink instead. It would be nice to be notified of this situation in the log. -
As per Wiki, params may be set. However, using
pw-cli set-param
, you can e.g. set Int values for params that, according to their PropInfo, accept Float ranges. The tool should catch that and bail out instead of setting a bogus value. A friendly message like "add .0 to numbers to set them as Floats" would be the icing on the cake :) -
In the Wiki, a wrong command is listed. I would edit it, but I have no permissions.
pw-cli ls Modules
should bepw-cli ls Module
.pw-cli
should complain when an unknown type is requested. As of now, it silently returns an empty string with successful exit code. -
likely more
Cheers!