@ebassi @elad I can actually see the use for this in another context (and have considered designing something like it): a timelapse app for artists.
In this context, their โworkโ is their art, not something imposed by an employer.
It should probably be built into the drawing app or whatever, but I could see the niftiness of a workflow timelapse that captures the various apps you use and whatnot over a long period of time, without having to sit and record an actual video of the entire process.
@ebassi @elad yeah, makes sense. So perhaps they're using some old tool for artists that uses screenshots when it really should use the screen share portal. It sounds terrifying at first but I sometimes watch those kinds of timelapses and feel like it would be a neat tool. ๐
But uh, yeah, hacking the Shell or whatever to just *not* give any feedback of a screenshot is the wrong way for them to go about it. ๐
@ebassi @cassidy @elad Screen and window capture is useful if you want the entire app view, however some apps provide native canvas or viewport capture for timelapse purposes. For example:
* #Krita: https://docs.krita.org/en/reference_manual/dockers/recorder_docker.html
There are also a handful of related add-ons for #Blender that can assist since the native screencast feature was removed in 2.8.
@cassidy
@ebassi @elad
If you only need one frame a minute, I think with screencast you'd still have a pipewire stream producing frames at a normal framerate, and just be ignoring most of them? So not a very resource efficient solution, if that matters
(I think you may be able to negotiate a framerate of 1/60 fps over pipewire if both ends support it, but I don't think implementations typically would.)
@YaLTeR @cassidy @ebassi @elad
It looks like framerate in Pipewire is indeed an `spa_fraction`, so I think it is possible to negotiate a framerate of 1/60 fps or whatever. And then have the client fallback to a higher rate if the desktop environment doesn't support that.
So yeah, seems like a viable solution. Probably not hard to add support for in gnome-shell if it already can negotiate fps with a minimum of 1.
