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 ....

This would be similar to using ffmpeg to generate PNG snapshots from M4V.

Thanks, Adrian

From: Adrian Owen
Sent: 15 March 2020 22:38
To: user@guacamole.apache.org
Subject: Re: guacenc new parameters

Hi Sean,

Yes this is something I'd be very interested on working on.

My requirements are simple. Start at point x and run to the end.

The stream will be active (locked), and each time I visit it and will have 
moved on.

Or supply the 2 parameters, either way make it a contribution to guacamole 

I had as look at video.c and see I have a really steep learning curve ahead to 
code it.

Thanks Adrian
From: Sean Reid <sean.re...@gmail.com<mailto:sean.re...@gmail.com>>
Sent: 15 March 2020 22:15
To: user@guacamole.apache.org<mailto:user@guacamole.apache.org>
Subject: Re: guacenc new parameters

Hi Adrian,

Is this something you'd be interested in working on? I've worked a bit on 
guacenc myself, so I can give you some information that I've found from working 
on it.

I'm not confident that you need to think about keyframes much at all from the 
perspective of guacenc. From my understanding (and I welcome anyone who might 
differ from my understanding or explanation here to jump in), since the 
Guacamole Protocol attempts to only send changes, guacenc renders a new image 
in memory for each new instruction in the recording file, based on the 
previously rendered image. Each new image is just a mutation of the previous, 
but itself is a full image. These images are sent to libavcodec on a periodic 
that matches the target framerate. This is done because the guacamole protocol 
doesn't have a framerate, so to square the circle of converting to a video with 
a time base, guacenc holds the image in memory so that it can repeat sending 
unchanged frames to libavcodec if no guacamole protocol instructions mutated 
the in-memory image. This implicitly means that each image guacenc sends can be 
a keyframe, so you could potentially start the encoding at any frame you'd like.

I'd recommend you look at the logic of 
 in the guacenc source to get a better idea about how this process works.


On Sun, Mar 15, 2020 at 5:17 PM Adrian Owen 
<adrian.o...@eesm.com<mailto:adrian.o...@eesm.com>> wrote:

Hi Sean,


I believe that Keyframes are written to video stream, done as work for the 

So I guess it would be StartKeyFrame    EndKeyFrame.

It would have to start at StartKeyFrame and run 'n' keyframes and stop.

So its a matter of scanning the video stream file for keyframes.

That is challenging. I am a C programmer, but know not how to identify a 
keyframe while reading the stream.


From: Sean Reid <sean.re...@gmail.com<mailto:sean.re...@gmail.com>>
Sent: 15 March 2020 20:02
To: user@guacamole.apache.org<mailto:user@guacamole.apache.org>
Subject: Re: guacenc new parameters

Hi Adrian,

I don't see a reason that this wouldn't be possible. I think it would be done 
by guacenc, though, not by ffmpeg. I'd think that guacenc just wouldn't start 
sending the frames to be encoded until, while reading the input file, guacenc 
has reached the start time and stop sending frames to be encoded at end time.


On Sun, Mar 15, 2020 at 1:55 PM Adrian Owen 
<adrian.o...@eesm.com<mailto:adrian.o...@eesm.com>> wrote:

ffmpeg allows getting a section of a video file by specifying start seconds and 
end seconds,

Now the Guacamole video steam may not know seconds but:

Could Guacenc support  extra parameters: StartPoint Endpoint?

And then only generate MV4 between those points.

This is a theoretical question,

Many thanks, Adrian

Reply via email to