Hi Sean, It’s 2 problems in 1.
Snapshots are needed for input for OCR and I also need make guacenc run a lots faster on High res data rich RDP sessions. I hoped if I could solve the snapshots only option, then it would also complete sooner. The overall Issue is how many concurrent users can it support with data gathered in a timely manner. From: Sean Reid [mailto:[email protected]] Sent: 26 March 2020 00:18 To: [email protected] Subject: Re: guacenc new parameters I don't think we can provide a definitive answer as to whether mpeg4 (which is the codec guacenc uses for m4v), jpeg, png, or any other codec will be faster always. Often, the ability for a codec to encode quickly relative to another depends on the content of the frames it is encoding. In addition, individual snapshots add a different type of concern that a video doesn't have: extra IO operations. A video is one big binary file, tons of images is tons of small binary files. Each image file creation is an extra create, write, flush, and close IO operation that video won't have. Whether these extra operations add up to a meaningful amount of overhead is another question entirely. To answer both your questions: 1. Guacenc could write snapshots every second of a recording instead of encoding video, but it doesn't right now and I don't know that anyone has talked about providing code to do that. 2. It's not possible to know if encoding individual images every second would be faster than encoding mpeg4 for the reasons I outlined above. This conversation brings up some other questions for me though. What problem are you trying to solve? Is it the speed of video encoding? Is it that you need screenshots rather than a video for OCR? Maybe understanding the whole problem will help us help you. On Wed, Mar 25, 2020 at 7:29 PM Adrian Owen <[email protected]<mailto:[email protected]>> wrote: Thanks, It’s what I suspected. And I use the typescript, for SSH/TELNET already. So going back to my question. Would guacaenc support writing snapshots every second? And moreover, if it did that instead of writing M4V would be a lot faster? An intense high res 1 Hour RDP, can take guacenc 15-30 minutes to complete? From: Mike Jumper [mailto:[email protected]<mailto:[email protected]>] Sent: 25 March 2020 22:26 To: [email protected]<mailto:[email protected]> Subject: Re: guacenc new parameters For purely-graphical connections like VNC and RDP, no, OCR would really be the only option. Once the data leaves the VNC/RDP server, it's just a fragment of an image and has lost all text meaning. If you enable recording of keyboard events, you would be able to infer what is being typed, but the only way to read the graphical content of the screen would be OCR. For connections driven by text like SSH, telnet, and Kubernetes, you can leverage Guacamole's support for typescripts. Each typescript is the raw text data received from the server prior to being rendered, including console codes, coupled with a separate file containing timing information. - Mike On Wed, Mar 25, 2020 at 1:52 PM Adrian Owen <[email protected]<mailto:[email protected]>> wrote: Mike, Is there a less convoluted way to grab the text displayed? From: Mike Jumper [mailto:[email protected]<mailto:[email protected]>] Sent: 25 March 2020 20:42 To: [email protected]<mailto:[email protected]> Subject: Re: guacenc new parameters On Wed, Mar 25, 2020 at 8:58 AM Adrian Owen <[email protected]<mailto:[email protected]>> wrote: I had an idea for another parameter to guacenc. gaucenc generates an M4V file. Could it optionally, generate PNG Snapshot images instead. Every second. 1.file.png, 2.file.png …. Why? - Mike
