All Projects

In the past BuildConfig.DEBUG wasn’t reliable (when combining Eclipse and ADT), but on Android Studio with Gradle it can be used safely and hence there’s no need to duplicate the functionality.

No need for description

No need for description

Fails on some files (gets stuck forever while capturing the first frame).

Happens often with Matroska. 1.0.7a introduced a workaround (-Wo) with ffmpeg’s argument order that worked with other file types.

/dev/shm isn’t really intended as an alternate temporary location, and VCS’ temporary files can easily grow too large for it too.

As a possible alternative offer a first-run choice of temp-dir (maybe suggesting /dev/shm).

References:
http://wiki.debian.org/ReleaseGoals/RunDirectory#Why_put_.2BAC8-dev.2BAC8-shm_and_.2BAC8-tmp_under_.2BAC8-run.3F http://stackoverflow.com/questions/9745281/tmp-vs-dev-shm-for-temp-file-storage-on-linux

Reported by Willy Romano 23/03/2017 on the Google Play

On Huawei G8. App doesn’t automatically execute when phone is turned off then back on. I protected the app and this seems to have solved the problem.

This task depends on reports of such issue.

So far all reports are on Marshmallow:

Reported by Charles Kanegeni 20/02/2016 on Google Play

New issue Great app, have always used it. Just upgraded to marshmallow and now it won’t even start. What’s up with that? From Android 5 I had problems, plus doesn’t support dual Sim phones. This is the new direction, twin Sim phones. Please work it out.

Infinix (Infinix_X510_sprout) / 6.0 / r14034

Reported by Red Rospo 04/08/2016 on Google Play

Da migliorare Non parte al boot

LG G5 (h1) / Marshmallow / r14034

Reported by Simon Howard 18/12/2016 on Google Play

Issue with auto start on boot I’ve had this app for some time now, but it will not auto start on boot on my current phone (Galaxy S5, Marshmallow 6.01)

Galaxy S5 (klte) / Marshmallow / r14034

Currently off Google Play due to failing to meet a deadline on policy changes.

Currently unable to re-stablish due to being away from my keys

Originally reported by Pär: https://outlyer.net/2019-11-26:vcs-1-13-4-released/comment-page-1/#comment-60689

Another thing that is a little bit annoying, but isn't a very big deal, is the fact that videos made from a phone where the image is rotated in metadata, doesn't produce a correct aspect ratio. For example, a video that is stored as 1920×1080 (16:9), but shown as 1080×1920 (9:16), due to metadata rotation, vcs will create thumbnails in 1920×1080 aspect ratio (16:9) but show them rotated correctly, which means the image at 9:16 gets squashed to fit into 16:9. Like I said, not a very huge deal, but it looks somewhat silly and it would be great if it was possible to fix.
I've tried to see if I could set the aspect parameter but it doesn't seem to do much when the rotation is made in metadata. Metadata usually state something like:
>
> "`bash
Side data:
displaymatrix: rotation of -90.00 degrees
"`

Appears to be an incompatibility with current ImageMagick (6), happens with old versions of vcs too

When the resulting contact sheet is too thin, the meta-information header is cramped and fields overlap.

Originally reported by Dougn Redhammer

Original report by Dougn Redhammer

vcs hangs with some RM files.

Tracing shows it gets stuck in mplayer_identify.

MPlayer can play the files fine from the terminal. Although it exits with «MPlayer interrupted by signal 11 in module: uninit_vcodec».

I can reproduce the abrupt termination, it happens when using Real’s native decoder (w64codecs, /usr/lib/codecs/drvc.so). Using FFMpeg’s decoder (MPlayer’s -vc ffrv30) MPlayer exits normally.

I can’t reproduce the hang either way.

The available configuration options need a serious review and renaming. Old names will be accepted with warnings for either two releases or six months.

Also, should provide a sample configuration file so that the syntax and options are clearer.

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.

See http://libav.org/, Jan 27 2012.
Also http://libav.org/index.html#fftools_rename for changes to the syntax.

Must change to avprobe/ffprobe and/or avconv.

Rendering on RTL devices is does not work properly due to alignment problems.

Attached: Screen grabs from the pre-release report on an Arabic device.

Material design icons are supposed to be white according to comments found online and most apps.

(I can’t find an actual upstream reference) Found at http://www.androiddocs.com/design/style/iconography.html

Dark icons are displayed white in practice.

Reported by Terry Parrott

Reports that the app won’t auto load despite having the option enabled.

Reported on Oreo.

Presumably related to FS#370.

The app force-closes on device boot when load on boot is enabled.

Once the boot is complete it behaves normally.

Seen in Oreo.

Presumably related to FS#369.

Reported by Paul:

Hey,
I'm using VCS via Homebrew Install (https://formulae.brew.sh/formula/vcs#default) and since the last update of imagemagick (?) I get dozens of error messages:
convert: Expected operator at '.mean*100' @ error/fx.c/GetOperator/2408

Confirmed to happen on ImageMagick 7.1 on Linux, the contact sheet is generated but blank frame evasion is skipped

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.

Originally reported by Pär: https://outlyer.net/2019-11-26:vcs-1-13-4-released/comment-page-1/#comment-60674

Recently got an update of ImageMagick:

$ magick --version
Version: ImageMagick 7.1.1-33 Q16-HDRI x86_64 22263 https://imagemagick.org
Copyright: (C) 1999 ImageMagick Studio LLC
License: https://imagemagick.org/script/license.php
Features: Cipher DPC HDRI Modules OpenCL OpenMP(4.5) 
Delegates (built-in): bzlib cairo djvu fftw fontconfig freetype heic jbig jng jp2 jpeg jxl lcms lqr ltdl lzma openexr pangocairo png raqm raw rsvg tiff webp wmf x xml zip zlib zstd
Compiler: gcc (14.1)

Because of that, the "convert" command now gives a deprecation warning:

WARNING: The convert command is deprecated in IMv7, use "magick"

Trying to do that, replacing all the calls to 'convert' for 'magick', the temp images seem to be problematic (I've added a few printouts of the suspected code blocks):

[i] Capturing in range [04:49.49-19:17.95]. Total length: 20:25.35
[i] Generating capture #1/4 (04:49.49)...
magick: no images found for operation `-geometry' at CLI arg 7 @ error/operation.c/CLIOption/5479.
magick: magick -background 'transparent' -fill 'transparent' '/dev/shm/vcs.SGteWR/vcs-ZQ0dJj-cap-000001.png'   \( -geometry 267x200! \)  -flatten   \( -box '#000000aa' -fill 'White' -stroke none -pointsize '9'     -gravity 'SouthEast' -font '/usr/share/fonts/TTF/DejaVuSans.ttf' -strokewidth 3 -annotate +5+5     ' 04:49.49 ' \) -flatten -gravity None  -flatten  \( -background black +clone -shadow 50x2+4+4 -background none \) +swap -flatten -trim +repage  -flatten  '/dev/shm/vcs.SGteWR/vcs-zQhKDd.png'

If I try to cp those two temp images on the line below the 'magick' command, they become 0 byte files.

The video renderer ffmpeg has also gone through a couple of steps of upgrades over the years, I now have:

$ ffmpeg -version
ffmpeg version n6.1.1 Copyright (c) 2000-2023 the FFmpeg developers
built with gcc 13.2.1 (GCC) 20230801

So commands like '-vframes' is now '-frames:v' and so on. No errors, just friendly suggestions in the man page. I replaced those also, but still the same problem.

I should have listened more carefully when our kindergarten teacher went through Bash. ;) IOW, I'm sure it's something simple I am not understanding.

N.b. I can still use vcs with the normal 'convert' command, but depending on how "militia force" serious the ImageMagick gang is going to be about deprecation warnings and removal of old code, it might stop working at some point in the future and I think that would be sad.

Any ideas? Thanks! :)

Originally suggested by Dogn Redhammer

Originally reported by Phil Grundig

Version of ffmpeg: ffmpeg (CVS-060515)