vnc2swf-users — General discussion about the use of vnc2swf.

Re: [Vnc2swf-users] error: unpack str size does not match format

[<lfk...@ya...>]

Well,

I guess I found the bug. I'll let Yusuke fix it! :)
The RFB protocol (http://www.realvnc.com/docs/rfbproto.pdf) states that
first the server sends the maximum protocol version it understands and 
then the client sends the version it wants to use.
Check function "init" in class RFBProxy. It's inverted!  And it assumes that
the handshaked version is the one returned from the server.  It's not. It's the
one sent by the client.
The RealVnc sends version 3.6. So the client must send a 3.3.
The problem is that the client is trying to decode the messages as 3.6, which
is not 3.3 so it ends up in the else clause along with the 3.7 and 3.8.
Just to make it work without much thought:
  def init(self):
    # recv: server protocol version
    self.server_version = self.recv(12)
    # send: client protocol version
    # just force version 3.3 for now
    # but should try the highest between 3.3, 3.7 and 3.8
    self.send('RFB 003.003\x0a')
    self.server_version = 'RFB 003.003\x0a'
    if self.debug:
      print >>stderr, 'server_version: %r' % self.server_version
    return self

That's it!

Luis Fernando

--- "Karnowski, David" <dka...@et...> escreveu:

> As a work-around the free edition of RealVNC works for me on Windows,
> including the authentication: http://www.realvnc.com/download.html 
> 
> -----Original Message-----
> From: vnc...@li...
> [mailto:vnc...@li...]On Behalf Of Fabiano
> Caixeta Duarte
> Sent: Friday, November 11, 2005 8:04 AM
> To: vnc...@li...
> Subject: [Vnc2swf-users] error: unpack str size does not match format
> 
> 
> Hi there!
> 
> I just installed pyvnc2swf 0.7.1 and pygame 1.7.1. I had already installed 
> tightVNC 1.2.9.
> 
> When I try to conect to a UltraVNC 1.0 (Windows), vnc2swf.py never prompts 
> for password and after a while, shows me
> "error: unpack str size does not match format"
> 
> The command line I'm using is:
> 
> $ ./vnc2swf.py -o /tmp/test.swf 192.168.0.5
> 
> I hope you have a solution for this :)
> 
> Thanks in advance!
> 
> --
> Fabiano Caixeta Duarte
> Seção Técnica de Informática
> FEA-RP/USP
> 
> ************************************
> " DESISTIR é uma solução permanente
>    para um problema temporário. "
>                       James MacArthur
> ************************************
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by:
> Tame your development challenges with Apache's Geronimo App Server. Download
> it for free - -and be entered to win a 42" plasma tv or your very own
> Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
> _______________________________________________
> Vnc2swf-users mailing list
> Vnc...@li...
> https://lists.sourceforge.net/lists/listinfo/vnc2swf-users
> 



	



	
		
_______________________________________________________ 
Yahoo! Acesso Grátis: Internet rápida e grátis. 
Instale o discador agora!
http://br.acesso.yahoo.com/

[Vnc2swf-users] error: unpack str size does not match format

[Karnowski, D. <dka...@et...>]

As a work-around the free edition of RealVNC works for me on Windows,
including the authentication: http://www.realvnc.com/download.html=20

-----Original Message-----
From: vnc...@li...
[mailto:vnc...@li...]On Behalf Of Fabiano
Caixeta Duarte
Sent: Friday, November 11, 2005 8:04 AM
To: vnc...@li...
Subject: [Vnc2swf-users] error: unpack str size does not match format


Hi there!

I just installed pyvnc2swf 0.7.1 and pygame 1.7.1. I had already =
installed=20
tightVNC 1.2.9.

When I try to conect to a UltraVNC 1.0 (Windows), vnc2swf.py never =
prompts=20
for password and after a while, shows me
"error: unpack str size does not match format"

The command line I'm using is:

$ ./vnc2swf.py -o /tmp/test.swf 192.168.0.5

I hope you have a solution for this :)

Thanks in advance!

--
Fabiano Caixeta Duarte
Se=E7=E3o T=E9cnica de Inform=E1tica
FEA-RP/USP

************************************
" DESISTIR =E9 uma solu=E7=E3o permanente
   para um problema tempor=E1rio. "
                      James MacArthur
************************************

[Vnc2swf-users] error: unpack str size does not match format

[Fabiano C. D. <fa...@fe...>]

Hi there!

I just installed pyvnc2swf 0.7.1 and pygame 1.7.1. I had already installed=
=20
tightVNC 1.2.9.

When I try to conect to a UltraVNC 1.0 (Windows), vnc2swf.py never prompts=
=20
for password and after a while, shows me
"error: unpack str size does not match format"

The command line I'm using is:

$ ./vnc2swf.py -o /tmp/test.swf 192.168.0.5

I hope you have a solution for this :)

Thanks in advance!

--
Fabiano Caixeta Duarte
Se=E7=E3o T=E9cnica de Inform=E1tica
FEA-RP/USP

************************************
" DESISTIR =E9 uma solu=E7=E3o permanente
   para um problema tempor=E1rio. "
                      James MacArthur
************************************

[Vnc2swf-users] pyvnc2swf-0.7.2 released!

[Yusuke S. <yu...@cs...>]

Folks,

I released pyvnc2swf-0.7.2.
http://www.unixuser.org/~euske/vnc2swf/pyvnc2swf-0.7.2.tar.gz

This version has a fix for the "illegal encoding" error (hopefully!),
and a couple of other features. Thanks for those who made suggestions.

New features include:
 * More efficient recording when a "clipping" option is used.
 * "recordwin.sh" script is brought from the original (C version) vnc2swf.

The cursor feature that Luis has pointed out will be put in the
next (major?) version, probably 0.8.0.

Thanks,
Yusuke

RE: [Vnc2swf-users] RFB protocol error: Illegal encoding

[Karnowski, D. <dka...@et...>]

Yes, running in "CUI" mode seems to have worked around it. I'm yet to =
experience a similar failure since running in CUI mode.

How do I end the CUI recording? I've been using <Ctrl>C which seems to =
work OK, but I'm guessing there maybe less brutal method?

Luis mentioned a couple of other things to try:
1) Running the "vnc" method. I'm yet to try this and won't since I have =
a workaround now unless you think it will be beneficial in resolving the =
original problem. But from Yusuke's email below I assume you're already =
on top of it.
2) Run (the GUI) in debug mode. Does this print the debug info to =
stdout/stderr? I ask because it didn't seem to display much more info =
than not running in debug mode. Anyway, here's the output in a GUI run =
that produced the error:
C:\Program Files\DesktopRecorder>python.exe =
C:\Progra~1\pyvnc2swf-0.7.1\vnc2swf.py -d -d -d -d -d -d -d -d -d -d
 Using pygame 1.7.0
 Connected: 127.0.0.1:5900, preferred_encoding=3D(0,)
 VNC Screen: size=3D800x600, name=3D'JFK1-35XMN0VDJV'
 Output movie size: 800x600
 Creating movie: 'C:/David/work/ireport_variables.swf': version=3D5, =
size=3D800x600, framerate=3D12.0, compression=3DNone
 start recording
 Ignored msg=3D'\xff'
 Ignored msg=3D'\xff'
 Ignored msg=3D'\xff'
 Illegal encoding: 0xffffff


Many thanks to Yusuke & Luis for your responses. I don't personally need =
any further responses as the workaround is sufficient for now.

regards,
David

-----Original Message-----
From: Yusuke Shinyama [mailto:yu...@cs...]
Sent: Thursday, November 10, 2005 11:46 AM
To: Karnowski, David; lfk...@ya...
Cc: Vnc...@li...
Subject: Re: [Vnc2swf-users] RFB protocol error: Illegal encoding


I noticed this happens only if you use GUI mode.  I set the socket
timeout in RFBNetworkClientWithTkMixin, and this is probably the
cause of the bug, as it might abort data transfer in the middle.
So the current workaround would be using command line mode for a while.
I think I can fix this before long.

Thanks
Yusuke

lfk...@ya... wrote:
>=20
> Hi,
>=20
> The recorder could be parsing the wrong number of bytes for some king =
of
> message that rarely happens. When it happens the recorder may not get =
the
> number of bytes as expected and then when it tries to decode the next =
message,
> the stream pointer is not at the expected position.  I'm just trying =
to guess
> it, of course.
> Maybe David could try to record it using the "vnc" method and then try =
to
> convert it later. If the problem occurs then we can use that file to =
check
> what's going wrong.  Just a suggestion!
>=20
> Luis Fernando
>=20
> --- Yusuke Shinyama <yu...@cs...> escreveu:
>=20
> > Yes, I've experienced this problem a couple of times, but didn't
> > know the exact condition when it happens. There's no solution
> > right now, but I hope I can investigate this problem.
> >=20
> > Yusuke
> >=20
> > "Karnowski, David" <dka...@et...> wrote:
> > > Hello,
> > >=20
> > > While recording I fairly consistently get an "RFB protocol error" =
window
> > pop up with the message "Illegal encoding: 0x6699cc" (sometimes the =
hex
> > number is different I think, but can't be sure). At that point my =
recording
> > stops and I have to start over. It doesn't always happen, but =
normally does
> > at some point. The longer I record the more likely it is that I'll =
experience
> > it. The error normally occurs after something fairly dynamic occurs =
on the
> > screen (opening a new window say).
> > >=20
> > > I'm running the 0.7.1 Python version of vnc2swf, but it also used =
to happen
> > with version 0.6.3 which I just upgraded from. My Python version is =
2.4, I'm
> > running RealVNC v4, and I'm on Windows 2000 Service Pack 4.
> > >=20
> > > Any help appreciated.
> > >=20
> > > thanks,
> > > David
> >=20

Re: [Vnc2swf-users] RFB protocol error: Illegal encoding

[Yusuke S. <yu...@cs...>]

I noticed this happens only if you use GUI mode.  I set the socket
timeout in RFBNetworkClientWithTkMixin, and this is probably the
cause of the bug, as it might abort data transfer in the middle.
So the current workaround would be using command line mode for a while.
I think I can fix this before long.

Thanks
Yusuke

lfk...@ya... wrote:
> 
> Hi,
> 
> The recorder could be parsing the wrong number of bytes for some king of
> message that rarely happens. When it happens the recorder may not get the
> number of bytes as expected and then when it tries to decode the next message,
> the stream pointer is not at the expected position.  I'm just trying to guess
> it, of course.
> Maybe David could try to record it using the "vnc" method and then try to
> convert it later. If the problem occurs then we can use that file to check
> what's going wrong.  Just a suggestion!
> 
> Luis Fernando
> 
> --- Yusuke Shinyama <yu...@cs...> escreveu:
> 
> > Yes, I've experienced this problem a couple of times, but didn't
> > know the exact condition when it happens. There's no solution
> > right now, but I hope I can investigate this problem.
> > 
> > Yusuke
> > 
> > "Karnowski, David" <dka...@et...> wrote:
> > > Hello,
> > > 
> > > While recording I fairly consistently get an "RFB protocol error" window
> > pop up with the message "Illegal encoding: 0x6699cc" (sometimes the hex
> > number is different I think, but can't be sure). At that point my recording
> > stops and I have to start over. It doesn't always happen, but normally does
> > at some point. The longer I record the more likely it is that I'll experience
> > it. The error normally occurs after something fairly dynamic occurs on the
> > screen (opening a new window say).
> > > 
> > > I'm running the 0.7.1 Python version of vnc2swf, but it also used to happen
> > with version 0.6.3 which I just upgraded from. My Python version is 2.4, I'm
> > running RealVNC v4, and I'm on Windows 2000 Service Pack 4.
> > > 
> > > Any help appreciated.
> > > 
> > > thanks,
> > > David
> > 

Re: [Vnc2swf-users] Cursor pseudo-encoding

[Yusuke S. <yu...@cs...>]

Thank you, Luis!  I've received your files. It seems working
pretty good, and I will try to add alpha channel things, and
incorporate your changes into the next version.

Yusuke

lfk...@ya... wrote:
>  Hi,
>  
>  I managed to make the cursor pseudo-encodings to work.
>  It understands the messages and draws the cursor image at the right place.
>  But it still needs to use the cursor mask to change the alpha channel to make
>  the background transparent.  Unfortunetly I don't know Python very much.
>  Maybe someone with Python knowlegde could make this part to work properly in
> an
>  easily manner.
>  How can I send the files? I've been trying to send it but my message gets 
>  blocked everytime.
>  Here's the problem I need to solve:  I have one variable with the maskData
> (one  
>  bit for each pixel) and I have another variable with the image (4 bytes per
>  pixel - RGBA).  How can I change the alpha channel?  I really couldn't 
>  understand the types used and how to access each element.
> 
>  Luis Fernando
> 

Re: [Vnc2swf-users] RFB protocol error: Illegal encoding

[<lfk...@ya...>]

Also try using debug to check the last messages before the error.  
They can give you a great hint on which message is causing the problem.


--- lfk...@ya... escreveu:

> 
> Hi,
> 
> The recorder could be parsing the wrong number of bytes for some king of
> message that rarely happens. When it happens the recorder may not get the
> number of bytes as expected and then when it tries to decode the next
> message,
> the stream pointer is not at the expected position.  I'm just trying to guess
> it, of course.
> Maybe David could try to record it using the "vnc" method and then try to
> convert it later. If the problem occurs then we can use that file to check
> what's going wrong.  Just a suggestion!
> 
> Luis Fernando
> 
> --- Yusuke Shinyama <yu...@cs...> escreveu:
> 
> > Yes, I've experienced this problem a couple of times, but didn't
> > know the exact condition when it happens. There's no solution
> > right now, but I hope I can investigate this problem.
> > 
> > Yusuke
> > 
> > "Karnowski, David" <dka...@et...> wrote:
> > > Hello,
> > > 
> > > While recording I fairly consistently get an "RFB protocol error" window
> > pop up with the message "Illegal encoding: 0x6699cc" (sometimes the hex
> > number is different I think, but can't be sure). At that point my recording
> > stops and I have to start over. It doesn't always happen, but normally does
> > at some point. The longer I record the more likely it is that I'll
> experience
> > it. The error normally occurs after something fairly dynamic occurs on the
> > screen (opening a new window say).
> > > 
> > > I'm running the 0.7.1 Python version of vnc2swf, but it also used to
> happen
> > with version 0.6.3 which I just upgraded from. My Python version is 2.4,
> I'm
> > running RealVNC v4, and I'm on Windows 2000 Service Pack 4.
> > > 
> > > Any help appreciated.
> > > 
> > > thanks,
> > > David
> > 
> > 
> > -------------------------------------------------------
> > SF.Net email is sponsored by:
> > Tame your development challenges with Apache's Geronimo App Server.
> Download
> > it for free - -and be entered to win a 42" plasma tv or your very own
> > Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
> > _______________________________________________
> > Vnc2swf-users mailing list
> > Vnc...@li...
> > https://lists.sourceforge.net/lists/listinfo/vnc2swf-users
> > 
> 
> 
> 
> 	
> 
> 
> 
> 	
> 		
> _______________________________________________________ 
> Yahoo! Acesso Grátis: Internet rápida e grátis. 
> Instale o discador agora!
> http://br.acesso.yahoo.com/
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by:
> Tame your development challenges with Apache's Geronimo App Server. Download
> it for free - -and be entered to win a 42" plasma tv or your very own
> Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
> _______________________________________________
> Vnc2swf-users mailing list
> Vnc...@li...
> https://lists.sourceforge.net/lists/listinfo/vnc2swf-users
> 



	



	
		
_______________________________________________________ 
Yahoo! Acesso Grátis: Internet rápida e grátis. 
Instale o discador agora!
http://br.acesso.yahoo.com/

Re: [Vnc2swf-users] RFB protocol error: Illegal encoding

[<lfk...@ya...>]

Hi,

The recorder could be parsing the wrong number of bytes for some king of
message that rarely happens. When it happens the recorder may not get the
number of bytes as expected and then when it tries to decode the next message,
the stream pointer is not at the expected position.  I'm just trying to guess
it, of course.
Maybe David could try to record it using the "vnc" method and then try to
convert it later. If the problem occurs then we can use that file to check
what's going wrong.  Just a suggestion!

Luis Fernando

--- Yusuke Shinyama <yu...@cs...> escreveu:

> Yes, I've experienced this problem a couple of times, but didn't
> know the exact condition when it happens. There's no solution
> right now, but I hope I can investigate this problem.
> 
> Yusuke
> 
> "Karnowski, David" <dka...@et...> wrote:
> > Hello,
> > 
> > While recording I fairly consistently get an "RFB protocol error" window
> pop up with the message "Illegal encoding: 0x6699cc" (sometimes the hex
> number is different I think, but can't be sure). At that point my recording
> stops and I have to start over. It doesn't always happen, but normally does
> at some point. The longer I record the more likely it is that I'll experience
> it. The error normally occurs after something fairly dynamic occurs on the
> screen (opening a new window say).
> > 
> > I'm running the 0.7.1 Python version of vnc2swf, but it also used to happen
> with version 0.6.3 which I just upgraded from. My Python version is 2.4, I'm
> running RealVNC v4, and I'm on Windows 2000 Service Pack 4.
> > 
> > Any help appreciated.
> > 
> > thanks,
> > David
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by:
> Tame your development challenges with Apache's Geronimo App Server. Download
> it for free - -and be entered to win a 42" plasma tv or your very own
> Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
> _______________________________________________
> Vnc2swf-users mailing list
> Vnc...@li...
> https://lists.sourceforge.net/lists/listinfo/vnc2swf-users
> 



	



	
		
_______________________________________________________ 
Yahoo! Acesso Grátis: Internet rápida e grátis. 
Instale o discador agora!
http://br.acesso.yahoo.com/

Re: [Vnc2swf-users] Cursor pseudo-encoding

[<lfk...@ya...>]

 Hi,
 
 I managed to make the cursor pseudo-encodings to work.
 It understands the messages and draws the cursor image at the right place.
 But it still needs to use the cursor mask to change the alpha channel to make
 the background transparent.  Unfortunetly I don't know Python very much.
 Maybe someone with Python knowlegde could make this part to work properly in
an
 easily manner.
 How can I send the files? I've been trying to send it but my message gets 
 blocked everytime.
 Here's the problem I need to solve:  I have one variable with the maskData
(one  
 bit for each pixel) and I have another variable with the image (4 bytes per
 pixel - RGBA).  How can I change the alpha channel?  I really couldn't 
 understand the types used and how to access each element.

 Luis Fernando



	



	
		
_______________________________________________________ 
Yahoo! Acesso Grátis: Internet rápida e grátis. 
Instale o discador agora!
http://br.acesso.yahoo.com/

Re: [Vnc2swf-users] RFB protocol error: Illegal encoding

[Yusuke S. <yu...@cs...>]

Yes, I've experienced this problem a couple of times, but didn't
know the exact condition when it happens. There's no solution
right now, but I hope I can investigate this problem.

Yusuke

"Karnowski, David" <dka...@et...> wrote:
> Hello,
> 
> While recording I fairly consistently get an "RFB protocol error" window pop up with the message "Illegal encoding: 0x6699cc" (sometimes the hex number is different I think, but can't be sure). At that point my recording stops and I have to start over. It doesn't always happen, but normally does at some point. The longer I record the more likely it is that I'll experience it. The error normally occurs after something fairly dynamic occurs on the screen (opening a new window say).
> 
> I'm running the 0.7.1 Python version of vnc2swf, but it also used to happen with version 0.6.3 which I just upgraded from. My Python version is 2.4, I'm running RealVNC v4, and I'm on Windows 2000 Service Pack 4.
> 
> Any help appreciated.
> 
> thanks,
> David

Re: [Vnc2swf-users] shockwave files generated fron vnc2swf.py seem to crash shock wave players e.g. macromedia plugin and realplayer

[Yusuke S. <yu...@cs...>]

Do you mean a garbled movie by "fall over"?
If so, it seems like you hit the limitation of
the maximum number of sprites in SWF movie. This can be solved by
converting the movie into "video" encoding. Try -V option
in edit.py. 

Thanks,
Yusuke

richard zatorski <ric...@gm...> wrote:
> I was having fits with my recorded files when it dawned on me that maybe the
> vnc2swf recorder might be generating weird .swf data. It turns out that when
> I'm recording a 30min+ session, the generic players fall over. However, when
> I tried to play these same files through play.py, it completed without
> error. Has anyone seen issues playing large files on the Macromedia plugin
> or in the realpayer? My file is 84M in size.
> 
> Thanks,
> (RAZ)
> 

Re: [Vnc2swf-users] Re: assertion error problem

[Yusuke S. <yu...@cs...>]

Doug, 
I'll put this in the next release. Thanks.

Yusuke

db...@br... wrote:
> vnc2swf can handle the control-c manually. In python it would look like:
> 
> import signal
> stop = 0
> def INThandler(signum, frame):
>       stop = 1
> prevsighandler = signal.signal(signal.SIGINT, INThandler)
> 
> In this manner you can control when the program stops when a control-c is
> encountered (or prevent it from stopping at all).
> 
> -Doug
> 
> > Bill,
> >
> > This assertion error occurs when the flash file is not finished
> > properly. Usually this should never happen, because when you hit
> > Ctrl-C vnc2swf.py captures the signal and take a proper action to
> > close the movie. But when you hit a bad timing, it might end up in
> > the middle of something (probably image transfer/conversion
> > routine) and just jumps out from it without doing the job. I
> > experienced this a couple of times, and I think the probability
> > gets higher when you have a larger screen, because the duration of
> > this "critical section" gets longer.  And it is even higher when
> > you're using "Video" type encoding, because it is known to be
> > slower so you more likely will get a bad timing.
> >
> > So, the answer I can propose is to use "shape" encoding instead of
> > "video" and convert it into "video" swf after recording.
> >
> > Yusuke
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by the JBoss Inc.
> Get Certified Today * Register for a JBoss Training Course
> Free Certification Exam for All Training Attendees Through End of 2005
> Visit http://www.jboss.com/services/certification for more information
> _______________________________________________
> Vnc2swf-users mailing list
> Vnc...@li...
> https://lists.sourceforge.net/lists/listinfo/vnc2swf-users
> 

[Vnc2swf-users] RFB protocol error: Illegal encoding

[Karnowski, D. <dka...@et...>]

Hello,

While recording I fairly consistently get an "RFB protocol error" window =
pop up with the message "Illegal encoding: 0x6699cc" (sometimes the hex =
number is different I think, but can't be sure). At that point my =
recording stops and I have to start over. It doesn't always happen, but =
normally does at some point. The longer I record the more likely it is =
that I'll experience it. The error normally occurs after something =
fairly dynamic occurs on the screen (opening a new window say).

I'm running the 0.7.1 Python version of vnc2swf, but it also used to =
happen with version 0.6.3 which I just upgraded from. My Python version =
is 2.4, I'm running RealVNC v4, and I'm on Windows 2000 Service Pack 4.

Any help appreciated.

thanks,
David

Re: [Vnc2swf-users] Problem with OSX 10.4

[Carlo G. <ga...@sk...>]

I get this:

$ /Applications/pyvnc2swf-0.7.0/vnc2swf.py 
Using pygame 1.7.0
/Applications/pyvnc2swf-0.7.0/image.py:44: RuntimeWarning: tp_compare
didn't return -1 or -2 for exception
  assert (1,6) <= pygame.vernum, 'we need pygame 1.6 or newer.'
Either Pygame or Python Imaging Library is required.

I've installed from pytonmac.org:
pygame-1.7.0-py2.3-macosx10.3.zip
PIL-1.1.5-py2.3-macosx10.3.zip

although I've OSX 10.4.3.
Pytonmac lilst only pygame for OSX 10.3, not for 10.4 :(
After that I've installed packages, I symlink both from
/Library/Python/2.3/ to
/System/Library/Frameworks/Python.framework/Versions/2.3/Extras/lib/python.


Yusuke Shinyama <yu...@cs...> on Lunedì, 31 ottobre 2005 at 5:01
+0100 wrote:
>Carlo,
>
>It looks like you've installed a wrong version of Pygame, but
>not sure. Type the following and tell me what happens.
>If you get an ImportError, you probably did not install the package
>correctly.
>
>
> $ /Applications/pyvnc2swf-0.7.0/vnc2swf.py
> >>> import pygame
> >>> pygame.vernum
>
>
>Thanks
>Yusuke

[Vnc2swf-users] shockwave files generated fron vnc2swf.py seem to crash shock wave players e.g. macromedia plugin and realplayer

[richard z. <ric...@gm...>]

I was having fits with my recorded files when it dawned on me that maybe th=
e
vnc2swf recorder might be generating weird .swf data. It turns out that whe=
n
I'm recording a 30min+ session, the generic players fall over. However, whe=
n
I tried to play these same files through play.py, it completed without
error. Has anyone seen issues playing large files on the Macromedia plugin
or in the realpayer? My file is 84M in size.

Thanks,
(RAZ)

[Vnc2swf-users] vnc2swf subprocess

[Juan P. <hel...@gm...>]

Hi,

   I started to use vnc2swf today and have a question about the "S"
parameter running under Windows OS: is supported?

   I tried to execute the following and the program hangs at the
subprocess launch, this is an output from the Windows console:

>>>>>>>>>>>
C:\DOCUME~1\pablodc\ESCRIT~1\PYVNC2~1.1>vnc2swf.py -n -d -o
capacitacion.swf -S "SoundCapture.exe -vbr -sr 22050 -br 112
capacitacion.mp3" localhost:0 5900
Using pygame 1.7.1release
Connected: localhost:5900, preferred_encoding=3D(0,)
VNC Screen: size=3D1024x768, name=3D'PAR001001-703'
Output movie size: 1024x768
Creating movie: 'capacitacion.swf': version=3D5, size=3D1024x768,
framerate=3D12.0, compression=3DNone
start recording
Traceback (most recent call last):
  File "C:\DOCUME~1\pablodc\ESCRIT~1\PYVNC2~1.1\vnc2swf.py", line 363, in ?
    if __name__ =3D=3D "__main__": main(sys.argv[1:])
  File "C:\DOCUME~1\pablodc\ESCRIT~1\PYVNC2~1.1\vnc2swf.py", line 356, in m=
ain
    debug=3Ddebug)
  File "C:\DOCUME~1\pablodc\ESCRIT~1\PYVNC2~1.1\vnc2swf.py", line 256,
in vnc2swf
    subprocess.start()
  File "C:\DOCUME~1\pablodc\ESCRIT~1\PYVNC2~1.1\vnc2swf.py", line 283, in s=
tart
    self.pid =3D os.fork()
AttributeError: 'module' object has no attribute 'fork'

C:\DOCUME~1\pablodc\ESCRIT~1\PYVNC2~1.1>
>>>>>>>>>>>

SoundCapture is in the %PATH% so the problem is not with this utility...

Any sugestion?

Thanks in advance and sorry by my bad english: it's not my native language.

[Vnc2swf-users] Issue with pyvnc2swf where the recorder stops recording after about 30min

[richard z. <ric...@gm...>]

I'm trying to record a 1hour presentation. I'm recording a tight vnc sessio=
n
with a 16 plane color depth. If I try either the python recorder or the C
recorder, the video recording just stops after about 30 minutes or so. Has
anyone seen this behavior, and if so do you know how to correct it?

Thanks,
(RAZ)

Re: [Vnc2swf-users] Re: assertion error problem

[<db...@br...>]

vnc2swf can handle the control-c manually. In python it would look like:

import signal
stop =3D 0
def INThandler(signum, frame):
      stop =3D 1
prevsighandler =3D signal.signal(signal.SIGINT, INThandler)

In this manner you can control when the program stops when a control-c is
encountered (or prevent it from stopping at all).

-Doug

> Bill,
>
> This assertion error occurs when the flash file is not finished
> properly. Usually this should never happen, because when you hit
> Ctrl-C vnc2swf.py captures the signal and take a proper action to
> close the movie. But when you hit a bad timing, it might end up in
> the middle of something (probably image transfer/conversion
> routine) and just jumps out from it without doing the job. I
> experienced this a couple of times, and I think the probability
> gets higher when you have a larger screen, because the duration of
> this "critical section" gets longer.  And it is even higher when
> you're using "Video" type encoding, because it is known to be
> slower so you more likely will get a bad timing.
>
> So, the answer I can propose is to use "shape" encoding instead of
> "video" and convert it into "video" swf after recording.
>
> Yusuke

[Vnc2swf-users] Re: assertion error problem

[Yusuke S. <yu...@cs...>]

Bill,

This assertion error occurs when the flash file is not finished
properly. Usually this should never happen, because when you hit
Ctrl-C vnc2swf.py captures the signal and take a proper action to
close the movie. But when you hit a bad timing, it might end up in
the middle of something (probably image transfer/conversion
routine) and just jumps out from it without doing the job. I
experienced this a couple of times, and I think the probability
gets higher when you have a larger screen, because the duration of
this "critical section" gets longer.  And it is even higher when
you're using "Video" type encoding, because it is known to be
slower so you more likely will get a bad timing.

So, the answer I can propose is to use "shape" encoding instead of
"video" and convert it into "video" swf after recording.

Yusuke


Bill Seddon <bil...@ly...> wrote:
> With 0.71 I'm able to record on my WindowsXP laptop.  So far I've been
> using the VNC record option and then using edit.py to convert the movies
> into clipped SWFs (and this works!).  
> 
> So I thought I'd try to record direct to SWF because then I can record
> and clip the movie at the same time.  I'm using the command:
> 
> vnc2swf.py -n -o test.swf -t video -C 1024x768+0+100 -r 5 localhost 5900
> 
> The recording appears to work and I see:
> 
> Using pygame 1.7.1release
> Connected: localhost:5900, preferred_encoding=(0,)
> Password for localhost:5900:
> 
> But when I end the session, I get the message(s) below.  A .SWF file is
> created but it is not playable.  What could I be doing wrong?
> 
> VNC Screen: size=1920x1200, name='INSPIRON9300-1'
> Output movie size: 1024x768
> Creating movie: 'test.swf': version=7, size=1024x768, framerate=5,
> compression=None
> Traceback (most recent call last):
>   File "C:\Program Files\vnc2swf-0.71\vnc2swf.py", line 363, in ?
>     if __name__ == "__main__": main(sys.argv[1:])
>   File "vnc2swf-0.71\vnc2swf.py", line 356, in main
>     debug=debug)
>   File "vnc2swf.py", line 265, in vnc2swf
>     client.close()
>   File "vnc2swf-0.71\rfb.py", line 423, in close
>     RFBProxy.close(self)
>   File "vnc2swf-0.71\rfb.py", line 372, in close
>     self.fb.close()
>   File "vnc2swf-0.71\rfb.py", line 693, in close
>     self.stream.close()
>   File "vnc2swf-0.71\output.py", line 603, in close
>     assert not self.writer.fpstack
> AssertionError
> 
> Regards
> 
> Bill Seddon
> 
> 
> 
> -----Original Message-----
> From: vnc...@li...
> [mailto:vnc...@li...] On Behalf Of Yusuke
> Shinyama
> Sent: 28 October 2005 06:39
> To: vnc...@li...
> Cc: Radoslaw Grzanka
> Subject: [Vnc2swf-users] pyvnc2swf 0.7.1 released!
> 
> I released pyvnc2swf-0.7.1. 
> 
> Radoslaw Grzanka sent me a patch for the MemoryError bug. (Thanks!)
> So now this version (hopefully) works fine in Windows XP...
> For those who are interested in, please grab and test it!
> 
> http://www.unixuser.org/~euske/vnc2swf/pyvnc2swf-0.7.1.tar.gz
> 
> Thank you,
> Yusuke

Re: [Vnc2swf-users] Problem with OSX 10.4

[Yusuke S. <yu...@cs...>]

Carlo,

It looks like you've installed a wrong version of Pygame, but
not sure. Type the following and tell me what happens.
If you get an ImportError, you probably did not install the package
correctly.

 $ /Applications/pyvnc2swf-0.7.0/vnc2swf.py
 >>> import pygame
 >>> pygame.vernum

Thanks
Yusuke

Carlo Gandolfi <ga...@sk...> wrote:
> I've installed pygame-1.7.0-py2.3-macosx10.3.zip and
> PIL-1.1.5-py2.3-macosx10.3.zip from http://pythonmac.org/packages/ then I
> symlink both from /Library/Python/2.3/ to
> /System/Library/Frameworks/Python.framework/Versions/2.3/Extras/lib/python.
> 
> When I run pyvnc2swf.py I get this error:
> $ /Applications/pyvnc2swf-0.7.0/vnc2swf.py -o out.swf localhost:6
> Using pygame 1.7.0
> /Applications/pyvnc2swf-0.7.0/image.py:44: RuntimeWarning: tp_compare
> didn't return -1 or -2 for exception
>   assert (1,6) <= pygame.vernum, 'we need pygame 1.6 or newer.'
> Either Pygame or Python Imaging Library is required.
> 
> How can I solve it?
> Thanks in advance, C.

[Vnc2swf-users] vnc2swf (C version) 0.5.0 released

[Yusuke S. <yu...@cs...>]

Hi, 

Since I realized there're still some needs for the older C
version of vnc2swf, I decided to work on it a little bit.

Now this newer version does not depend on Ming.

http://www.unixuser.org/~euske/vnc2swf/vnc2swf-0.5.0.tar.gz

Yusuke

Re: [Vnc2swf-users] vnc2swf dosn't start

[Douglas S. B. <db...@br...>]

On Fri, 2005-10-28 at 18:14 +0200, panda wrote:
> Hi!
> 
> I have tryed to start vnc2swf and everytime I get this error message:
> 
> >>
> vnc2swf.py
> , line 27, in ?
>     import Tkinter, tkFileDialog, tkMessageBox
> ImportError: No module named Tkinter
> <<
> 
> Im using Windows XP SP2, Python 2.4, TightVNC 1.2.9 and pyvnc2swf-0.7.1.
> I hope you can help me.

Panda,

You probably need to do what the error is complaining about: you need to
install Tkinter. Many Python packages come with Tkinter. Maybe yours
didn't?

-Doug

> thx
> panda
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by the JBoss Inc.
> Get Certified Today * Register for a JBoss Training Course
> Free Certification Exam for All Training Attendees Through End of 2005
> Visit http://www.jboss.com/services/certification for more information
> _______________________________________________
> Vnc2swf-users mailing list
> Vnc...@li...
> https://lists.sourceforge.net/lists/listinfo/vnc2swf-users
> 
-- 
Douglas S. Blank       Computer Science
Assistant Professor    Bryn Mawr College
(610)526-6501          http://cs.brynmawr.edu/~dblank

[Vnc2swf-users] vnc2swf dosn't start

[panda <pa...@ca...>]

Hi!

I have tryed to start vnc2swf and everytime I get this error message:

>>
vnc2swf.py
, line 27, in ?
    import Tkinter, tkFileDialog, tkMessageBox
ImportError: No module named Tkinter
<<

Im using Windows XP SP2, Python 2.4, TightVNC 1.2.9 and pyvnc2swf-0.7.1.
I hope you can help me.

thx
panda

RE: [Vnc2swf-users] pyvnc2swf 0.7.1 released!

[Bill S. <bil...@ly...>]

With 0.71 I'm able to record on my WindowsXP laptop.  So far I've been
using the VNC record option and then using edit.py to convert the movies
into clipped SWFs (and this works!). =20

So I thought I'd try to record direct to SWF because then I can record
and clip the movie at the same time.  I'm using the command:

vnc2swf.py -n -o test.swf -t video -C 1024x768+0+100 -r 5 localhost 5900

The recording appears to work and I see:

Using pygame 1.7.1release
Connected: localhost:5900, preferred_encoding=3D(0,)
Password for localhost:5900:

But when I end the session, I get the message(s) below.  A .SWF file is
created but it is not playable.  What could I be doing wrong?

VNC Screen: size=3D1920x1200, name=3D'INSPIRON9300-1'
Output movie size: 1024x768
Creating movie: 'test.swf': version=3D7, size=3D1024x768, framerate=3D5,
compression=3DNone
Traceback (most recent call last):
  File "C:\Program Files\vnc2swf-0.71\vnc2swf.py", line 363, in ?
    if __name__ =3D=3D "__main__": main(sys.argv[1:])
  File "vnc2swf-0.71\vnc2swf.py", line 356, in main
    debug=3Ddebug)
  File "vnc2swf.py", line 265, in vnc2swf
    client.close()
  File "vnc2swf-0.71\rfb.py", line 423, in close
    RFBProxy.close(self)
  File "vnc2swf-0.71\rfb.py", line 372, in close
    self.fb.close()
  File "vnc2swf-0.71\rfb.py", line 693, in close
    self.stream.close()
  File "vnc2swf-0.71\output.py", line 603, in close
    assert not self.writer.fpstack
AssertionError

Regards

Bill Seddon



-----Original Message-----
From: vnc...@li...
[mailto:vnc...@li...] On Behalf Of Yusuke
Shinyama
Sent: 28 October 2005 06:39
To: vnc...@li...
Cc: Radoslaw Grzanka
Subject: [Vnc2swf-users] pyvnc2swf 0.7.1 released!

I released pyvnc2swf-0.7.1.=20

Radoslaw Grzanka sent me a patch for the MemoryError bug. (Thanks!)
So now this version (hopefully) works fine in Windows XP...
For those who are interested in, please grab and test it!

http://www.unixuser.org/~euske/vnc2swf/pyvnc2swf-0.7.1.tar.gz

Thank you,
Yusuke


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
Vnc2swf-users mailing list
Vnc...@li...
https://lists.sourceforge.net/lists/listinfo/vnc2swf-users