vcs

The available configuration options need a serious review and renaming. Old names will be accepted with warnings for either two releases or six months.

Also, should provide a sample configuration file so that the syntax and options are clearer.

Great feature, implemented in mtn

http://moviethumbnail.sourceforge.net/

See also FS#126

Originally suggested by Dogn Redhammer

Fails on some files (gets stuck forever while capturing the first frame).

Happens often with Matroska. 1.0.7a introduced a workaround (-Wo) with ffmpeg’s argument order that worked with other file types.

Being based on System V, it’s quite different to most other Unix-like OSes, might be a good target for x-platform enhancements

Originally reported by Tomasz Strózik

Example given:

$ find $DIR \(-name "*.avi" -o -name "*.wmv" -o -name "*.mpg" -o -name "*.mp4" \) -exec vcs -dt -ds -n 12 -c2 -H 200 --jpeg --quiet {} \;

Works on avi, mpg and mp4 but fails on wmv with
Failed to capture frame (at second xxx.000)

Processing the same file directly works:

$ vcs -dt -ds -n 12 -c2 -H 200 --jpeg --quiet File.wmv

This is a meta-item depending on bugs/features required to complete before releasing vcs 2.0.

v2.0 will be a rewrite in Python.

Previous: FS#153

This is a meta-item depending on bugs/features required to complete before releasing vcs 1.14

Previous:  FS#152   FS#218   FS#224   FS#250   FS#366 

Request by Chris Hills

http://outlyer.net/2014-05-18:vcs-1_13_2-released/comment-page-1/#comment-17238:

Thanks Toni. I was hoping I could simply run `$ vcs-1.13.2.bash -? **/*.mp4` to create contact sheets for all videos in all subfolders, but it sounds like I’ll have to use a wrapper script. Would you consider adding this in a future release for a donation?

My reply:

I guess you’re using zsh-ish globbing there.
That’s not something I use so I didn’t even think of the case where recursing could be so simple.

It was a bit of an overlook on my part not to have the option to output to the same directory as the video, probably because recursion always required a wrapper in my head.

Introduce new names in 1.12 ( FS#120 )

Remove old names in 1.13 or 1.14 (this)

No need for description

/dev/shm isn’t really intended as an alternate temporary location, and VCS’ temporary files can easily grow too large for it too.

As a possible alternative offer a first-run choice of temp-dir (maybe suggesting /dev/shm).

References:
http://wiki.debian.org/ReleaseGoals/RunDirectory#Why_put_.2BAC8-dev.2BAC8-shm_and_.2BAC8-tmp_under_.2BAC8-run.3F http://stackoverflow.com/questions/9745281/tmp-vs-dev-shm-for-temp-file-storage-on-linux

Originally reported by Phil Grundig

Version of mplayer: mplayer (1.0pre8cvs)

When the resulting contact sheet is too thin, the meta-information header is cramped and fields overlap.

Reported by KW in comments: https://outlyer.net/2019-11-26:vcs-1-13-4-released/#comment-51875

With the new script I'm getting issues the following error:
No compatible version of getopt in path, can't continue.
Enhanced getopt (i.e. GNU getopt) is required

Added by Darko in comments: https://outlyer.net/2019-11-26:vcs-1-13-4-released/#comment-52719

The homebrew's version of vcs has this at line 186:
declare GETOPT=/opt/homebrew/opt/gnu-getopt/bin/getopt
While Toni's just uses whatever is on path:
declare GETOPT=getopt
… which on macOS is non-gnu version of getopt.

Added by X in comments: https://outlyer.net/2019-11-26:vcs-1-13-4-released/#comment-53401

The issue is on line 186. Brew version has this:
declare GETOPT=/usr/local/opt/gnu-getopt/bin/getopt
The trunk version has:
declare GETOPT=getopt
When I backport the most important change you did in the trunk version ('`fx:image.mean` > `fx:mean`') then indeed the error messages on '.mean*100' are gone.

No need for description

No need for description