Re: [Vnc2swf-users] Project Future
Status: Alpha
Brought to you by:
euske
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 |