doesn't work
doesn't work
I was afraid that would be the case ... was just a shot in the dark
Anyway, I'll implement this functionality in version 1.8. Right now this can't be done, or at least I'm not aware of a way to do it. If I discover one, I'll let you know.
Of course i can integrate video coding to Blink
No! Please don't do that! The idea is to invoke an external application to perform the video encoding task (divide and conquer strategy). It is basically a two-step procedure:
- Generate a set of video frames at a user-selected resolution. Wikipedia has a
nice chart in SVG format that compares all standard resolutions. These video frames could be generated as PNG images on a working directory; that's super easy to do with PCL. I'd include the possibility to select a region of interest. Note also that in order to create smooth transitions at video rates of 25 fps or more, this may involve generation of intermediate video frames by interpolation from images loaded in Blink.
- From the Blink module, invoke a command line application to perform the video encoding work.
- Optionally, delete the working frames once a video has been successfully encoded. Or leave them in case the user wants to use them later (see Vicent's comments).
I think
ffmpeg is our best option. It is cross-platform, works extremely well, and is released under LGPL license, which allows us to include it in PI distributions.
Now the only problem is that PCL does not currently support execution of external processes (the PJSR does support it for JavaScript scripts). However if there is interest in this development line, I can push inclusion of this functionality in PCL and the core application.
But why inside Blink?
Because Blink is already a perfect movie maker/previewer. Note the icon that I drew for your module