vcs

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.

Asked by Bob on the blog

Would it be possible to somehow specify to only screenshot half of the video image (for 180 side-by-side VR videos)?

Or would this require new features to be added to the VCS?

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.

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.

No need for description

No need for description

Originally requested by Daniel