vcs

Safe length measuring, when probing the video length, prints only the number of seconds and milliseconds, it would be better to display a more readable format.

mplayer: FPS1

i.e.:
ID_VIDEO_CODEC=fffraps
ID_VIDEO_FORMAT=FPS1

ffmpeg: fraps

i.e.:
Stream #0.0: Video: fraps, yuvj420p, 1680x1050, 30 fps, 30 tbr, 30 tbn, 30 tbc

Version 1.12.3 breaks on FreeBSD due to the usage of GNU-specific extensions of expr, sed and an incompatible Bash RE.

When a timestamp is present in more than one set (highlights/std/extended) there’s no need to re-capture it.

See also  FS#123 

No need for description

Internal: Stale code from prior versions, numsecs inside process() uses mplayer’s value instead of the best value to determine video length (and keep or discard timestamps).

As a side-effect, newer code being more strict about array vs string handling can fail easily.

Parsing of the “-U” option (optional argument) is incorrect, it always receives an argument (empty if none provided) which must be shifted manually. Currently it’s only shifted if provided explicitly.

“–fullname” is not affected since it doesn’t take any arguments.

Configuration options that will trigger a change of all fonts, background and foreground settings respectively

font_filename is ignored in 1.12

An alternative in the form of (boolean) nonlatin_filenames or similar should be added.

WebM: http://www.webmproject.org/

Uses VP8 video and Vorbis audio.

Current Status:

Identification

MPlayer: Video detected as VP80
FFmpeg:
* 0.5.1+svn20100311: Not supported (fails in the safe-length-detection stage)
* 0.6~svn20100603: Video detected as libvpx

Capture

Both appear to work fine.

Originally submitted by Jason Tackaberry

VCS’ temporary dir (and its contents) is not removed on cleanup. Space in /dev/shm is wasted as a result.

Patch attached.

Original report by ya at:

Video Contact Sheet *NIX v1.12, (c) 2007-2010 Toni Corvera
Processing <FILE>...
awk: BEGIN { if (4993,00000000000000000000 == 0) exit 0 ; else exit 1 }
awk:                 ^ syntax error
awk: BEGIN { if (4993,00000000000000000000 == 0) exit 0 ; else exit 1 }
awk:                                           ^ syntax error
awk: BEGIN { if (4993,00000000000000000000 == 0) exit 0 ; else exit 1 }
awk:                                                      ^ syntax error
awk: BEGIN { printf "%.20f", ((4993,00000000000000000000 - 4993.92))+0 }
awk:                                                               ^ syntax error
awk: BEGIN { printf "%.20f", ((4993,00000000000000000000 - 4993.92))+0 }
awk:                                                                ^ syntax error
awk: BEGIN { if (() < (0)) print (() * -1) ; else print () }
awk:              ^ syntax error
awk: BEGIN { if (() < (0)) print (() * -1) ; else print () }
awk:                ^ syntax error
awk: BEGIN { if (() < (0)) print (() * -1) ; else print () }
awk:                       ^ syntax error
awk: BEGIN { if (() < (0)) print (() * -1) ; else print () }
awk:                                 ^ syntax error
awk: BEGIN { if (() < (0)) print (() * -1) ; else print () }
awk:                                       ^ syntax error
awk: BEGIN { if (() < (0)) print (() * -1) ; else print () }
awk:                                                       ^ syntax error
...

Originally reported by Dougn Redhammer

-I does use it

.

.

Workaround introduced in 1.0.7a, needs refinement

Originally requested by Daniel

Originally requested by Daniel

No need for description

Originally requested by Phil Grundig

“Failed to capture frame (at second xxx.yyy)”

Known bug, reported by various users.

Replace with pure bash or perl/awk

No need for description

Even though they’re ignored, it might fail on some files. May be due to the 5 frames hack.