... | ... | @@ -7,4 +7,11 @@ Some ideas for the implementation of PulseAudio features |
|
|
make other paths inactive, possibly using UCM.
|
|
|
- Work on implementing the relevant modules
|
|
|
- we would want a client replacement library that speaks directly to PipeWire to make existing clients work
|
|
|
without changes. |
|
|
\ No newline at end of file |
|
|
without changes.
|
|
|
- we can share a volume/mute control between the mixer and the client, making volume changes very low overhead.
|
|
|
- we would like to have resampling and channel mapping done in the client. This makes it easier to implement the
|
|
|
server. Because we can use a PipeWire graph in the client this should not be too much trouble. Also:
|
|
|
+ most multimedia apps (vlc, GStreamer, mplayer, ..) implement resampling/channel mapping themselves and
|
|
|
always prefer the server to not touch the audio data.
|
|
|
+ latency and quality of the resampling is at the control of the client.
|
|
|
- we might have to renegotiate buffers when the sink/format changes. |
|
|
\ No newline at end of file |