06:27 <DemiMarieObenour[m]> The main reason for handling audio separately, IMO, is the much lower latency requirements.

06:28 <DemiMarieObenour[m]> That said, one could definitely tunnel PipeWire in Wayland arrays. However, this would require a compositor and client that did all of their rendering asynchronously, so that slow rendering could not cause audio glitches. It could also interfere with the use of realtime audio threads.

07:36 <qyliss> DemiMarieObenour[m]: will you be documenting all your findings somewhere? I'd love to read them.

17:21 <wlb> weston Merge request !712 opened by () pipewire: Drop support for 0.2 API https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/712

19:12 <DemiMarieObenour[m]> <qyliss> "Demi Marie Obenour: will you..." <- I have not done so yet, but I can start! Some of them are security vulnerabilities under embargo, but the rest I can make public on GitHub.

19:12 <qyliss> please do! :)

19:14 <DemiMarieObenour[m]> I can also use https://gitlab.freedesktop.org if that is a better choice.

19:14 <DemiMarieObenour[m]> Do these belong in the Wayland protocol documentation?

19:16 <qyliss> no idea — I'm no Wayland developer, just an interested onlooker :)

21:42 <wlb> wayland Issue #246 opened by () Proposal: Add a `destroy-with="request-name"` attribute for events that create objects https://gitlab.freedesktop.org/wayland/wayland/-/issues/246