From: Tom P. <lu...@gm...> - 2007-05-09 15:05:01
|
On 3/30/07, Yusuke Shinyama <yu...@cs...> wrote: > > Hi Luis, > > On Thu, 29 Mar 2007 06:44:55 -0700 (PDT), lfk...@ya... wrote: > > In my opinion the correct timestamp should be the moment the > > client starts receiving the framebuffer update because that's > > the closest to the moment that the server actually checked the > > screen. The problem is most noticeable when there are none or > > just a few interactions (keyboard and mouse movements). When the > > mouse moves alot the server is constantly sending an update so > > the difference in timestamp is not noticeable. Another problem > > lies in function update_screen of RFBMovieConverter class > > (rfb.py). Given a timestamp, it should first create empty > > frames to catchup the elapsed time and only after that it should > > insert a frame with the framebuffer update. Currently it's in > > the other way around. This is used in vnclog playback. SWF > > recordings use a different class which is currently working > > correctly. > > Hmm... you seem to be right. I haven't thought much about > this timing issue, but experienced weird phenomena > (screen updates are sometime too off timing) a couple of times. > I'll take a look into this. Yusuke, Have you had a chance to look at this problem? Is there anything that I can do to help? Thanks, Tom |