VCS 1.13.3 released

The latest version of VCS is available to download.
It's been a good while since the last release, but there aren't a lot of changes this time around, apart from the usual bugfixes there's better handling of errors and unsupported files.

The most important bug fixed is obviously the one I already previewed some days ago. The header was being cropped with current-day ImageMagick, and that problem should be gone.

See the full changelog for more details.


vcs 1.13.3
vcs-1.13.3.gz (script only)
or
vcs-1.13.3.tar.gz (script, sample configuration, manpage and profiles)
deb, rpm, PKGBUILD & xz
as usual at p.outlyer.net/vcs

14 thoughts on “VCS 1.13.3 released

  1. Chris Hills says:

    Thanks for fixing the bug where it would not save the output file if the input filename contained an apostrophe. I just have one niggle:-

    tput: unknown terminal "pc3"

    This does not seem to cause any problems.

  2. Toni Corvera says:

    Hi Chris, this is likely a side effect of the tput error you mentioned. While I look into it you may run vcs like:
    TERM=xterm vcs ...
    which should work.

    May you tell me what OS and OS version you're running vcs on?

  3. Manfred says:

    Hi Tony,

    I've been using VCS for some time now, and it has worked fine for me since.
    When upgrading my system to openSuSE Leap 42.3, VCS does not seem to honor -c anymore, generating one very wide image with captures next to each other…
    After some debugging I learned that bash now exposes $COLUMNS as an internal variable, interfering with the VCS $COLUMNS.
    replacing all 'COLUMNS' with 'USR_COLUMNS' in VCS solved the issue…

    best regards,
    Manfred

  4. Sam says:

    Hi Tony

    Very nice Script, I wasn't wondering if it's possible when running vcs to say something like vcs folder/path/*/*.avi and have it scan a folder/subfolders for .avi files and make thumbnails of them and output the thumbnail to the same folder?" Not sure how this can Be done if possib?

  5. Toni Corvera says:

    Hi,

    VCS will output to the directory it was called from. To recursively place the generated files on the same directory as the video file you'll have to wrap it into a script or command-line that traverses the directories you want.

    For example something like:

    $ find folder/path -type d -exec sh -c 'cd "{}" && vcs *.avi' \;

  6. Not Tellin says:

    Hey Toni!

    Can you please direct me to the best place to discuss VCS issues? I have a problem with certain videos and don't know where to ask for help. I'm happy to provide any debugging info required.

    Thank you for your fantastic script. 😀

  7. Jose Alonso says:

    Hi Tony,

    There is a minor rounding problem when the miliseconds of
    the time is 0.995 or above.

    [i] Generating capture #16/30 (03:09.17)…
    [i] Generating capture #17/30 (03:20.100)…
    [i] Generating capture #18/30 (03:32.82)…

  8. Pär says:

    Seems to me you've lost interest in this project. Pity. Anyway, if you're still interested, I found a couple of bugs.

    One that affects movie file names with '-characters in them. vcs can't save the output. Input does not seem to be affected. My workaround:
    #output_name=$( safe_rename "$output" "$wanted_name" ) || {
    output_name=$( safe_rename "$output" "${wanted_name//\'/_}" ) || {
    Not optimal, but at least it writes the files.

    And one bug that showed up when ffmpeg and possibly, also IM or some other stuff on the system, got updated. Anyway, vcs no longer writes the footer. I have no workaround for that, though, since I really don't speak bash.
    \\// `(o_o)´ –"Live long and prosper!"

  9. Bao says:

    Hello! Thank you for VCS, it's really useful!

    I want to explain a small problem I have with it, hope you can help. If I use it with a video that has the filename in non-latin characters (like Chinese) the filename in the contact sheet is written as "????????.mp4".

  10. Toni Corvera says:

    Hi, for those cases you'll have to tell VCS to use a font that supports such characters using the --nonlatin (or -Ik) option, for example:

    $ vcs ... -Ik=/usr/share/fonts/opentype/noto/NotoSansCJK-Regular.ttc ...

    (adjust the command to load the appropriate font)

    Note --nonlatin doesn't take any arguments and will try to pick a font for you, but it will probably fail.


Please note: New comments won't appear immediately, they have to be manually approved (usually done quickly).

Leave a Reply

Your email address will not be published. Required fields are marked *