[Vnc2swf-users] memory error using localhost
Status: Alpha
Brought to you by:
euske
From: Bill S. <bil...@ly...> - 2005-10-11 13:06:43
|
I've been able to record a VNC session from remote servers running on both Windows 2000 and Windows 2003. As a result, I have three questions I'd welcome your comments on: 1) Memory error When I try to use vnc2swf on my machine I get the "memory error" message that has been reported in this list before. My machine is setup using the same version of VNC (4.1.1) as I've used on the remote servers and, apart from the host name, uses the same command. The only difference is that on my machine I've set the VNC server to accept local connections. My machine is a laptop with a 1900x1600 screen so I'm wondering if this is a possible cause of the problem? I've tried to use the "clipping" option to limit the scope of the recording of the local session but it doesn't help. The laptop has 1GB RAM so I don't think memory itself is going to be the problem. 2) Record clipping not yet supported? I've tried using the clipping region option on the stream from one of the remote servers and it appears to be ignored when recording using the VNC recording mode. Is that right? 3) Edit clipping supported? Clipping seems to work in edit.py when converting a .vnc file to a .swf. However the recorded size of the swf retains the size of the original recording and only the clipped region is displayed. The rest of the swf display is black. For example, suppose you record from a VNC session with a geometry of 1024x768. You then convert the .vnc to a .swf using a clipping region of, say, 640x480+0+0. When the resulting swf is played, the swf window is still 1024x768 though the only area used to display the movie is the specified clipping region. The area to the right and bottom - outside the clipping area - is black. What should I be doing to have the final swf have a window size that is the same as the clipping area? Or it is even possible? Regards Bill Seddon |