Hi Todd (and all, really),
On Feb 14, 7:25 am, Todd Tyree <
t...@snappl.co.uk> wrote:
> I notice that the main git repository has had no activity since the initial
> import in September and rubyforge still installs gem version 0.9.3. Ishttp://
github.com/Artforge/rvideo/tree/masternow the 'official' master?
> Also, I need the capture_frame functionality (last commented here in
> December) fairly urgently. I'm happy to patch it myself, but am not sure
> which repo to pull from in the first instance.
I was wondering about the state of RVideo, too. I spoke to Jon Dahl,
and he says that the latest work he and the Zencoder people have done
is not fully abstracted away from the application they are working on.
He asked if I've any interest in putting together a "master" repo. I
definitely do, so I've created a fork of RVideo on GitHub with the
intention of getting a contemporary, public RVideo source going again.
http://github.com/greatseth/rvideo
I took the 0.9.5, test-less code in the "zencoder" repo, did a little
hack and slash to get the 0.9.4 Rubyforge SVN specs passing against
that and am going to move on from there. I'm not convinced that all
the changes I made are appropriate, but I thought "it's a start" and
we can figure it out from here.
That repo has a few important fixes:
- Metadata parsing is agnostic about the exact contents of the "need
an output file" line in ffmpeg. Later ffmpeg builds would not work
with most versions of RVideo out there because of a bad regexp.
- Input/output filenames are quoted for the command strings to avoid
problems with spaces, ampersands and other special characters
I've marked some old posts on the mailing list with patches or feature
suggestions for later attention, as well. I would, of course, love any
help with all of this.
Some of the guys from Zencoder are going to be getting some of their
work on RVideo into this mix in the next month or so as well.