3 ms·
> long time Considering the age of Wayland it's not that long. Besides that, Pipewire is not part of the Wayland protocol. This means external protocols now ha
by sprash 5y ago
> long time
Considering the age of Wayland it's not that long. Besides that, Pipewire is not part of the Wayland protocol. This means external protocols now have to jump in fixing the deficiencies of Wayland.
- kaba0 5y agoNo, it means that a problem best solved elsewhere is solved.. elsewhere. Screen sharing is streaming, where audio is also relevant and the two have to be synced. It would be plain incorrect to solve the two thing separately.
- sprash 5y agoThe composited image of the desktop is only available to the compositor. Hence it needs to be solved at the compositor. Since Wayland is essentially nothing more than a multiprocess negotiation protocol for video memory access it is exactly the right place where it should be solved.
- kaba0 5y agoBut at the end pipewire does get the output from the compositor, doesn’t it? Not specifying a general API can be a good and a bad thing — see eg. the linux kernel’s stance on driver interfaces.