All Projects

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

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.

Originally requested by Dougn Redhammer

E.g. with ImageMagick’s -stroke and -strokewidth

Originally requested by Daniel

Originally reported by Phil Grundig

Version of ffmpeg: ffmpeg (CVS-060515)

Originally reported by Phil Grundig

Version of mplayer: mplayer (1.0pre8cvs)

Originally requested by Phil Grundig

See vcs:devel:transcode

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

-o is a GNU extension, supported in Linux and FreeBSD

Unsupported in SunOS, OpenBSD?

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

No need for description

Originally reported by Dougn Redhammer

Timestamps could use some tweaking: e.g. centering on their background and rounded corners

Original report by Dougn Redhammer

vcs hangs with some RM files.

Tracing shows it gets stuck in mplayer_identify.

MPlayer can play the files fine from the terminal. Although it exits with «MPlayer interrupted by signal 11 in module: uninit_vcodec».

I can reproduce the abrupt termination, it happens when using Real’s native decoder (w64codecs, /usr/lib/codecs/drvc.so). Using FFMpeg’s decoder (MPlayer’s -vc ffrv30) MPlayer exits normally.

I can’t reproduce the hang either way.

Introduce new names in 1.12 ( FS#120 )

Remove old names in 1.13 or 1.14 (this)

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 

No need for description

No need for description

No need for description

No need for description

See  FS#171 

As reported by Dirk Reiners (paraphrased)

Files incorrectly reporting too short length (unlike too long), pass the safe_length_measure check ⇒ This prevents correcting length.

See http://libav.org/, Jan 27 2012.
Also http://libav.org/index.html#fftools_rename for changes to the syntax.

Must change to avprobe/ffprobe and/or avconv.

/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

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