Does that mean you use the JS Screen capture api to capture each and every window separately?
I would’ve thought that’s too much for typical (laptop) cpus but have to admit I never tried this
I would’ve thought that’s too much for typical (laptop) cpus but have to admit I never tried this
The way I understand you, coscreen captures each window shown individually.
Doesn’t that also mean that overlapping windows are captured in full? I can’t try it out atm so perhaps if you could leave a comment on cpu usage for encoding as well as bandwidth (upload) compared to a typical Screen Sharing solution with a single screen that would be great.
I’ve been toying with the idea of getting a MacBook with cores > 4 for precisely that idea: capturing every single window, streaming them out to a separate machine for analysis of what’s happening in them and possibly making them accessible for collaboration as well, all without losing too much performance
I believe somewhere in this area is a lot of productivity waiting to be unlocked with better tools, not just for typical remote use cases but for any kind of office work