VCS update 2007-05-12: 1.0.7a released

The new version is out. I've noticed some things that didn't work as expected (or as I assumed before, like command-line overrides –although as usual I guess few or no people uses them anyway :p– I'll have to look at them but have not much time anymore so I'm releasing as is.

What's new in 1.0.7a

Decimal point precission
Finally you can set an exact frame to capture, define the exact boundaries of the capture or set an interval like 30 seconds and 250 milliseconds.

The new timecode format accepts a point now, e.g. 2m.2 (2 minutes and 0.2 seconds) or 15.333 (15 seconds and 333 milliseconds).

You can consider this feature in alpha stage, it has many rough edges still.

Worth noting also is that funky modes are random, so the result might look great or be plain dull.

In short the funky modes are like the normal vcs mode but less useful 😛. They are meant to provide some nicer output modes. Well in fact they're a toy of mine, but don't tell anyone.

Probably the most interesting bit is the polaroid mode, based on a feature built in newer versions of ImageMagick (although I'm not actually using it), here's a sample:

As you can see, it basically adds a frame around each capture, rotates and overlaps them semi-randomly.

Although not useful for common video previews it might be nice for family videos and such 🙂

The list of funky modes in the current version is:

Description

Sample

rotate
Rotates each capture randomly.

overlap
Overlaps captures randomly.

photoframe
Adds a frame to each capture.

polaroid
See above. A combination of rotate,photoframe and overlap.

filmThis one is specially rough, currently. Adds a filmstrip effect
to captures.

random

This is basically a way to discover nice fonts/colours combinations. Randomizes
font and colours selection. The output is rarely usable.

(no sample)

Support for non-latin file names

Honestly, I don't know how well this works or doesn't because I can't speak any such language. What this feature does is switching the font to an alternate one (by default Kochi Mincho) just to print the filename. In theory this should work for Hiragana and Katakana (plus latin scripts) and (partially?) for the Hangul and Cyrillic scripts (although the default font in my system already prints Cyrillic).
Samples. These are vcs runs against a file named "Roman – 日本語 – 漢語 – Русский – 한글.avi"
(if your browser can't display the name correctly, see this image):

The first row uses the default font (helvetica), only latin and cyrillic characters are drawn.
The second row uses the alternate font (by default Kochi Mincho), only the korean text is ignored.

If you can help with this I'd appreciate it 🙂

Workaround for ffmpeg arguments order.

A known issue is that depending on the order of arguments passed to ffmpeg, with some input files the capture will stall or fail. If vcs seems to get stuck on the first capture for too long, try using -Wo. On some files in works, on others it doesn't. Some files simply make ffmpeg suffer a lot and eventually it does the capture but taking a lot more time.

Matroska files (.mkv) seem to be specially tough, most of my samples won't work.
Can't help more here right now.

End offset
My personal impression is that most often it is desirable not to capture from the very end of the video. I'm not talking about spoilers, what I mean is that when vcs is run over a full film, often the last capture is simply a black (or blank) frame.
Now by default a minute from the end is ignored, hence in those situations the last capture most often will be of the credits.

This isn't practical for a lot of videos so you can change or disable the offset by using -E or --end_offset. By default it will be disabled when the video runs for less than the default offset. Use -E 0 to disable the offset, or override DEFAULT_END_OFFSET to change/disable the default.

As I haven't written the overrides documentation yet, here's what you can do to disable the "end offset" feature forever:$ echo 'DEFAULT_END_OFFSET=0' >> ~/.vcs.conf