Originally posted by Aryma
View Post
Announcement
Collapse
No announcement yet.
KDE Plasma 5.20 To Bring Working Screen Recording / Screencasting On Wayland
Collapse
X
-
Originally posted by elatllat View PostScreen sharing via WebRTC might keep me on X11 :/
Chrome is having some issues with distributions using newer versions of Pipewire. WebRTC screen sharing can be done by pipewire its once all the finer details have settled in WebRTC will not be a reason to remain on X11 at all.
Originally posted by V1tol View PostSame. I need app screen sharing working in Google Chrome for work and that's why I am tied to X11 like forever. AFAIK only full screen sharing works now through PipeWire and I don't know if that works on KDE at all.
KDE Plasma now has the protocol coverage in place that is based on Pipewire for allowing the management of video feeds and requesting output / window streams.
That bit OBS Studio with KDE 5.2.0 is using pipewire for screen sharing and its full screen and window base sharing in wayland mode.
V1tol is now to the point is more a matter of time until the finer details of the version of pipewire chrome is built against and the version of pipewire KDE Plasma needs to do screen sharing in fact align.
Interesting point is the pipewire method is better for those with multi screen setups than the X11 screen capture method.
- Likes 1
Comment
-
Originally posted by tildearrow View PostLet's do something.
They don't invade our territory, and we don't invade theirs.
Really looking forward to Wayland replacing x11 on all desktops. Pity nvidia has been too arrogant to get their crap together
- Likes 3
Comment
-
Originally posted by ngraham View Post
For Plasma, here's the list: https://community.kde.org/Plasma/Wayland_Showstoppers
Comment
-
Originally posted by Auzy View Post
That totally doesn't sound immature...
Really looking forward to Wayland replacing x11 on all desktops. Pity nvidia has been too arrogant to get their crap together
And I think you can see why Nvidia isn't jumping on the opportunity to implement something that's only usable by less than 3% of their installed base.
For bonus points, when discussing how to move this forward, it was made clear that neither GBM nor EGLStreams are without fault wrt to what they're supposed to do in Wayland, so technically, neither can be declared the better (or worse) solution.
Having just got my 4k monitor, I would love to be able to use separate display scaling at least, so yeah, I'm rooting for Wayland. But the list of known issues is just too long still. I'm sure I'll jump ship at some point, but I've given up on trying to guess which is "the year of Wayland".Last edited by bug77; 26 July 2020, 07:29 AM.
- Likes 2
Comment
-
Originally posted by bug77 View Post
Oaaa. how long has this been sitting there? I've been looking for this since forever. (I'm actually looking for this page to say "all done", but one step at a time.)
It used to be much larger! The "All done" stage is probably not that far off...
- Likes 4
Comment
-
Originally posted by bug77 View Post
I don't think they're being arrogant, if you get the whole picture. Nvidia has a unified drivers (with thin wrappers) that works for all operating systems they support. EGLStreams is an extension to EGL which also works on all operating systems they support. GBM is something that is actually not required by Wayland (Wayland is a specification, it doesn't care much how it's implemented). GBM is also Linux specific and happened to be what the reference Wayland implementation used. For some reason, compositors also used GBM at first. gdm has also implemented EGLStreams support in the meantime, kwin is still playing the "understaffed" card.
- Likes 3
Comment
Comment