3 ms·

> only presents the option to capture the full screen Are you sure? I'm pretty sure I had two tabs, one for picking displays and other for picking windows. Pr

> only presents the option to capture the full screen Are you sure? I'm pretty sure I had two tabs, one for picking displays and other for picking windows. Pretty much like this: https://bug1675764.bmoattachments.org/attachment.cgi?id=9186238 https://bug1675764.bmoattachments.org/attachment.cgi?id=9186...

zamadatix 6y ago
Looking deeper into it (been meaning to anyways) it seems to be the typical Wayland compositor specific issue, and ironically I'm using ddevault's compositor sway. Pipewire doesn't seem to care what you send it but your second window looks to be part of xdg-desktop-portal-gtk if I'm not mistaken. Since I'm using sway/wlroots I need to use xdg-desktop-portal-wlr instead. In the FAQ for this package: "Will this let me share individual windows? No, only entire outputs. It would take significant work in wlroots, and likely a new protocol, to make this possible. A second rendering pass would be required, which would significantly reduce wlroots performance, so this may not be implemented any time soon (or ever). Will this let me share all of my outputs/displays at once? Not yet, no. It will likely never create a single stream that combines all of your outputs, but once we implement better output selection, there is no reason xdpw cannot create multiple simultaneous streams of different outputs." So it looks like I'm shit out of luck for quite a while on sway/wlroots. Looks like Gnome figured it out. Not sure about KDE.
- vetinari 6y ago
  Ah, that explains it. Yes, I'm running Gnome and xdg-desktop-portal-gtk. Thanks for the constructive and informative discussion.
- majewsky 6y ago
  For your reference, these are the issues to subscribe to if you're interested in following the discussion as it's taking place: https://github.com/emersion/xdg-desktop-portal-wlr/issues/12 https://github.com/emersion/xdg-desktop-portal-wlr/issues/12 https://github.com/swaywm/wlr-protocols/issues/93 https://github.com/swaywm/wlr-protocols/issues/93

zamadatix 6y ago

Looking deeper into it (been meaning to anyways) it seems to be the typical Wayland compositor specific issue, and ironically I'm using ddevault's compositor sway. Pipewire doesn't seem to care what you send it but your second window looks to be part of xdg-desktop-portal-gtk if I'm not mistaken. Since I'm using sway/wlroots I need to use xdg-desktop-portal-wlr instead. In the FAQ for this package: "Will this let me share individual windows? No, only entire outputs. It would take significant work in wlroots, and likely a new protocol, to make this possible. A second rendering pass would be required, which would significantly reduce wlroots performance, so this may not be implemented any time soon (or ever). Will this let me share all of my outputs/displays at once? Not yet, no. It will likely never create a single stream that combines all of your outputs, but once we implement better output selection, there is no reason xdpw cannot create multiple simultaneous streams of different outputs." So it looks like I'm shit out of luck for quite a while on sway/wlroots. Looks like Gnome figured it out. Not sure about KDE.

vetinari 6y ago
Ah, that explains it. Yes, I'm running Gnome and xdg-desktop-portal-gtk. Thanks for the constructive and informative discussion.
majewsky 6y ago
For your reference, these are the issues to subscribe to if you're interested in following the discussion as it's taking place: https://github.com/emersion/xdg-desktop-portal-wlr/issues/12 https://github.com/emersion/xdg-desktop-portal-wlr/issues/12 https://github.com/swaywm/wlr-protocols/issues/93 https://github.com/swaywm/wlr-protocols/issues/93