All Projects

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

v2.0 will be a rewrite in Python.

Previous: FS#153

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%

Should allow to disable it in both configuration and command-line.

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

Originally suggested by Dean: http://outlyer.net/2010-08-24:vcs-1_12-2-released/

” [...]

Second, my dvd-drive is useless atm, but i remember previously piping dvd-ouput from mplayer into ffmpeg via a fifo and finding the info generated to be much better than mplayer-alone – for one thing, it won’t ‘downmix’ 6-channel audio automatically. Don’t know if that would be useful to you. The syntax was something like:-

mkfifo piped.vob &&
mplayer dvd:// -dumpstream -dumpfile piped.vob & \
ffmpeg -i piped.vob

…See what you think…
”

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.