Emmanuele BassiThis is utterly horrific holy fuck
elad@ebassi this basically reads "hello I'm writing malware plz help"
@elad either that, or it’s a case of somebody working in a terrible environment
Cassidy James 
@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.
Ian Douglas Scott@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.)
@cassidy
@ebassi @elad
Yeah. And video encoding overhead, which is probably the largest overhead for actual screencasting and is avoided here. Still non trivial overhead here though if it means copying 60 frames per second from a discrete GPU to main memory for each of 3 4k monitors only to ignore most frames (for the worst case scenario here).
@ebassi @elad
Yeah. And video encoding overhead, which is probably the largest overhead for actual screencasting and is avoided here. Still non trivial overhead here though if it means copying 60 frames per second from a discrete GPU to main memory for each of 3 4k monitors only to ignore most frames (for the worst case scenario here).