vnc2swf-users Mailing List for vnc2swf (Page 3)
Status: Alpha
Brought to you by:
euske
You can subscribe to this list here.
2005 |
Jan
|
Feb
(1) |
Mar
(11) |
Apr
(9) |
May
(2) |
Jun
(2) |
Jul
(7) |
Aug
(32) |
Sep
(22) |
Oct
(31) |
Nov
(54) |
Dec
(8) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2006 |
Jan
(11) |
Feb
(14) |
Mar
(2) |
Apr
(6) |
May
(13) |
Jun
(10) |
Jul
(14) |
Aug
(12) |
Sep
(13) |
Oct
(62) |
Nov
(18) |
Dec
(12) |
2007 |
Jan
(13) |
Feb
(10) |
Mar
(27) |
Apr
(1) |
May
(10) |
Jun
(1) |
Jul
|
Aug
(10) |
Sep
(21) |
Oct
(15) |
Nov
(3) |
Dec
(4) |
2008 |
Jan
(4) |
Feb
(24) |
Mar
(1) |
Apr
(9) |
May
(7) |
Jun
(11) |
Jul
(10) |
Aug
(11) |
Sep
(4) |
Oct
|
Nov
(13) |
Dec
|
2009 |
Jan
(3) |
Feb
(4) |
Mar
(6) |
Apr
(37) |
May
|
Jun
(5) |
Jul
(1) |
Aug
(2) |
Sep
(1) |
Oct
|
Nov
(20) |
Dec
|
2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
2011 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
(1) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
From: The A. <the...@gm...> - 2009-04-16 18:39:29
|
On Thu, Apr 16, 2009 at 12:06 PM, Olivier Hervieu < oli...@wa...> wrote: > I love the idea to rename pyvnc2swf to pyvncrecorder.. and i think it sould > be something like python remote recorder... because, with a modular > architecture, and in the future, we will able to record remote protocols > (not only vnc), and output this to several video format. > I think that'd be great. vncrec hasn't been maintained in a long time and pyvncrecorder would be a welcome update... like the aforementioned eschewing of a GUI. Then there's the question of what file format to record in (assuming that ffmpeg can be used for transcoding into any other formats). For most screen captures, lossless encoding doesn't just look better, it ends up being smaller too (due to large sections of identical colors and typically few colors). While it's possible to save in something like x264 or flv losslessly, it's far, far more efficient to save a gzipped RFB (VNC's format) data stream. Trying to convert to something like x264 or flv in real time is taxing (while modern computers can easily handle this for a single recording, imagine running 40 instances -- which is what I've had to do). By comparison, gzip uses a trivial amount of CPU time. For video transcoding, instead of a custom tool that can playback/edit/convert that file (like vncrec does, but very poorly), write an input filter for ffmpeg so it can read the .vnc files and convert them to whatever you want. Then you don't have to worry about what formats you want to conver to. -- http://theamigo.blogspot.com |
From: Olivier H. <oli...@wa...> - 2009-04-16 17:06:57
|
What a wonderfull discussion ... So if i resume ... there's two direction : - some wants a recording tool (with or without GUI) - some wants an authoring tool... It's now time to choose.... I don't think that the same tool can do this two different things. I love the idea to rename pyvnc2swf to pyvncrecorder.. and i think it sould be something like python remote recorder... because, with a modular architecture, and in the future, we will able to record remote protocols (not only vnc), and output this to several video format. I'm agree, with other people, to take the lead on this project and "recode" pyvnc2swf in that way. Authoring tool is a very exciting way too ... but it's not really in my interest to work on this kind of project.. So if someone wants to take the lead on this ... it will be great, and i will happy to collaborate :). ----- Mail Original ----- De: "Reid Ellis" <ra...@tn...> À: "General discussion about vnc2swf" <vnc...@li...> Envoyé: Jeudi 16 Avril 2009 17h28:59 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne Objet: Re: [Vnc2swf-users] Project Future I agree about the GUI. That can be done as a separate project that perhaps uses pyvnc code. (I'm a big PyQt fan myself). About the file formats -- I wasn't saying to support them all, just architect it so that others can add more as they like. Once you have to support two formats, architecting to support N formats is not a lot of extra work. Good design and all that. Wow, this discussion certainly stirred up some action on the list. :-) Reid On Thu Apr 16, 2009, at 11:18 AM, Yusuke Shinyama wrote: > Hi Olivier, > > Thanks for your reply. Okay... so first I think > I have to state my opinion about the project: > > * I don't want to touch GUI. Getting involved with GUI is not > worthwhile because > we'd have to spend most of the time for just debugging the interface > rather than adding or stablizing the core functions. > (Actually, I think that adding the GUI interface to pyvnc2swf was > a mistake.) > > * Depending less external libraries is better. > We're currently using only Python and Pygame and we already have > compatilibty problems (between python 2.3/2.4/2.5 and pygame 1.7/1.8 > and minor platform issues). If we start using other GUI libraries > (Tk/Gtk/Qt/Wx or whatever) or crypto/encoding libraries, I'd expect > a big mess. I personally do not want to get involved with that. > > * Just support a few rock-solid core functions is enough. > After all, this is a spare-time project. I just want something > that is > simple and working. Nothing fancy. I like a Unixy way. > > So there you go. I don't have much desire to take a control of > this project, but this is how I can support it. After spending > several years on this I'm now realizing my interest is somewhat > shifted. So if anyone really wants to be ambitious and expand the > whole functionality, go for it and I'll try to help it as much as > possible. Maybe it's the time to split the project or restart > from scratch. > > Yusuke > > On Thu, 16 Apr 2009 12:21:37 +0200 (CEST), Olivier Hervieu <oli...@wa... > > wrote: >> >> So ... why don't we use this thread to discut about the future of >> pyvnc2swf and establish a wishlist? >> >> I begin : >> >> - safe file writer (every frames is write before the tool quit on a >> SIGINT or SIGTERM...). >> - full flv support (cue points, keyframes) >> - streaming (flv?, gstreamer?) >> - better performance >> - remove GUI from the pyvnc2swf core (we can write later a GUI when >> all in the command-line is ok and it remove also dependencies to >> useless packages for frame recording) >> - removing the d3des.py and use something like pyCrypto for >> encryption purpose >> - write more readable code (and use correct indentation (pyvnc2swf >> is indent with 2 char ... ) >> >> Olivier Hervieu. ------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ Vnc2swf-users mailing list Vnc...@li... https://lists.sourceforge.net/lists/listinfo/vnc2swf-users |
From: Reid E. <ra...@tn...> - 2009-04-16 15:29:11
|
I agree about the GUI. That can be done as a separate project that perhaps uses pyvnc code. (I'm a big PyQt fan myself). About the file formats -- I wasn't saying to support them all, just architect it so that others can add more as they like. Once you have to support two formats, architecting to support N formats is not a lot of extra work. Good design and all that. Wow, this discussion certainly stirred up some action on the list. :-) Reid On Thu Apr 16, 2009, at 11:18 AM, Yusuke Shinyama wrote: > Hi Olivier, > > Thanks for your reply. Okay... so first I think > I have to state my opinion about the project: > > * I don't want to touch GUI. Getting involved with GUI is not > worthwhile because > we'd have to spend most of the time for just debugging the interface > rather than adding or stablizing the core functions. > (Actually, I think that adding the GUI interface to pyvnc2swf was > a mistake.) > > * Depending less external libraries is better. > We're currently using only Python and Pygame and we already have > compatilibty problems (between python 2.3/2.4/2.5 and pygame 1.7/1.8 > and minor platform issues). If we start using other GUI libraries > (Tk/Gtk/Qt/Wx or whatever) or crypto/encoding libraries, I'd expect > a big mess. I personally do not want to get involved with that. > > * Just support a few rock-solid core functions is enough. > After all, this is a spare-time project. I just want something > that is > simple and working. Nothing fancy. I like a Unixy way. > > So there you go. I don't have much desire to take a control of > this project, but this is how I can support it. After spending > several years on this I'm now realizing my interest is somewhat > shifted. So if anyone really wants to be ambitious and expand the > whole functionality, go for it and I'll try to help it as much as > possible. Maybe it's the time to split the project or restart > from scratch. > > Yusuke > > On Thu, 16 Apr 2009 12:21:37 +0200 (CEST), Olivier Hervieu <oli...@wa... > > wrote: >> >> So ... why don't we use this thread to discut about the future of >> pyvnc2swf and establish a wishlist? >> >> I begin : >> >> - safe file writer (every frames is write before the tool quit on a >> SIGINT or SIGTERM...). >> - full flv support (cue points, keyframes) >> - streaming (flv?, gstreamer?) >> - better performance >> - remove GUI from the pyvnc2swf core (we can write later a GUI when >> all in the command-line is ok and it remove also dependencies to >> useless packages for frame recording) >> - removing the d3des.py and use something like pyCrypto for >> encryption purpose >> - write more readable code (and use correct indentation (pyvnc2swf >> is indent with 2 char ... ) >> >> Olivier Hervieu. |
From: Yusuke S. <yu...@cs...> - 2009-04-16 15:18:14
|
Hi Olivier, Thanks for your reply. Okay... so first I think I have to state my opinion about the project: * I don't want to touch GUI. Getting involved with GUI is not worthwhile because we'd have to spend most of the time for just debugging the interface rather than adding or stablizing the core functions. (Actually, I think that adding the GUI interface to pyvnc2swf was a mistake.) * Depending less external libraries is better. We're currently using only Python and Pygame and we already have compatilibty problems (between python 2.3/2.4/2.5 and pygame 1.7/1.8 and minor platform issues). If we start using other GUI libraries (Tk/Gtk/Qt/Wx or whatever) or crypto/encoding libraries, I'd expect a big mess. I personally do not want to get involved with that. * Just support a few rock-solid core functions is enough. After all, this is a spare-time project. I just want something that is simple and working. Nothing fancy. I like a Unixy way. So there you go. I don't have much desire to take a control of this project, but this is how I can support it. After spending several years on this I'm now realizing my interest is somewhat shifted. So if anyone really wants to be ambitious and expand the whole functionality, go for it and I'll try to help it as much as possible. Maybe it's the time to split the project or restart from scratch. Yusuke On Thu, 16 Apr 2009 12:21:37 +0200 (CEST), Olivier Hervieu <oli...@wa...> wrote: > > So ... why don't we use this thread to discut about the future of pyvnc2swf and establish a wishlist? > > I begin : > > - safe file writer (every frames is write before the tool quit on a SIGINT or SIGTERM...). > - full flv support (cue points, keyframes) > - streaming (flv?, gstreamer?) > - better performance > - remove GUI from the pyvnc2swf core (we can write later a GUI when all in the command-line is ok and it remove also dependencies to useless packages for frame recording) > - removing the d3des.py and use something like pyCrypto for encryption purpose > - write more readable code (and use correct indentation (pyvnc2swf is indent with 2 char ... ) > > Olivier Hervieu. |
From: Yusuke S. <yu...@cs...> - 2009-04-16 14:44:35
|
Hi Luis, thanks for your comments. On Thu, 16 Apr 2009 05:55:53 -0700 (PDT), lfk...@ya... wrote: > > But what I really miss is an application for postprocessing the > recording, that allows editing, merging, cutting, including text > and sound, etc, with a good GUI. The recording can be done with > pvnc2swf, vncrec, TeleTeachingTool or any other tool. There > could be an effort to create an efficient recorder but in my > opinion we miss a postprocessing tool that is not tied with it's > own recorder. Personally, I think GUI is not necessarily needed for editing. Once I was planning to write another tool like edit.py that can "script" a movie with using Python; you could write something like this: movie = Movie("output.flv") movie.add_caption("title") movie.wait(10) movie.load("a.flv") movie.add_caption("this is my desktop.") movie.load("b.flv") ... Yusuke |
From: Yusuke S. <yu...@cs...> - 2009-04-16 14:26:59
|
On Thu, 16 Apr 2009 08:59:01 -0400, Reid Ellis <ra...@tn...> wrote: > If you are going to generalize for two formats, it's the same as for > *any* format. Perhaps the format should be removed from the name? > Something more like pyvncrecord or something? Personally, I would love > to have output in ogg / mpg / divx / m4p.. > > Reid Well, the input does not have to be VNC then. This kind of expansion is tempting and you can go on and on. But, IMO it's better to stick with a few de-facto standard (actually, fewer is better!) formats to keep the task manageable. I've seen a quite few open source projects which have got a really ambitious plan and never be finished. Yusuke |
From: Fabiano C. D. <fcd...@gm...> - 2009-04-16 13:44:37
|
2009/4/16 Reid Ellis <ra...@tn...>: > If you are going to generalize for two formats, it's the same as for > *any* format. Perhaps the format should be removed from the name? > Something more like pyvncrecord or something? Personally, I would love > to have output in ogg / mpg / divx / m4p.. > > Reid I think mp4 is enough... further encodings/conversions can be made with ffmpeg and mencoder. Fabiano. |
From: <lfk...@ya...> - 2009-04-16 13:22:38
|
Hi, I contributed with a few things for pyvnc2swf including the flv output. Yusuke was responsable for making it work properly, because unfortunately python is not my world. I've been thinking for a while in creating a new application in Java specially for editing and saving recordings in different formats. There are so many open source libraries in Java, including libraries for working with Flash files. There is one special project that I think is really cool: TeleTeachingTool It was developed and it's been used in a university in Germany. It allows broadcast of the screen, audio and optionally from a camera. It's been used to record long lectures and the result seems very good. It can save the recordings in flash with thumbnails created automatically. It could be improved to save in FLV format also. But what I really miss is an application for postprocessing the recording, that allows editing, merging, cutting, including text and sound, etc, with a good GUI. The recording can be done with pvnc2swf, vncrec, TeleTeachingTool or any other tool. There could be an effort to create an efficient recorder but in my opinion we miss a postprocessing tool that is not tied with it's own recorder. Luis Fernando ________________________________ De: Olivier Hervieu <oli...@wa...> Para: Yusuke Shinyama <yu...@cs...> Cc: General discussion about vnc2swf <vnc...@li...> Enviadas: Quinta-feira, 16 de Abril de 2009 7:21:37 Assunto: Re: [Vnc2swf-users] Project Future Interressed??? Maybe yes and maybe not... In fact in the last days, i was thinking about a complete rewriting of pyvnc2swf ... to feet my special desire.. which looks like more a tool called pyvnc2FLV!. In fact ... the compliency with other format will be easy to do (thanks to object model and python) ... But i think that if pyvnc2swf firstly become a tool for record and stream vlc session in flv format, it will be great and a good beginning!! With help of others .... we can manage this kind of evolution.. Don't know because we have to establish a wishlist of what user wants of pyvnc2swf to get it involved... If this should lead to two different tools, new tools will emerge from pyvnc2swf. So ... why don't we use this thread to discut about the future of pyvnc2swf and establish a wishlist? I begin : - safe file writer (every frames is write before the tool quit on a SIGINT or SIGTERM...). - full flv support (cue points, keyframes) - streaming (flv?, gstreamer?) - better performance - remove GUI from the pyvnc2swf core (we can write later a GUI when all in the command-line is ok and it remove also dependencies to useless packages for frame recording) - removing the d3des.py and use something like pyCrypto for encryption purpose - write more readable code (and use correct indentation (pyvnc2swf is indent with 2 char ... ) Olivier Hervieu. ----- Mail Original ----- De: "Yusuke Shinyama" <yu...@cs...> À: "Olivier Hervieu" <oli...@wa...>, "General discussion about vnc2swf" <vnc...@li...> Envoyé: Jeudi 16 Avril 2009 01h06:10 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne Objet: Project Future Hi, On Mon, 06 Apr 2009 11:15:11 +0200, Olivier Hervieu <oli...@wa...> wrote: > Unfortunately, I do not know the desires of Euske on the roadmap of the > product ... As a matter of fact, I'm recently getting less keen on this project. It's not like that I completely lost my interest, but simply it's not in my top priority anymore. Maybe it changes in future, or maybe not. Anyway, my response for these requests are now slow. Sorry! If someone is still interested in improving this piece of software, I'd rather hand the project to that person and let them develop it for suiting their own purposes. So, Olivier, aren't you interested in taking on this project? Or anyone else? I can give an administrator account. If you're not inclined to use SourceForge, it's okay to move to other hosting sites. Currently the main page of vnc2swf is hosted on my personal page, so I can change that to point some other sites too. (I'm eager to make the transision smooth to avoid users' confusion.) Please let me know if anyone is interested. Best, Yusuke ------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ Vnc2swf-users mailing list Vnc...@li... https://lists.sourceforge.net/lists/listinfo/vnc2swf-users Veja quais são os assuntos do momento no Yahoo! +Buscados http://br.maisbuscados.yahoo.com |
From: Reid E. <ra...@tn...> - 2009-04-16 13:17:13
|
If you are going to generalize for two formats, it's the same as for *any* format. Perhaps the format should be removed from the name? Something more like pyvncrecord or something? Personally, I would love to have output in ogg / mpg / divx / m4p.. Reid On Thu Apr 16, 2009, at 6:21 AM, Olivier Hervieu wrote: > Interressed??? Maybe yes and maybe not... > > In fact in the last days, i was thinking about a complete rewriting > of pyvnc2swf ... to feet my special desire.. which looks like more a > tool called pyvnc2FLV!. > > In fact ... the compliency with other format will be easy to do > (thanks to object model and python) ... But i think that if > pyvnc2swf firstly become a tool for record and stream vlc session in > flv format, it will be great and a good beginning!! > > With help of others .... we can manage this kind of evolution.. > Don't know because we have to establish a wishlist of what user > wants of pyvnc2swf to get it involved... If this should lead to two > different tools, new tools will emerge from pyvnc2swf. > > So ... why don't we use this thread to discut about the future of > pyvnc2swf and establish a wishlist? > > I begin : > > - safe file writer (every frames is write before the tool quit on a > SIGINT or SIGTERM...). > - full flv support (cue points, keyframes) > - streaming (flv?, gstreamer?) > - better performance > - remove GUI from the pyvnc2swf core (we can write later a GUI when > all in the command-line is ok and it remove also dependencies to > useless packages for frame recording) > - removing the d3des.py and use something like pyCrypto for > encryption purpose > - write more readable code (and use correct indentation (pyvnc2swf > is indent with 2 char ... ) > > Olivier Hervieu. > > > ----- Mail Original ----- > De: "Yusuke Shinyama" <yu...@cs...> > À: "Olivier Hervieu" <oli...@wa...>, "General > discussion about vnc2swf" <vnc...@li...> > Envoyé: Jeudi 16 Avril 2009 01h06:10 GMT +01:00 Amsterdam / Berlin / > Berne / Rome / Stockholm / Vienne > Objet: Project Future > > Hi, > > On Mon, 06 Apr 2009 11:15:11 +0200, Olivier Hervieu <oli...@wa... > > wrote: >> Unfortunately, I do not know the desires of Euske on the roadmap of >> the >> product ... > > As a matter of fact, I'm recently getting less keen on this project. > It's not like that I completely lost my interest, but simply it's > not in > my top priority anymore. Maybe it changes in future, or maybe not. > > Anyway, my response for these requests are now slow. Sorry! > If someone is still interested in improving this piece of > software, I'd rather hand the project to that person and let them > develop it for suiting their own purposes. > > So, Olivier, aren't you interested in taking on this project? > Or anyone else? I can give an administrator account. > If you're not inclined to use SourceForge, it's okay to move > to other hosting sites. > Currently the main page of vnc2swf is hosted on my personal page, > so I can change that to point some other sites too. > (I'm eager to make the transision smooth to avoid users' confusion.) > > Please let me know if anyone is interested. > > Best, > Yusuke |
From: Olivier H. <oli...@wa...> - 2009-04-16 10:21:55
|
Interressed??? Maybe yes and maybe not... In fact in the last days, i was thinking about a complete rewriting of pyvnc2swf ... to feet my special desire.. which looks like more a tool called pyvnc2FLV!. In fact ... the compliency with other format will be easy to do (thanks to object model and python) ... But i think that if pyvnc2swf firstly become a tool for record and stream vlc session in flv format, it will be great and a good beginning!! With help of others .... we can manage this kind of evolution.. Don't know because we have to establish a wishlist of what user wants of pyvnc2swf to get it involved... If this should lead to two different tools, new tools will emerge from pyvnc2swf. So ... why don't we use this thread to discut about the future of pyvnc2swf and establish a wishlist? I begin : - safe file writer (every frames is write before the tool quit on a SIGINT or SIGTERM...). - full flv support (cue points, keyframes) - streaming (flv?, gstreamer?) - better performance - remove GUI from the pyvnc2swf core (we can write later a GUI when all in the command-line is ok and it remove also dependencies to useless packages for frame recording) - removing the d3des.py and use something like pyCrypto for encryption purpose - write more readable code (and use correct indentation (pyvnc2swf is indent with 2 char ... ) Olivier Hervieu. ----- Mail Original ----- De: "Yusuke Shinyama" <yu...@cs...> À: "Olivier Hervieu" <oli...@wa...>, "General discussion about vnc2swf" <vnc...@li...> Envoyé: Jeudi 16 Avril 2009 01h06:10 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne Objet: Project Future Hi, On Mon, 06 Apr 2009 11:15:11 +0200, Olivier Hervieu <oli...@wa...> wrote: > Unfortunately, I do not know the desires of Euske on the roadmap of the > product ... As a matter of fact, I'm recently getting less keen on this project. It's not like that I completely lost my interest, but simply it's not in my top priority anymore. Maybe it changes in future, or maybe not. Anyway, my response for these requests are now slow. Sorry! If someone is still interested in improving this piece of software, I'd rather hand the project to that person and let them develop it for suiting their own purposes. So, Olivier, aren't you interested in taking on this project? Or anyone else? I can give an administrator account. If you're not inclined to use SourceForge, it's okay to move to other hosting sites. Currently the main page of vnc2swf is hosted on my personal page, so I can change that to point some other sites too. (I'm eager to make the transision smooth to avoid users' confusion.) Please let me know if anyone is interested. Best, Yusuke |
From: Yusuke S. <yu...@cs...> - 2009-04-15 23:06:27
|
Hi, On Mon, 06 Apr 2009 11:15:11 +0200, Olivier Hervieu <oli...@wa...> wrote: > Unfortunately, I do not know the desires of Euske on the roadmap of the > product ... As a matter of fact, I'm recently getting less keen on this project. It's not like that I completely lost my interest, but simply it's not in my top priority anymore. Maybe it changes in future, or maybe not. Anyway, my response for these requests are now slow. Sorry! If someone is still interested in improving this piece of software, I'd rather hand the project to that person and let them develop it for suiting their own purposes. So, Olivier, aren't you interested in taking on this project? Or anyone else? I can give an administrator account. If you're not inclined to use SourceForge, it's okay to move to other hosting sites. Currently the main page of vnc2swf is hosted on my personal page, so I can change that to point some other sites too. (I'm eager to make the transision smooth to avoid users' confusion.) Please let me know if anyone is interested. Best, Yusuke |
From: Oscar U. <osc...@pr...> - 2009-04-14 16:41:45
|
doh, edit.py does this ... ty > ----- Original Message ----- > From: "Olivier Hervieu" <oli...@wa...> > To: "General discussion about vnc2swf" <vnc...@li...> > Subject: Re: [Vnc2swf-users] How to set FLV meta data (was Re: About FLV output.) > Date: Tue, 14 Apr 2009 13:55:57 +0200 > > > You can insert cue points in flv's... See : > http://livedocs.adobe.com/flash/8/main/wwhelp/wwhimpl/common/html/wwhelp.htm?context=LiveDocs_Parts&file=00003484.html > > Regards, > > Olivier. > > Oscar Usifer a écrit : > > Another question, is there a way to get a png image preview, or > > the first image frame of the flv? Thanks, > > OSC > > > > PS Great info Amigo, thanks... :D I will try and report back. > > > > > >> ----- Original Message ----- > >> From: "The Amigo" <the...@gm...> > >> To: "General discussion about vnc2swf" <vnc...@li...> > >> Subject: Re: [Vnc2swf-users] How to set FLV meta data (was Re: > >> About FLV output.) > >> Date: Fri, 3 Apr 2009 15:46:31 -0500 > >> > >> > >> I used pyvnc2swf for a bit, but found that it took far too much CPU time. > >> Instead, here's what I do now: > >> > >> 1) Use this patched vncrec: http://aur.archlinux.org/packages.php?ID=16265 > >> In addition to simply recording vnc sessions to a log file, it can convert > >> the recordings to YUV4MPEG (the twibright patch) on stdout (my patch). > >> > >> 2) Use ffmpeg to read the YUV4MPEG stream and write an .flv > >> > >> A couple of caveats however: > >> - vncrec needs an X display (use Xvfb to create a virtual one, but make > >> sure it's at least as large as your video) > >> - flashsv is the lossless video codec that will generally produce smaller > >> files for screen recordings while maintaining perfect quality > >> - if your ffmpeg doesn't have flashsv support and you have to compile from > >> source, install zlib-devel > >> - scaling down the video size with ffmpeg will often result in a larger > >> file size (due to the added anti-aliasing), for web-based playback, you can > >> save bandwidth by having a swf player scale the video down. > >> > >> -- > >> http://theamigo.blogspot.com > >> > >> ------------------------------------------------------------------------------ > >> > >> _______________________________________________ > >> Vnc2swf-users mailing list > >> Vnc...@li... > >> https://lists.sourceforge.net/lists/listinfo/vnc2swf-users > >> > > > > > > > > > > > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > High Quality Requirements in a Collaborative Environment. > Download a free trial of Rational Requirements Composer Now! > http://p.sf.net/sfu/www-ibm-com > _______________________________________________ > Vnc2swf-users mailing list > Vnc...@li... > https://lists.sourceforge.net/lists/listinfo/vnc2swf-users > -- It's News. It's Reviews. It's Interviews. It's Free. What Are You Waiting For? www.movieline.com |
From: Olivier H. <oli...@wa...> - 2009-04-14 11:55:45
|
You can insert cue points in flv's... See : http://livedocs.adobe.com/flash/8/main/wwhelp/wwhimpl/common/html/wwhelp.htm?context=LiveDocs_Parts&file=00003484.html Regards, Olivier. Oscar Usifer a écrit : > Another question, is there a way to get a png image preview, or the first image frame of the flv? > > Thanks, > OSC > > PS Great info Amigo, thanks... :D I will try and report back. > > >> ----- Original Message ----- >> From: "The Amigo" <the...@gm...> >> To: "General discussion about vnc2swf" <vnc...@li...> >> Subject: Re: [Vnc2swf-users] How to set FLV meta data (was Re: About FLV output.) >> Date: Fri, 3 Apr 2009 15:46:31 -0500 >> >> >> I used pyvnc2swf for a bit, but found that it took far too much CPU time. >> Instead, here's what I do now: >> >> 1) Use this patched vncrec: http://aur.archlinux.org/packages.php?ID=16265 >> In addition to simply recording vnc sessions to a log file, it can convert >> the recordings to YUV4MPEG (the twibright patch) on stdout (my patch). >> >> 2) Use ffmpeg to read the YUV4MPEG stream and write an .flv >> >> A couple of caveats however: >> - vncrec needs an X display (use Xvfb to create a virtual one, but make >> sure it's at least as large as your video) >> - flashsv is the lossless video codec that will generally produce smaller >> files for screen recordings while maintaining perfect quality >> - if your ffmpeg doesn't have flashsv support and you have to compile from >> source, install zlib-devel >> - scaling down the video size with ffmpeg will often result in a larger >> file size (due to the added anti-aliasing), for web-based playback, you can >> save bandwidth by having a swf player scale the video down. >> >> -- >> http://theamigo.blogspot.com >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> Vnc2swf-users mailing list >> Vnc...@li... >> https://lists.sourceforge.net/lists/listinfo/vnc2swf-users >> > > > > > |
From: Oscar U. <osc...@pr...> - 2009-04-13 21:11:16
|
Another question, is there a way to get a png image preview, or the first image frame of the flv? Thanks, OSC PS Great info Amigo, thanks... :D I will try and report back. > ----- Original Message ----- > From: "The Amigo" <the...@gm...> > To: "General discussion about vnc2swf" <vnc...@li...> > Subject: Re: [Vnc2swf-users] How to set FLV meta data (was Re: About FLV output.) > Date: Fri, 3 Apr 2009 15:46:31 -0500 > > > I used pyvnc2swf for a bit, but found that it took far too much CPU time. > Instead, here's what I do now: > > 1) Use this patched vncrec: http://aur.archlinux.org/packages.php?ID=16265 > In addition to simply recording vnc sessions to a log file, it can convert > the recordings to YUV4MPEG (the twibright patch) on stdout (my patch). > > 2) Use ffmpeg to read the YUV4MPEG stream and write an .flv > > A couple of caveats however: > - vncrec needs an X display (use Xvfb to create a virtual one, but make > sure it's at least as large as your video) > - flashsv is the lossless video codec that will generally produce smaller > files for screen recordings while maintaining perfect quality > - if your ffmpeg doesn't have flashsv support and you have to compile from > source, install zlib-devel > - scaling down the video size with ffmpeg will often result in a larger > file size (due to the added anti-aliasing), for web-based playback, you can > save bandwidth by having a swf player scale the video down. > > -- > http://theamigo.blogspot.com > > ------------------------------------------------------------------------------ > > _______________________________________________ > Vnc2swf-users mailing list > Vnc...@li... > https://lists.sourceforge.net/lists/listinfo/vnc2swf-users > -- Be Yourself @ mail.com! Choose From 200+ Email Addresses Get a Free Account at www.mail.com |
From: Olivier H. <oli...@wa...> - 2009-04-06 09:14:49
|
interesting .. it's a way to consider for the future of pyvnc2swf .. Unfortunately, I do not know the desires of Euske on the roadmap of the product ... Regards, Olivier. The Amigo a écrit : > I used pyvnc2swf for a bit, but found that it took far too much CPU > time. Instead, here's what I do now: > > 1) Use this patched vncrec: http://aur.archlinux.org/packages.php?ID=16265 > In addition to simply recording vnc sessions to a log file, it can > convert the recordings to YUV4MPEG (the twibright patch) on stdout (my > patch). > > 2) Use ffmpeg to read the YUV4MPEG stream and write an .flv > > A couple of caveats however: > - vncrec needs an X display (use Xvfb to create a virtual one, but > make sure it's at least as large as your video) > - flashsv is the lossless video codec that will generally produce > smaller files for screen recordings while maintaining perfect quality > - if your ffmpeg doesn't have flashsv support and you have to compile > from source, install zlib-devel > - scaling down the video size with ffmpeg will often result in a > larger file size (due to the added anti-aliasing), for web-based > playback, you can save bandwidth by having a swf player scale the > video down. > > -- > http://theamigo.blogspot.com > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > > ------------------------------------------------------------------------ > > _______________________________________________ > Vnc2swf-users mailing list > Vnc...@li... > https://lists.sourceforge.net/lists/listinfo/vnc2swf-users > |
From: Olivier H. <oli...@wa...> - 2009-04-06 09:11:10
|
Greetings! I use flvtool2... with my little patch, when i ask to display metadata i have : $ flvtool2 -P /home/XXXXXXXX/test.flv --- /home/XXXXXXXX/test.flv: framerate: 24 canSeekToEnd: true uselessdatabuff: duration: 42 I don't know flvtool++ and i have no time since the end of april to look at it.... But can you seek into your produced flv with my patch ? Oscar Usifer a écrit : > Folks, > > FLV "keyframes" meta data apparently is not being set correctly, even after updating and patching flvtool++-1.1.7. It may be useful to us to ask the author of that tool for a fix. As a result, steaming seeks is not possible. Can others corroborate this finding? > > Thanks, > OSC > > > > > >> ----- Original Message ----- >> From: "Olivier Hervieu" <oli...@wa...> >> To: "Oscar Usifer" <osc...@pr...> >> Cc: "General discussion about vnc2swf" <vnc...@li...> >> Subject: Re: How to set FLV meta data (was Re: [Vnc2swf-users] About FLV output.) >> Date: Fri, 03 Apr 2009 10:19:17 +0200 >> >> >> Greetings! >> >> Yes, the resulted diff shows a minimal workaround to add some >> metadata to the resulting flv (in fact framerate and duration). >> These one are needed, otherwise, produced flv files are not >> correctly read with flv players (such as FlowPlayer). >> >> But it's still 'experimental'. And it will be nice to insert all >> metadata like flvtool++ or flvtool2 does. On the other side, >> flvtool++ or flvtool2 are post treatment tool. And, more your flv >> file is heavy, more your post treatment is long... >> >> In an ideal world, there should be inclusion of all the metadata >> (such as flvtool + +) at creation time of the flv by vnc2swf .... >> Still work to do! >> >> If you're interested by this, read the following documentation : >> >> http://osflash.org/flv >> http://pyamf.org/ >> >> Olivier. >> >> Oscar Usifer a écrit : >> >>> Folks, >>> >>> I updated __init__.py and commented out import play, and that got >>> me further, so I could at least test. The result of this, was >>> being able to use the vnc2swf-recorder script to output .flv >>> reading from a streaming stdin input. However the resulting >>> output files contained blank frames. Seeing that v.0.10.0 swf.py >>> had the updates to write out the meta-data for .flv formats, I >>> attempted to simply update this file with the diff, but with the >>> same bad result as before. Below is an approximate diff. >>> "flvtool++" (v.1.1) apparently is a work around for this >>> situation. It will create the flv meta data, but does not write >>> the correct height meta-data value either because pyvnc2swf >>> writes it incorrectly (see swf.py use of 'rect' in FLVWriter), or >>> because flvtool++.cpp does uses an incorrect algorithm to read >>> it. The diff resolves this. >>> >>> Thanks >>> >>> [osc@builder-freebsd ~/packages/flvtool++/src/patch]$ diff >>> flvtool++.cpp /usr/ports/multimedia/flvtool++/work/flvtool++.cpp >>> 190,191c190,191 >>> < h = ((*(vptr++)) & 0x0f) << 8; >>> < h += ((*(vptr++)) & 0xff); >>> --- >>> >>> >>>> h = ((*(vptr++)) & 0xff) << 4; >>>> h = ((*(vptr++)) & 0xf0) >> 4; >>>> >>>> >>> [osc@rt01 /var/ee/www/swf]$ ~/flvtool++ /tmp/FILM078.flv >>> /tmp/FILM078.2.flv Video: 878x629 SCREEN >>> Total: 313234 video bytes (190.329029 kbps), 0 audio bytes >>> (0.000000 kbps), 13.166000 seconds long >>> Final onMetaData tag contents: { audiodatarate: 0.000000 >>> audiosize: 0.000000 >>> canSeekToEnd: true >>> datasize: 316322.000000 >>> duration: 13.166000 >>> framerate: 12.076561 >>> hasAudio: false >>> hasCuePoints: false >>> hasKeyframes: true >>> hasMetadata: true >>> hasVideo: true >>> height: 629.000000 >>> keyframes: { filepositions: { 544.000000 >>> } >>> times: { 0.000000 >>> } >>> } >>> lasttimestamp: 13.166000 >>> metadatacreator: flvtool++ (Facebook, Motion project, dweatherford) >>> metadatadate: Thu Apr 2 22:10:27 2009 >>> totalframes: 159.000000 >>> videocodecid: 3.000000 >>> videodatarate: 190.329029 >>> videosize: 313234.000000 >>> width: 878.000000 >>> } >>> >>> >>> >>> [osc@builder-freebsd >>> ~/packages/vnc2swf/src/pyvnc2swf-0.9.5/pyvnc2swf]$ diff >>> swf-0.10.0.py swf.py 854d853 >>> < 857,871d855 >>> < < # Meta Data information must be at the start of the file.... >>> < # Reserve here an area of 100 char to store meta data information >>> < # I know this is a bit ugly.. But i have no better idea... >>> < i = 0 < self.pos = self.outfp.tell() >>> < self.writeui8(18) >>> < self.writeub24(100) < self.writeub24(0) >>> < self.writeui32(0) >>> < self.outfp.flush() >>> < while i < 100: >>> < self.writeui8(0) >>> < i = i+1 < self.writeub32(111) 885,926d868 >>> < # To be correctly played into a FLV Player, flv files has >>> to handle some meta data >>> < # With framerate and duration, many flv player successfully >>> read the produced >>> < # FLV Stream >>> < import struct >>> < < # Flushing all the remaining data < self.outfp.flush() >>> < < # Write metadata information >>> < self.outfp.seek(self.pos) < < # The needed metadata >>> are stored in flv with amf format. >>> < # For documentation, see : < # - http://osflash.org/flv >>> < # - http://pyamf.org/ >>> < # Following metadata was generated with the help of pyamf >>> < < duration = framecount / self.framerate >>> < meta = '\x02\x00\nonMetaData\x08\x00\x00\x00\x00\x00\x08' >>> < meta += 'duration\x02' + >>> struct.pack('>H',len(str(duration))) + str(duration) >>> < meta += '\x00\x0ccanSeekToEnd\x01\x01\x00\t' >>> < meta += 'framerate\x02' + >>> struct.pack('>H',len(str(self.framerate))) + str(self.framerate) >>> + '\x00' >>> < # writing metadata duration >>> < self.writeui8(18) >>> < self.writeub24(100) >>> < self.writeub24(0) >>> < self.writeui32(0) >>> < # Insert pseudo Data to fill the rest of the reserved space >>> < rest = 100 -len(meta) -22 >>> < meta +='\x0fuselessdatabuff\x02' + struct.pack('>H',rest) >>> < data = '' >>> < while len(data)<rest: >>> < # Inserting Blank Data >>> < data += '\x00' >>> < meta += data >>> < meta += '\x00\x00\t' >>> < self.write(meta) >>> < print len(meta) >>> < self.writeub32(111) >>> < < self.outfp.seek(0,2) #The end of file >>> < self.outfp.flush() >>> >>> Command I am using test For v. 0.10.0 >>> 400 zcat FILM075.vnc.gz | vnc2swf-recorder -n -z -o /tmp/FILM078.flv -V >>> >>> For v. 0.9.5 >>> 411 zcat FILM078.vnc.gz | /usr/local/pyvnc2swf/bin/vnc2swf.py >>> -n -z -o /tmp/FILM078.flv -V >>> >>> >>> >>> >>>> ----- Original Message ----- >>>> From: "Oscar Usifer" <osc...@pr...> >>>> To: oli...@wa... >>>> Cc: "General discussion about vnc2swf" <vnc...@li...> >>>> Subject: Re: [Vnc2swf-users] About FLV output. >>>> Date: Thu, 2 Apr 2009 13:52:36 -0500 >>>> >>>> >>>> It complains pygame is not installed. Is there a version that >>>> uses PIL instead, or is there a setup option to set it to use >>>> PIL? >>>> >>>> Thanks >>>> >>>> >>>> >>>> >>>> >>>>> ----- Original Message ----- >>>>> From: "Olivier Hervieu" <oli...@wa...> >>>>> To: "Oscar Usifer" <osc...@pr...> >>>>> Cc: "General discussion about vnc2swf" >>>>> <vnc...@li...> >>>>> Subject: Re: [Vnc2swf-users] About FLV output. >>>>> Date: Thu, 02 Apr 2009 10:26:44 +0200 >>>>> >>>>> >>>>> The attached tarball has a setup.py that respect standard >>>>> python distribution style. >>>>> >>>>> Run >>>>> >>>>> python setup.py build >>>>> python setup.py install >>>>> >>>>> You can have some help by running >>>>> >>>>> 'python setup.py --help' or 'python setup.py --help [command name]' >>>>> >>>>> Forget the old makefile. I leave it here for euske. >>>>> >>>>> Regards, >>>>> >>>>> Olivier. >>>>> >>>>> Oscar Usifer a écrit : >>>>> >>>>> >>>>>> Greets Olivier, >>>>>> >>>>>> Just a few requests. I would like to test it out, but am not >>>>>> >>>>> able > to get it into an installed state. I tried to run >>>>> setup.py, but > it seems to output usage along the way instead >>>>> of actually > performing an install. I was not able to use your >>>>> package, as > make fails as well. Could you please update so >>>>> that it is > compatible with the current build system? Also, I >>>>> have a target > system that I use for installation, so the >>>>> setup/make would need > an option to install into a target >>>>> directory instead of into a > system. I can take your work and >>>>> figure out how to get it > completely installed, but not >>>>> everyone has the time or desire to > go to that level of energy >>>>> output. Also, I am beginner level with > Python, which makes it >>>>> less accessible. >>>>> >>>>> >>>>>> Thanks, >>>>>> OSC >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>> ----- Original Message ----- >>>>>>> From: "Olivier Hervieu" <oli...@wa...> >>>>>>> To: vnc...@li..., "Yusuke Shinyama" >> >>>>>>> >>>>> <yu...@cs...> >>>>> >>>>> >>>>>>> Subject: [Vnc2swf-users] About FLV output. >>>>>>> Date: Mon, 30 Mar 2009 16:49:48 +0200 >>>>>>> >>>>>>> >>>>>>> Hi all, >>>>>>> >>>>>>> Vnc2swf can produce FLV. But produced files present some drawbacks. >>>>>>> >>>>>>> - files has only one keyframe (also report a few weeks ago), >>>>>>> - files has no metadata. This means that support of pyvnc2swf >>>>>>> FLV files is not complete for most FLV players (impossible to >>>>>>> scroll, total record time is not available (a good example : >>>>>>> test your pyvnc2swf FlV in FlowPlayer)). >>>>>>> >>>>>>> I attach a tarball containing some modifications: >>>>>>> >>>>>>> - add a '-k' option to specify the keyframe rate >>>>>>> - Add meta data on the produced flv. >>>>>>> >>>>>>> Note that I also repackage pyvnc2swf to be more pythonic. >> >>>>>>> >>>>> Vnc2swf scripts, edit and play are replaced by scripts >> >>>>> vnc2swf-recorder, vnc2swf-editor and vnc2swf player. The >> >>>>> distribution is now built and installed with setuptools. >>>>> >>>>> >>>>>>> The Cli interface was successfully tested on Ubuntu 8.04 and >>>>>>> Debian Lenny. >>>>>>> >>>>>>> Also note that I did not (and do not want to) install >>>>>>> >>>>> python-tk. >> I paid attention to add some options in the GUI. >>>>> But these >> changes are not yet tested,. >>>>> >>>>> >>>>>>> I leave to Euske or others to test and commit these changes. >>>>>>> >>>>>>> Regards, >>>>>>> >>>>>>> Olivier Hervieu. >>>>>>> << pyvnc2swf-0.10.0.tar.gz >> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>> -- >>>> Be Yourself @ mail.com! >>>> Choose From 200+ Email Addresses >>>> Get a Free Account at www.mail.com >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> _______________________________________________ >>>> Vnc2swf-users mailing list >>>> Vnc...@li... >>>> https://lists.sourceforge.net/lists/listinfo/vnc2swf-users >>>> >>>> >>> >>> >>> >>> > > > > > |
From: The A. <the...@gm...> - 2009-04-03 20:46:37
|
I used pyvnc2swf for a bit, but found that it took far too much CPU time. Instead, here's what I do now: 1) Use this patched vncrec: http://aur.archlinux.org/packages.php?ID=16265 In addition to simply recording vnc sessions to a log file, it can convert the recordings to YUV4MPEG (the twibright patch) on stdout (my patch). 2) Use ffmpeg to read the YUV4MPEG stream and write an .flv A couple of caveats however: - vncrec needs an X display (use Xvfb to create a virtual one, but make sure it's at least as large as your video) - flashsv is the lossless video codec that will generally produce smaller files for screen recordings while maintaining perfect quality - if your ffmpeg doesn't have flashsv support and you have to compile from source, install zlib-devel - scaling down the video size with ffmpeg will often result in a larger file size (due to the added anti-aliasing), for web-based playback, you can save bandwidth by having a swf player scale the video down. -- http://theamigo.blogspot.com |
From: Oscar U. <osc...@pr...> - 2009-04-03 17:52:25
|
Folks, FLV "keyframes" meta data apparently is not being set correctly, even after updating and patching flvtool++-1.1.7. It may be useful to us to ask the author of that tool for a fix. As a result, steaming seeks is not possible. Can others corroborate this finding? Thanks, OSC > ----- Original Message ----- > From: "Olivier Hervieu" <oli...@wa...> > To: "Oscar Usifer" <osc...@pr...> > Cc: "General discussion about vnc2swf" <vnc...@li...> > Subject: Re: How to set FLV meta data (was Re: [Vnc2swf-users] About FLV output.) > Date: Fri, 03 Apr 2009 10:19:17 +0200 > > > Greetings! > > Yes, the resulted diff shows a minimal workaround to add some > metadata to the resulting flv (in fact framerate and duration). > These one are needed, otherwise, produced flv files are not > correctly read with flv players (such as FlowPlayer). > > But it's still 'experimental'. And it will be nice to insert all > metadata like flvtool++ or flvtool2 does. On the other side, > flvtool++ or flvtool2 are post treatment tool. And, more your flv > file is heavy, more your post treatment is long... > > In an ideal world, there should be inclusion of all the metadata > (such as flvtool + +) at creation time of the flv by vnc2swf .... > Still work to do! > > If you're interested by this, read the following documentation : > > http://osflash.org/flv > http://pyamf.org/ > > Olivier. > > Oscar Usifer a écrit : > > Folks, > > > > I updated __init__.py and commented out import play, and that got > > me further, so I could at least test. The result of this, was > > being able to use the vnc2swf-recorder script to output .flv > > reading from a streaming stdin input. However the resulting > > output files contained blank frames. Seeing that v.0.10.0 swf.py > > had the updates to write out the meta-data for .flv formats, I > > attempted to simply update this file with the diff, but with the > > same bad result as before. Below is an approximate diff. > > "flvtool++" (v.1.1) apparently is a work around for this > > situation. It will create the flv meta data, but does not write > > the correct height meta-data value either because pyvnc2swf > > writes it incorrectly (see swf.py use of 'rect' in FLVWriter), or > > because flvtool++.cpp does uses an incorrect algorithm to read > > it. The diff resolves this. > > > > Thanks > > > > [osc@builder-freebsd ~/packages/flvtool++/src/patch]$ diff > > flvtool++.cpp /usr/ports/multimedia/flvtool++/work/flvtool++.cpp > > 190,191c190,191 > > < h = ((*(vptr++)) & 0x0f) << 8; > > < h += ((*(vptr++)) & 0xff); > > --- > > > >> h = ((*(vptr++)) & 0xff) << 4; > >> h = ((*(vptr++)) & 0xf0) >> 4; > >> > > > > [osc@rt01 /var/ee/www/swf]$ ~/flvtool++ /tmp/FILM078.flv > > /tmp/FILM078.2.flv Video: 878x629 SCREEN > > Total: 313234 video bytes (190.329029 kbps), 0 audio bytes > > (0.000000 kbps), 13.166000 seconds long > > Final onMetaData tag contents: { audiodatarate: 0.000000 > > audiosize: 0.000000 > > canSeekToEnd: true > > datasize: 316322.000000 > > duration: 13.166000 > > framerate: 12.076561 > > hasAudio: false > > hasCuePoints: false > > hasKeyframes: true > > hasMetadata: true > > hasVideo: true > > height: 629.000000 > > keyframes: { filepositions: { 544.000000 > > } > > times: { 0.000000 > > } > > } > > lasttimestamp: 13.166000 > > metadatacreator: flvtool++ (Facebook, Motion project, dweatherford) > > metadatadate: Thu Apr 2 22:10:27 2009 > > totalframes: 159.000000 > > videocodecid: 3.000000 > > videodatarate: 190.329029 > > videosize: 313234.000000 > > width: 878.000000 > > } > > > > > > > > [osc@builder-freebsd > > ~/packages/vnc2swf/src/pyvnc2swf-0.9.5/pyvnc2swf]$ diff > > swf-0.10.0.py swf.py 854d853 > > < 857,871d855 > > < < # Meta Data information must be at the start of the file.... > > < # Reserve here an area of 100 char to store meta data information > > < # I know this is a bit ugly.. But i have no better idea... > > < i = 0 < self.pos = self.outfp.tell() > > < self.writeui8(18) > > < self.writeub24(100) < self.writeub24(0) > > < self.writeui32(0) > > < self.outfp.flush() > > < while i < 100: > > < self.writeui8(0) > > < i = i+1 < self.writeub32(111) 885,926d868 > > < # To be correctly played into a FLV Player, flv files has > > to handle some meta data > > < # With framerate and duration, many flv player successfully > > read the produced > > < # FLV Stream > > < import struct > > < < # Flushing all the remaining data < self.outfp.flush() > > < < # Write metadata information > > < self.outfp.seek(self.pos) < < # The needed metadata > > are stored in flv with amf format. > > < # For documentation, see : < # - http://osflash.org/flv > > < # - http://pyamf.org/ > > < # Following metadata was generated with the help of pyamf > > < < duration = framecount / self.framerate > > < meta = '\x02\x00\nonMetaData\x08\x00\x00\x00\x00\x00\x08' > > < meta += 'duration\x02' + > > struct.pack('>H',len(str(duration))) + str(duration) > > < meta += '\x00\x0ccanSeekToEnd\x01\x01\x00\t' > > < meta += 'framerate\x02' + > > struct.pack('>H',len(str(self.framerate))) + str(self.framerate) > > + '\x00' > > < # writing metadata duration > > < self.writeui8(18) > > < self.writeub24(100) > > < self.writeub24(0) > > < self.writeui32(0) > > < # Insert pseudo Data to fill the rest of the reserved space > > < rest = 100 -len(meta) -22 > > < meta +='\x0fuselessdatabuff\x02' + struct.pack('>H',rest) > > < data = '' > > < while len(data)<rest: > > < # Inserting Blank Data > > < data += '\x00' > > < meta += data > > < meta += '\x00\x00\t' > > < self.write(meta) > > < print len(meta) > > < self.writeub32(111) > > < < self.outfp.seek(0,2) #The end of file > > < self.outfp.flush() > > > > Command I am using test For v. 0.10.0 > > 400 zcat FILM075.vnc.gz | vnc2swf-recorder -n -z -o /tmp/FILM078.flv -V > > > > For v. 0.9.5 > > 411 zcat FILM078.vnc.gz | /usr/local/pyvnc2swf/bin/vnc2swf.py > > -n -z -o /tmp/FILM078.flv -V > > > > > > > >> ----- Original Message ----- > >> From: "Oscar Usifer" <osc...@pr...> > >> To: oli...@wa... > >> Cc: "General discussion about vnc2swf" <vnc...@li...> > >> Subject: Re: [Vnc2swf-users] About FLV output. > >> Date: Thu, 2 Apr 2009 13:52:36 -0500 > >> > >> > >> It complains pygame is not installed. Is there a version that > >> uses PIL instead, or is there a setup option to set it to use > >> PIL? > >> > >> Thanks > >> > >> > >> > >> > >>> ----- Original Message ----- > >>> From: "Olivier Hervieu" <oli...@wa...> > >>> To: "Oscar Usifer" <osc...@pr...> > >>> Cc: "General discussion about vnc2swf" > >>> <vnc...@li...> > >>> Subject: Re: [Vnc2swf-users] About FLV output. > >>> Date: Thu, 02 Apr 2009 10:26:44 +0200 > >>> > >>> > >>> The attached tarball has a setup.py that respect standard > >>> python distribution style. > >>> > >>> Run > >>> > >>> python setup.py build > >>> python setup.py install > >>> > >>> You can have some help by running > >>> > >>> 'python setup.py --help' or 'python setup.py --help [command name]' > >>> > >>> Forget the old makefile. I leave it here for euske. > >>> > >>> Regards, > >>> > >>> Olivier. > >>> > >>> Oscar Usifer a écrit : > >>> > >>>> Greets Olivier, > >>>> > >>>> Just a few requests. I would like to test it out, but am not > >>> able > to get it into an installed state. I tried to run > >>> setup.py, but > it seems to output usage along the way instead > >>> of actually > performing an install. I was not able to use your > >>> package, as > make fails as well. Could you please update so > >>> that it is > compatible with the current build system? Also, I > >>> have a target > system that I use for installation, so the > >>> setup/make would need > an option to install into a target > >>> directory instead of into a > system. I can take your work and > >>> figure out how to get it > completely installed, but not > >>> everyone has the time or desire to > go to that level of energy > >>> output. Also, I am beginner level with > Python, which makes it > >>> less accessible. > >>> > >>>> Thanks, > >>>> OSC > >>>> > >>>> > >>>> > >>>> > >>>> > >>>>> ----- Original Message ----- > >>>>> From: "Olivier Hervieu" <oli...@wa...> > >>>>> To: vnc...@li..., "Yusuke Shinyama" >> > >>> <yu...@cs...> > >>> > >>>>> Subject: [Vnc2swf-users] About FLV output. > >>>>> Date: Mon, 30 Mar 2009 16:49:48 +0200 > >>>>> > >>>>> > >>>>> Hi all, > >>>>> > >>>>> Vnc2swf can produce FLV. But produced files present some drawbacks. > >>>>> > >>>>> - files has only one keyframe (also report a few weeks ago), > >>>>> - files has no metadata. This means that support of pyvnc2swf > >>>>> FLV files is not complete for most FLV players (impossible to > >>>>> scroll, total record time is not available (a good example : > >>>>> test your pyvnc2swf FlV in FlowPlayer)). > >>>>> > >>>>> I attach a tarball containing some modifications: > >>>>> > >>>>> - add a '-k' option to specify the keyframe rate > >>>>> - Add meta data on the produced flv. > >>>>> > >>>>> Note that I also repackage pyvnc2swf to be more pythonic. >> > >>> Vnc2swf scripts, edit and play are replaced by scripts >> > >>> vnc2swf-recorder, vnc2swf-editor and vnc2swf player. The >> > >>> distribution is now built and installed with setuptools. > >>> > >>>>> The Cli interface was successfully tested on Ubuntu 8.04 and > >>>>> Debian Lenny. > >>>>> > >>>>> Also note that I did not (and do not want to) install > >>> python-tk. >> I paid attention to add some options in the GUI. > >>> But these >> changes are not yet tested,. > >>> > >>>>> I leave to Euske or others to test and commit these changes. > >>>>> > >>>>> Regards, > >>>>> > >>>>> Olivier Hervieu. > >>>>> << pyvnc2swf-0.10.0.tar.gz >> > >>>>> > >>>>> > >>>>> > >>>> > >>>> > >> -- > >> Be Yourself @ mail.com! > >> Choose From 200+ Email Addresses > >> Get a Free Account at www.mail.com > >> > >> > >> ------------------------------------------------------------------------------ > >> _______________________________________________ > >> Vnc2swf-users mailing list > >> Vnc...@li... > >> https://lists.sourceforge.net/lists/listinfo/vnc2swf-users > >> > > > > > > > > > > > -- Be Yourself @ mail.com! Choose From 200+ Email Addresses Get a Free Account at www.mail.com |
From: Olivier H. <oli...@wa...> - 2009-04-03 08:19:15
|
Greetings! Yes, the resulted diff shows a minimal workaround to add some metadata to the resulting flv (in fact framerate and duration). These one are needed, otherwise, produced flv files are not correctly read with flv players (such as FlowPlayer). But it's still 'experimental'. And it will be nice to insert all metadata like flvtool++ or flvtool2 does. On the other side, flvtool++ or flvtool2 are post treatment tool. And, more your flv file is heavy, more your post treatment is long... In an ideal world, there should be inclusion of all the metadata (such as flvtool + +) at creation time of the flv by vnc2swf .... Still work to do! If you're interested by this, read the following documentation : http://osflash.org/flv http://pyamf.org/ Olivier. Oscar Usifer a écrit : > Folks, > > I updated __init__.py and commented out import play, and that got me further, so I could at least test. The result of this, was being able to use the vnc2swf-recorder script to output .flv reading from a streaming stdin input. However the resulting output files contained blank frames. Seeing that v.0.10.0 swf.py had the updates to write out the meta-data for .flv formats, I attempted to simply update this file with the diff, but with the same bad result as before. Below is an approximate diff. > > "flvtool++" (v.1.1) apparently is a work around for this situation. It will create the flv meta data, but does not write the correct height meta-data value either because pyvnc2swf writes it incorrectly (see swf.py use of 'rect' in FLVWriter), or because flvtool++.cpp does uses an incorrect algorithm to read it. The diff resolves this. > > Thanks > > [osc@builder-freebsd ~/packages/flvtool++/src/patch]$ diff flvtool++.cpp /usr/ports/multimedia/flvtool++/work/flvtool++.cpp > 190,191c190,191 > < h = ((*(vptr++)) & 0x0f) << 8; > < h += ((*(vptr++)) & 0xff); > --- > >> h = ((*(vptr++)) & 0xff) << 4; >> h = ((*(vptr++)) & 0xf0) >> 4; >> > > [osc@rt01 /var/ee/www/swf]$ ~/flvtool++ /tmp/FILM078.flv /tmp/FILM078.2.flv > Video: 878x629 SCREEN > Total: 313234 video bytes (190.329029 kbps), 0 audio bytes (0.000000 kbps), 13.166000 seconds long > Final onMetaData tag contents: { > audiodatarate: 0.000000 > audiosize: 0.000000 > canSeekToEnd: true > datasize: 316322.000000 > duration: 13.166000 > framerate: 12.076561 > hasAudio: false > hasCuePoints: false > hasKeyframes: true > hasMetadata: true > hasVideo: true > height: 629.000000 > keyframes: { > filepositions: { > 544.000000 > } > times: { > 0.000000 > } > } > lasttimestamp: 13.166000 > metadatacreator: flvtool++ (Facebook, Motion project, dweatherford) > metadatadate: Thu Apr 2 22:10:27 2009 > totalframes: 159.000000 > videocodecid: 3.000000 > videodatarate: 190.329029 > videosize: 313234.000000 > width: 878.000000 > } > > > > [osc@builder-freebsd ~/packages/vnc2swf/src/pyvnc2swf-0.9.5/pyvnc2swf]$ diff swf-0.10.0.py swf.py > 854d853 > < > 857,871d855 > < > < # Meta Data information must be at the start of the file.... > < # Reserve here an area of 100 char to store meta data information > < # I know this is a bit ugly.. But i have no better idea... > < i = 0 > < self.pos = self.outfp.tell() > < self.writeui8(18) > < self.writeub24(100) > < self.writeub24(0) > < self.writeui32(0) > < self.outfp.flush() > < while i < 100: > < self.writeui8(0) > < i = i+1 > < self.writeub32(111) > 885,926d868 > < # To be correctly played into a FLV Player, flv files has to handle some meta data > < # With framerate and duration, many flv player successfully read the produced > < # FLV Stream > < import struct > < > < # Flushing all the remaining data > < self.outfp.flush() > < > < # Write metadata information > < self.outfp.seek(self.pos) > < > < # The needed metadata are stored in flv with amf format. > < # For documentation, see : > < # - http://osflash.org/flv > < # - http://pyamf.org/ > < # Following metadata was generated with the help of pyamf > < > < duration = framecount / self.framerate > < meta = '\x02\x00\nonMetaData\x08\x00\x00\x00\x00\x00\x08' > < meta += 'duration\x02' + struct.pack('>H',len(str(duration))) + str(duration) > < meta += '\x00\x0ccanSeekToEnd\x01\x01\x00\t' > < meta += 'framerate\x02' + struct.pack('>H',len(str(self.framerate))) + str(self.framerate) + '\x00' > < # writing metadata duration > < self.writeui8(18) > < self.writeub24(100) > < self.writeub24(0) > < self.writeui32(0) > < # Insert pseudo Data to fill the rest of the reserved space > < rest = 100 -len(meta) -22 > < meta +='\x0fuselessdatabuff\x02' + struct.pack('>H',rest) > < data = '' > < while len(data)<rest: > < # Inserting Blank Data > < data += '\x00' > < meta += data > < meta += '\x00\x00\t' > < self.write(meta) > < print len(meta) > < self.writeub32(111) > < > < self.outfp.seek(0,2) #The end of file > < self.outfp.flush() > > Command I am using test > > For v. 0.10.0 > 400 zcat FILM075.vnc.gz | vnc2swf-recorder -n -z -o /tmp/FILM078.flv -V > > For v. 0.9.5 > 411 zcat FILM078.vnc.gz | /usr/local/pyvnc2swf/bin/vnc2swf.py -n -z -o /tmp/FILM078.flv -V > > > >> ----- Original Message ----- >> From: "Oscar Usifer" <osc...@pr...> >> To: oli...@wa... >> Cc: "General discussion about vnc2swf" <vnc...@li...> >> Subject: Re: [Vnc2swf-users] About FLV output. >> Date: Thu, 2 Apr 2009 13:52:36 -0500 >> >> >> It complains pygame is not installed. Is there a version that uses >> PIL instead, or is there a setup option to set it to use PIL? >> >> Thanks >> >> >> >> >>> ----- Original Message ----- >>> From: "Olivier Hervieu" <oli...@wa...> >>> To: "Oscar Usifer" <osc...@pr...> >>> Cc: "General discussion about vnc2swf" <vnc...@li...> >>> Subject: Re: [Vnc2swf-users] About FLV output. >>> Date: Thu, 02 Apr 2009 10:26:44 +0200 >>> >>> >>> The attached tarball has a setup.py that respect standard python >>> distribution style. >>> >>> Run >>> >>> python setup.py build >>> python setup.py install >>> >>> You can have some help by running >>> >>> 'python setup.py --help' or 'python setup.py --help [command name]' >>> >>> Forget the old makefile. I leave it here for euske. >>> >>> Regards, >>> >>> Olivier. >>> >>> Oscar Usifer a écrit : >>> >>>> Greets Olivier, >>>> >>>> Just a few requests. I would like to test it out, but am not >>>> >>> able > to get it into an installed state. I tried to run >>> setup.py, but > it seems to output usage along the way instead of >>> actually > performing an install. I was not able to use your >>> package, as > make fails as well. Could you please update so that >>> it is > compatible with the current build system? Also, I have a >>> target > system that I use for installation, so the setup/make >>> would need > an option to install into a target directory instead >>> of into a > system. I can take your work and figure out how to >>> get it > completely installed, but not everyone has the time or >>> desire to > go to that level of energy output. Also, I am >>> beginner level with > Python, which makes it less accessible. >>> >>>> Thanks, >>>> OSC >>>> >>>> >>>> >>>> >>>> >>>>> ----- Original Message ----- >>>>> From: "Olivier Hervieu" <oli...@wa...> >>>>> To: vnc...@li..., "Yusuke Shinyama" >> >>>>> >>> <yu...@cs...> >>> >>>>> Subject: [Vnc2swf-users] About FLV output. >>>>> Date: Mon, 30 Mar 2009 16:49:48 +0200 >>>>> >>>>> >>>>> Hi all, >>>>> >>>>> Vnc2swf can produce FLV. But produced files present some drawbacks. >>>>> >>>>> - files has only one keyframe (also report a few weeks ago), >>>>> - files has no metadata. This means that support of pyvnc2swf >>>>> FLV files is not complete for most FLV players (impossible to >>>>> scroll, total record time is not available (a good example : >>>>> test your pyvnc2swf FlV in FlowPlayer)). >>>>> >>>>> I attach a tarball containing some modifications: >>>>> >>>>> - add a '-k' option to specify the keyframe rate >>>>> - Add meta data on the produced flv. >>>>> >>>>> Note that I also repackage pyvnc2swf to be more pythonic. >> >>>>> >>> Vnc2swf scripts, edit and play are replaced by scripts >> >>> vnc2swf-recorder, vnc2swf-editor and vnc2swf player. The >> >>> distribution is now built and installed with setuptools. >>> >>>>> The Cli interface was successfully tested on Ubuntu 8.04 and Debian Lenny. >>>>> >>>>> Also note that I did not (and do not want to) install >>>>> >>> python-tk. >> I paid attention to add some options in the GUI. >>> But these >> changes are not yet tested,. >>> >>>>> I leave to Euske or others to test and commit these changes. >>>>> >>>>> Regards, >>>>> >>>>> Olivier Hervieu. >>>>> << pyvnc2swf-0.10.0.tar.gz >> >>>>> >>>>> >>>>> >>>> >>>> >> -- >> Be Yourself @ mail.com! >> Choose From 200+ Email Addresses >> Get a Free Account at www.mail.com >> >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Vnc2swf-users mailing list >> Vnc...@li... >> https://lists.sourceforge.net/lists/listinfo/vnc2swf-users >> > > > > > |
From: Oscar U. <osc...@pr...> - 2009-04-02 22:24:30
|
Folks, I updated __init__.py and commented out import play, and that got me further, so I could at least test. The result of this, was being able to use the vnc2swf-recorder script to output .flv reading from a streaming stdin input. However the resulting output files contained blank frames. Seeing that v.0.10.0 swf.py had the updates to write out the meta-data for .flv formats, I attempted to simply update this file with the diff, but with the same bad result as before. Below is an approximate diff. "flvtool++" (v.1.1) apparently is a work around for this situation. It will create the flv meta data, but does not write the correct height meta-data value either because pyvnc2swf writes it incorrectly (see swf.py use of 'rect' in FLVWriter), or because flvtool++.cpp does uses an incorrect algorithm to read it. The diff resolves this. Thanks [osc@builder-freebsd ~/packages/flvtool++/src/patch]$ diff flvtool++.cpp /usr/ports/multimedia/flvtool++/work/flvtool++.cpp 190,191c190,191 < h = ((*(vptr++)) & 0x0f) << 8; < h += ((*(vptr++)) & 0xff); --- > h = ((*(vptr++)) & 0xff) << 4; > h = ((*(vptr++)) & 0xf0) >> 4; [osc@rt01 /var/ee/www/swf]$ ~/flvtool++ /tmp/FILM078.flv /tmp/FILM078.2.flv Video: 878x629 SCREEN Total: 313234 video bytes (190.329029 kbps), 0 audio bytes (0.000000 kbps), 13.166000 seconds long Final onMetaData tag contents: { audiodatarate: 0.000000 audiosize: 0.000000 canSeekToEnd: true datasize: 316322.000000 duration: 13.166000 framerate: 12.076561 hasAudio: false hasCuePoints: false hasKeyframes: true hasMetadata: true hasVideo: true height: 629.000000 keyframes: { filepositions: { 544.000000 } times: { 0.000000 } } lasttimestamp: 13.166000 metadatacreator: flvtool++ (Facebook, Motion project, dweatherford) metadatadate: Thu Apr 2 22:10:27 2009 totalframes: 159.000000 videocodecid: 3.000000 videodatarate: 190.329029 videosize: 313234.000000 width: 878.000000 } [osc@builder-freebsd ~/packages/vnc2swf/src/pyvnc2swf-0.9.5/pyvnc2swf]$ diff swf-0.10.0.py swf.py 854d853 < 857,871d855 < < # Meta Data information must be at the start of the file.... < # Reserve here an area of 100 char to store meta data information < # I know this is a bit ugly.. But i have no better idea... < i = 0 < self.pos = self.outfp.tell() < self.writeui8(18) < self.writeub24(100) < self.writeub24(0) < self.writeui32(0) < self.outfp.flush() < while i < 100: < self.writeui8(0) < i = i+1 < self.writeub32(111) 885,926d868 < # To be correctly played into a FLV Player, flv files has to handle some meta data < # With framerate and duration, many flv player successfully read the produced < # FLV Stream < import struct < < # Flushing all the remaining data < self.outfp.flush() < < # Write metadata information < self.outfp.seek(self.pos) < < # The needed metadata are stored in flv with amf format. < # For documentation, see : < # - http://osflash.org/flv < # - http://pyamf.org/ < # Following metadata was generated with the help of pyamf < < duration = framecount / self.framerate < meta = '\x02\x00\nonMetaData\x08\x00\x00\x00\x00\x00\x08' < meta += 'duration\x02' + struct.pack('>H',len(str(duration))) + str(duration) < meta += '\x00\x0ccanSeekToEnd\x01\x01\x00\t' < meta += 'framerate\x02' + struct.pack('>H',len(str(self.framerate))) + str(self.framerate) + '\x00' < # writing metadata duration < self.writeui8(18) < self.writeub24(100) < self.writeub24(0) < self.writeui32(0) < # Insert pseudo Data to fill the rest of the reserved space < rest = 100 -len(meta) -22 < meta +='\x0fuselessdatabuff\x02' + struct.pack('>H',rest) < data = '' < while len(data)<rest: < # Inserting Blank Data < data += '\x00' < meta += data < meta += '\x00\x00\t' < self.write(meta) < print len(meta) < self.writeub32(111) < < self.outfp.seek(0,2) #The end of file < self.outfp.flush() Command I am using test For v. 0.10.0 400 zcat FILM075.vnc.gz | vnc2swf-recorder -n -z -o /tmp/FILM078.flv -V For v. 0.9.5 411 zcat FILM078.vnc.gz | /usr/local/pyvnc2swf/bin/vnc2swf.py -n -z -o /tmp/FILM078.flv -V > ----- Original Message ----- > From: "Oscar Usifer" <osc...@pr...> > To: oli...@wa... > Cc: "General discussion about vnc2swf" <vnc...@li...> > Subject: Re: [Vnc2swf-users] About FLV output. > Date: Thu, 2 Apr 2009 13:52:36 -0500 > > > It complains pygame is not installed. Is there a version that uses > PIL instead, or is there a setup option to set it to use PIL? > > Thanks > > > > > ----- Original Message ----- > > From: "Olivier Hervieu" <oli...@wa...> > > To: "Oscar Usifer" <osc...@pr...> > > Cc: "General discussion about vnc2swf" <vnc...@li...> > > Subject: Re: [Vnc2swf-users] About FLV output. > > Date: Thu, 02 Apr 2009 10:26:44 +0200 > > > > > > The attached tarball has a setup.py that respect standard python > > distribution style. > > > > Run > > > > python setup.py build > > python setup.py install > > > > You can have some help by running > > > > 'python setup.py --help' or 'python setup.py --help [command name]' > > > > Forget the old makefile. I leave it here for euske. > > > > Regards, > > > > Olivier. > > > > Oscar Usifer a écrit : > > > Greets Olivier, > > > > > > Just a few requests. I would like to test it out, but am not > > able > to get it into an installed state. I tried to run > > setup.py, but > it seems to output usage along the way instead of > > actually > performing an install. I was not able to use your > > package, as > make fails as well. Could you please update so that > > it is > compatible with the current build system? Also, I have a > > target > system that I use for installation, so the setup/make > > would need > an option to install into a target directory instead > > of into a > system. I can take your work and figure out how to > > get it > completely installed, but not everyone has the time or > > desire to > go to that level of energy output. Also, I am > > beginner level with > Python, which makes it less accessible. > > > > > > Thanks, > > > OSC > > > > > > > > > > > > > > >> ----- Original Message ----- > > >> From: "Olivier Hervieu" <oli...@wa...> > > >> To: vnc...@li..., "Yusuke Shinyama" >> > > <yu...@cs...> > > >> Subject: [Vnc2swf-users] About FLV output. > > >> Date: Mon, 30 Mar 2009 16:49:48 +0200 > > >> > > >> > > >> Hi all, > > >> > > >> Vnc2swf can produce FLV. But produced files present some drawbacks. > > >> > > >> - files has only one keyframe (also report a few weeks ago), > > >> - files has no metadata. This means that support of pyvnc2swf > > >> FLV files is not complete for most FLV players (impossible to > > >> scroll, total record time is not available (a good example : > > >> test your pyvnc2swf FlV in FlowPlayer)). > > >> > > >> I attach a tarball containing some modifications: > > >> > > >> - add a '-k' option to specify the keyframe rate > > >> - Add meta data on the produced flv. > > >> > > >> Note that I also repackage pyvnc2swf to be more pythonic. >> > > Vnc2swf scripts, edit and play are replaced by scripts >> > > vnc2swf-recorder, vnc2swf-editor and vnc2swf player. The >> > > distribution is now built and installed with setuptools. > > >> > > >> The Cli interface was successfully tested on Ubuntu 8.04 and Debian Lenny. > > >> > > >> Also note that I did not (and do not want to) install > > python-tk. >> I paid attention to add some options in the GUI. > > But these >> changes are not yet tested,. > > >> > > >> I leave to Euske or others to test and commit these changes. > > >> > > >> Regards, > > >> > > >> Olivier Hervieu. > > >> << pyvnc2swf-0.10.0.tar.gz >> > > >> > > >> > > > > > > > > > > > > > > > -- > Be Yourself @ mail.com! > Choose From 200+ Email Addresses > Get a Free Account at www.mail.com > > > ------------------------------------------------------------------------------ > _______________________________________________ > Vnc2swf-users mailing list > Vnc...@li... > https://lists.sourceforge.net/lists/listinfo/vnc2swf-users > -- Be Yourself @ mail.com! Choose From 200+ Email Addresses Get a Free Account at www.mail.com |
From: Oscar U. <osc...@pr...> - 2009-04-02 18:52:46
|
It complains pygame is not installed. Is there a version that uses PIL instead, or is there a setup option to set it to use PIL? Thanks > ----- Original Message ----- > From: "Olivier Hervieu" <oli...@wa...> > To: "Oscar Usifer" <osc...@pr...> > Cc: "General discussion about vnc2swf" <vnc...@li...> > Subject: Re: [Vnc2swf-users] About FLV output. > Date: Thu, 02 Apr 2009 10:26:44 +0200 > > > The attached tarball has a setup.py that respect standard python > distribution style. > > Run > > python setup.py build > python setup.py install > > You can have some help by running > > 'python setup.py --help' or 'python setup.py --help [command name]' > > Forget the old makefile. I leave it here for euske. > > Regards, > > Olivier. > > Oscar Usifer a écrit : > > Greets Olivier, > > > > Just a few requests. I would like to test it out, but am not able > > to get it into an installed state. I tried to run setup.py, but > > it seems to output usage along the way instead of actually > > performing an install. I was not able to use your package, as > > make fails as well. Could you please update so that it is > > compatible with the current build system? Also, I have a target > > system that I use for installation, so the setup/make would need > > an option to install into a target directory instead of into a > > system. I can take your work and figure out how to get it > > completely installed, but not everyone has the time or desire to > > go to that level of energy output. Also, I am beginner level with > > Python, which makes it less accessible. > > > > Thanks, > > OSC > > > > > > > > > >> ----- Original Message ----- > >> From: "Olivier Hervieu" <oli...@wa...> > >> To: vnc...@li..., "Yusuke Shinyama" > >> <yu...@cs...> > >> Subject: [Vnc2swf-users] About FLV output. > >> Date: Mon, 30 Mar 2009 16:49:48 +0200 > >> > >> > >> Hi all, > >> > >> Vnc2swf can produce FLV. But produced files present some drawbacks. > >> > >> - files has only one keyframe (also report a few weeks ago), > >> - files has no metadata. This means that support of pyvnc2swf > >> FLV files is not complete for most FLV players (impossible to > >> scroll, total record time is not available (a good example : > >> test your pyvnc2swf FlV in FlowPlayer)). > >> > >> I attach a tarball containing some modifications: > >> > >> - add a '-k' option to specify the keyframe rate > >> - Add meta data on the produced flv. > >> > >> Note that I also repackage pyvnc2swf to be more pythonic. > >> Vnc2swf scripts, edit and play are replaced by scripts > >> vnc2swf-recorder, vnc2swf-editor and vnc2swf player. The > >> distribution is now built and installed with setuptools. > >> > >> The Cli interface was successfully tested on Ubuntu 8.04 and Debian Lenny. > >> > >> Also note that I did not (and do not want to) install python-tk. > >> I paid attention to add some options in the GUI. But these > >> changes are not yet tested,. > >> > >> I leave to Euske or others to test and commit these changes. > >> > >> Regards, > >> > >> Olivier Hervieu. > >> << pyvnc2swf-0.10.0.tar.gz >> > >> > >> > > > > > > > -- Be Yourself @ mail.com! Choose From 200+ Email Addresses Get a Free Account at www.mail.com |
From: Olivier H. <oli...@wa...> - 2009-04-02 08:26:36
|
The attached tarball has a setup.py that respect standard python distribution style. Run python setup.py build python setup.py install You can have some help by running 'python setup.py --help' or 'python setup.py --help [command name]' Forget the old makefile. I leave it here for euske. Regards, Olivier. Oscar Usifer a écrit : > Greets Olivier, > > Just a few requests. I would like to test it out, but am not able to get it into an installed state. I tried to run setup.py, but it seems to output usage along the way instead of actually performing an install. I was not able to use your package, as make fails as well. Could you please update so that it is compatible with the current build system? Also, I have a target system that I use for installation, so the setup/make would need an option to install into a target directory instead of into a system. I can take your work and figure out how to get it completely installed, but not everyone has the time or desire to go to that level of energy output. Also, I am beginner level with Python, which makes it less accessible. > > Thanks, > OSC > > > > >> ----- Original Message ----- >> From: "Olivier Hervieu" <oli...@wa...> >> To: vnc...@li..., "Yusuke Shinyama" <yu...@cs...> >> Subject: [Vnc2swf-users] About FLV output. >> Date: Mon, 30 Mar 2009 16:49:48 +0200 >> >> >> Hi all, >> >> Vnc2swf can produce FLV. But produced files present some drawbacks. >> >> - files has only one keyframe (also report a few weeks ago), >> - files has no metadata. This means that support of pyvnc2swf FLV >> files is not complete for most FLV players (impossible to scroll, >> total record time is not available (a good example : test your >> pyvnc2swf FlV in FlowPlayer)). >> >> I attach a tarball containing some modifications: >> >> - add a '-k' option to specify the keyframe rate >> - Add meta data on the produced flv. >> >> Note that I also repackage pyvnc2swf to be more pythonic. Vnc2swf >> scripts, edit and play are replaced by scripts vnc2swf-recorder, >> vnc2swf-editor and vnc2swf player. The distribution is now built >> and installed with setuptools. >> >> The Cli interface was successfully tested on Ubuntu 8.04 and Debian Lenny. >> >> Also note that I did not (and do not want to) install python-tk. I >> paid attention to add some options in the GUI. But these changes >> are not yet tested,. >> >> I leave to Euske or others to test and commit these changes. >> >> Regards, >> >> Olivier Hervieu. >> << pyvnc2swf-0.10.0.tar.gz >> >> >> > > > |
From: Oscar U. <osc...@pr...> - 2009-04-01 22:05:49
|
Greets Olivier, Just a few requests. I would like to test it out, but am not able to get it into an installed state. I tried to run setup.py, but it seems to output usage along the way instead of actually performing an install. I was not able to use your package, as make fails as well. Could you please update so that it is compatible with the current build system? Also, I have a target system that I use for installation, so the setup/make would need an option to install into a target directory instead of into a system. I can take your work and figure out how to get it completely installed, but not everyone has the time or desire to go to that level of energy output. Also, I am beginner level with Python, which makes it less accessible. Thanks, OSC > ----- Original Message ----- > From: "Olivier Hervieu" <oli...@wa...> > To: vnc...@li..., "Yusuke Shinyama" <yu...@cs...> > Subject: [Vnc2swf-users] About FLV output. > Date: Mon, 30 Mar 2009 16:49:48 +0200 > > > Hi all, > > Vnc2swf can produce FLV. But produced files present some drawbacks. > > - files has only one keyframe (also report a few weeks ago), > - files has no metadata. This means that support of pyvnc2swf FLV > files is not complete for most FLV players (impossible to scroll, > total record time is not available (a good example : test your > pyvnc2swf FlV in FlowPlayer)). > > I attach a tarball containing some modifications: > > - add a '-k' option to specify the keyframe rate > - Add meta data on the produced flv. > > Note that I also repackage pyvnc2swf to be more pythonic. Vnc2swf > scripts, edit and play are replaced by scripts vnc2swf-recorder, > vnc2swf-editor and vnc2swf player. The distribution is now built > and installed with setuptools. > > The Cli interface was successfully tested on Ubuntu 8.04 and Debian Lenny. > > Also note that I did not (and do not want to) install python-tk. I > paid attention to add some options in the GUI. But these changes > are not yet tested,. > > I leave to Euske or others to test and commit these changes. > > Regards, > > Olivier Hervieu. > << pyvnc2swf-0.10.0.tar.gz >> > -- Be Yourself @ mail.com! Choose From 200+ Email Addresses Get a Free Account at www.mail.com |
From: Juazisco <haf...@gm...> - 2009-03-30 14:54:57
|
hi Oliver, I need streaming the output of pyvnc2swf, but i have problem with output whe i use '|', can you help me please. thanks, PD: Sorry for my english 2009/3/30 Olivier Hervieu <oli...@wa...> > Hi all, > > Vnc2swf can produce FLV. But produced files present some drawbacks. > > - files has only one keyframe (also report a few weeks ago), > - files has no metadata. This means that support of pyvnc2swf FLV files is > not complete for most FLV players (impossible to scroll, total record time > is not available (a good example : test your pyvnc2swf FlV in FlowPlayer)). > > I attach a tarball containing some modifications: > > - add a '-k' option to specify the keyframe rate > - Add meta data on the produced flv. > > Note that I also repackage pyvnc2swf to be more pythonic. Vnc2swf scripts, > edit and play are replaced by scripts vnc2swf-recorder, vnc2swf-editor and > vnc2swf player. The distribution is now built and installed with setuptools. > > The Cli interface was successfully tested on Ubuntu 8.04 and Debian Lenny. > > Also note that I did not (and do not want to) install python-tk. I paid > attention to add some options in the GUI. But these changes are not yet > tested,. > > I leave to Euske or others to test and commit these changes. > > Regards, > > Olivier Hervieu. > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Vnc2swf-users mailing list > Vnc...@li... > https://lists.sourceforge.net/lists/listinfo/vnc2swf-users > > -- ------------------------------- Jose Quiñones Enciso Blog: http://joseq.inkax.org ------------------------------- Apesol: http://www.apesol.org ------------------------------- |
From: Olivier H. <oli...@wa...> - 2009-03-30 14:50:05
|
Hi all, Vnc2swf can produce FLV. But produced files present some drawbacks. - files has only one keyframe (also report a few weeks ago), - files has no metadata. This means that support of pyvnc2swf FLV files is not complete for most FLV players (impossible to scroll, total record time is not available (a good example : test your pyvnc2swf FlV in FlowPlayer)). I attach a tarball containing some modifications: - add a '-k' option to specify the keyframe rate - Add meta data on the produced flv. Note that I also repackage pyvnc2swf to be more pythonic. Vnc2swf scripts, edit and play are replaced by scripts vnc2swf-recorder, vnc2swf-editor and vnc2swf player. The distribution is now built and installed with setuptools. The Cli interface was successfully tested on Ubuntu 8.04 and Debian Lenny. Also note that I did not (and do not want to) install python-tk. I paid attention to add some options in the GUI. But these changes are not yet tested,. I leave to Euske or others to test and commit these changes. Regards, Olivier Hervieu. |