vcs

Symbolic font names don’t work since IM won’t know about TTF fonts.

Probably affects other systems too.

Originally requested by Peter Berends

1.0.8a did accept some ISOs with mplayer but not others

See vcs:devel:posix

Experimental support was introduced in 1.0.100a

No need for description

Introduce new names in 1.12 (this)

Remove old names in 1.13 or 1.14 (FS#151)

End offset will be set to a small percentage of the length (5.5%? –5m for 90m–), applicable always by default, instead of a fixed value

Command-line arguments for DVD handling should be consistent with handling of video files, e.g.:

$ vcs --dvd --dvd-title 1 /dev/dvd

with dvd-title being optional, instead of

$ vcs --dvd /dev/dvd 1

Reported by remlap

File sizes are displayed as 3.00GiB instead of 3.54GiB

Implementation notes:

• Reserved namespace: :<WHATEVER>
• Built-in profiles won’t use reserved names
• System profiles will always take precedence over built-in profiles
• ~ profiles take precedence over site (/usr and /usr/local) profiles
• /usr/local takes precedence over /usr. Both are searched
• No such thing as a default profile (this would be redundant to configuration files)
• Profiles can’t depend/include/load other profiles
• Profile names are reflected in file names

Specific files will be loadable with --config

Markup

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

No need for description

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

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

Known bug, reported by various users.

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

Seen in HEVC contained in MPEG-TS

.

Originally reported by Dougn Redhammer

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.

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.

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.

Submitted by someone desiring no credit.

Here’s a patch against 1.13.2 for mistaken approximate size calculation.

Self-notes about the patch:

• More accurate rounding → Discarded. I went for rounding by excess
• Leading 0 in fractionary units was not present in the original → BUG
  Sample: Samsung HD sample, 1080pto720p version

Workaround introduced in 1.0.7a, needs refinement

Originally requested by Phil Grundig

Replace with pure bash or perl/awk

No need for description