All Projects

Gradle allows to define fields on the generated class BuildConfig. This should be enough to discard the current per-build-type classes.

Example: https://stackoverflow.com/questions/24518940/custom-fields-for-a-build-type-in-gradle

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.

As of 2019-07 usage below KitKat is anecdotal:

2.3.x: 0.04%
4.0.x: 0.07%
4.1: 0.86%
4.2: 1.35%
4.3: 0.82%

2.3 to 4.3: 3.14%

4.4: 6.28%
5.0: 4.33%

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

Next: FS#192

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

First version allowing multiple file sharing.
Possibly release early and keep as alpha or beta to test further.

Meta-task depending on tasks scheduled for the 1.4 release.

Previous release:  FS#234  (1.3.1)

It just makes more sense

Useful for debugging, likely not useful for users since the command-line already overrides configurable arguments

Should provide an easy way to generate a new configuration file based on the provided command-line arguments.

No need for description

The progress bar should reflect when the size of the shared file is unknown.

Possibly using a dynamic ZIP file

See http://developer.android.com/reference/java/util/zip/ZipOutputStream.html

This is necessary for ZIP files constructed on the fly.

The current webserver implementation doesn’t support that.

The chunked transfer encoding is necessary to serve files of unknown size (created dynamically)

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.

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.

Originally suggested by Dogn Redhammer

Originally reported by Phil Grundig

Version of ffmpeg: ffmpeg (CVS-060515)

Originally reported by Phil Grundig

Version of mplayer: mplayer (1.0pre8cvs)

Originally reported by Tomasz Strózik

Example given:

$ find $DIR \(-name "*.avi" -o -name "*.wmv" -o -name "*.mpg" -o -name "*.mp4" \) -exec vcs -dt -ds -n 12 -c2 -H 200 --jpeg --quiet {} \;

Works on avi, mpg and mp4 but fails on wmv with
Failed to capture frame (at second xxx.000)

Processing the same file directly works:

$ vcs -dt -ds -n 12 -c2 -H 200 --jpeg --quiet File.wmv

Timestamps could use some tweaking: e.g. centering on their background and rounded corners

No need for description