vcs

Submitted by Davide Cavestro

The array EVASION_ALTERNATIVES isn’t looped over correctly. Correction:

-		for delta in $EVASION_ALTERNATIVES ; do
+		for delta in ${EVASION_ALTERNATIVES[*]} ; do

Reported by remlap

File sizes are displayed as 3.00GiB instead of 3.54GiB

Seen in HEVC contained in MPEG-TS

Reported by DanC

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

A great utilty... I’ve been using this for a couple of years now (it runs every night as a cron job).

I’ve been looking at cleaning up the output that cron captures from each of its commands and stores as a system email.

I’ve enabled the -Wc option to prevent coloured output. Mostly this works except near the start of the script when it says:
Settings from /home/danc/.vcs/vcs.conf:
bg_heading
This is still shown in green. Bug?

Currently the colour only stops after the option is found.

Originally reported by Markus and Wade

The codec information box gets cropped with current versions of ImageMagick.

Reported by Miya

When using mplayer as capturer and defining a number of captures, the produced number exceeds it by one (i.e. 21 instead of 20).

Pointed out by Miya

eval: line 1874: syntax error in conditional expression
eval: line 1874: syntax error near `got'
eval: line 1874: `[[ -n 'File's got problems.mp4.png' ]]'
Internal error at safe_rename():1510: [[ -n 'File's got problems.mp4.png' ]]

Submitted by Eris Belew

Unquotted grep pattern ^ID is problematic.

Patch submitted.

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

As reported by Dirk Reiners (paraphrased)

When steps get too small they might round to 0 ⇒ infinite loop in compute_timecodes.

At least on some systems, the console/terminal needs a manual reset (or tset) to be usable after running vcs.

When repeated captures are avoided, captures end up being filtered more than once

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.

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

With the introduction of ~/.vcs/ (or ~/.vcs-nix/) it makes sense moving local configurations there. The older ~/.vcs.conf will still be accepted.

Load order:

1. /etc/vcs.conf
2. ~/.vcs.conf
3. ~/.vcs/vcs.conf
4. ./vcs.conf

No need for description

-I does use it