OutlyerNet

New version released, it fixes highlights, which were broken in the last version and a couple of long-standing cosmetic bugs.

Also now requires minimum length before using the "end offset" i.e.: will only ignore a bit off the end of the video
if it's long enough, by default 19'30" (the default value was chosen based on the fact that most series are at least 20' long,
and since the automatic end offset is intended to skip credits, it's most useful with series and films). Your input is welcome
as always.

To change the minimum length set the desired value to variable MIN_LENGTH_FOR_END_OFFSET in your configuration file, e.g.:
echo MIN_LENGTH_FOR_END_OFFSET=\'1h30m\' >> ~/.vcs.conf # for 1h 30'

I just noticed a bug while editing this page :/ and it's been there for quite awhile… great… whatever, most probably few people, if anyone
suffered it, since it required a pretty specific timestamp format being used in the command-line.

Finally I've also re-added the black border after the highlights, which was removed a long time ago due to it breaking vcs back then.

See the changelog as usual for full details.

New version released with a couple fixes and cosmetic touches.

Fixes include a workaround for cases in which mplayer outputted all-black (or all-equal) captures. Also slightly better
support for older/tighter systems (e.g. Damn Small Linux).

Most notably in the cosmetic side is better thumbnail alignment in extended mode (-e), slightly less padded captures and drop of milliseconds
when using mplayer (since they aren't meaningful at all).

See the changelog as usual for full details and credits.

I'm also providing a debian package now.

I was holding off a bit this release since there's still some known stuff to fix or refine but I'll rather publish now what I've
since, well, who knows when will be the next release

Important note: this version's support for highlights (-l) is broken,
This version is deprecated for this reason, use the last version instead.
I'll update 1.0.10.

New version released wth a bugfix and a couple new features: allow disabling timestamps and/or shadows.
See the changelog below.

I've also published a bit of information on the future of VCS and comments would be very welcome (in short, most probably, I'll be rewriting it in a different language than bash).

Finally, I'm moving the documentation into a wiki and filling in a bit more, will be live soonish I hope.

I've added a tips section to the project's page where I'll write any useful tip I might come up with. As usual contributions are welcome.

Yet a couple more (stupid) bugs fixed . See the changelog for details.

Just a couple stupid bugs fixed. See the changelog.

Sorry for the long break, I had some things to delve with in off-line life, plus
a web server change. I hope to restart development soon and look into the list of reported and known bugs.

Also, I should be expanding online documentation. Hopefully.

In the meantime I'm updating the list of known bugs with the ones I hadn't yet added.

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).

  As a side effect, the timestamps now include centiseconds.

• Soft Shadows
  A subtle yet nice improvement, the captures have now "real" shadows:
  
  Upper half has hard shadows (version 1.0.6b and below), lower half has soft shadows (1.0.7a).
• Funky modes.

  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.
  film This 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
  
  If later you want to use the end offset use the -E option normally.

1.0.7b is theoretically ready for release. I'll throw some more files at it and
see how it does. Right now it has almost all features I remember wanting .