Disable dither explicitly per frame; fixes some weird artifacts I found.

[movit] / README

diff --git a/README b/README
index 81bb4c99e2f8428cca5b417c6fd7801c17a57103..05ba9f3cd89f292cf9a10e1d8fd93a71b9f5fb00 100644 (file)
--- a/README
+++ b/README
@@ -9,7 +9,7 @@ Movit is the Modern Video Toolkit, notwithstanding that anything that's
 called “modern” usually isn't, and it's really not a toolkit.
 
 Movit aims to be a _high-quality_, _high-performance_, _open-source_
 called “modern” usually isn't, and it's really not a toolkit.
 
 Movit aims to be a _high-quality_, _high-performance_, _open-source_

-library for video filters. It is currently in alpha stage.
+library for video filters.

 
 
 TL;DR, please give me download link and system demands
 
 
 TL;DR, please give me download link and system demands


@@ -25,8 +25,9 @@ OK, you need
   part of OpenGL 3.0 or newer, although most OpenGL 2.0 cards also
   have what's needed through extensions). If your machine is less than five
   years old _and you have the appropriate drivers_, you're home free.
   part of OpenGL 3.0 or newer, although most OpenGL 2.0 cards also
   have what's needed through extensions). If your machine is less than five
   years old _and you have the appropriate drivers_, you're home free.

-* The [Eigen 3] and [Google Test] libraries. (The library itself
-  depends only on the former, but you probably want to run the unit tests.)
+  GLES3 (for mobile devices) will also work.
+* The [Eigen 3], [FFTW3] and [Google Test] libraries. (The library itself
+  does not depend on the latter, but you probably want to run the unit tests.)

 * The [epoxy] library, for dealing with OpenGL extensions on various
   platforms.
 
 * The [epoxy] library, for dealing with OpenGL extensions on various
   platforms.
 


@@ -40,10 +41,11 @@ for performance estimates.
 Still TL;DR, please give me the list of filters
 ===============================================
 
 Still TL;DR, please give me the list of filters
 ===============================================
 

-Blur, diffusion, glow, lift/gamma/gain (color correction), mirror,
-mix (add two inputs), overlay (the Porter-Duff “over” operation),
-scale (bilinear and Lanczos), sharpen (both by unsharp mask and by
-Wiener filters), saturation (or desaturation), vignette, and white balance.
+Blur, diffusion, FFT-based convolution, glow, lift/gamma/gain (color
+correction), mirror, mix (add two inputs), luma mix (use a map to wipe between
+two inputs), overlay (the Porter-Duff “over” operation), scale (bilinear and
+Lanczos), sharpen (both by unsharp mask and by Wiener filters), saturation
+(or desaturation), vignette, and white balance.

 
 Yes, that's a short list. But they all look great, are fast and don't give
 you any nasty surprises. (I'd love to include denoise, deinterlace and
 
 Yes, that's a short list. But they all look great, are fast and don't give
 you any nasty surprises. (I'd love to include denoise, deinterlace and


@@ -54,8 +56,8 @@ all research-grade problems, and Movit is currently not there.)
 TL;DR, but I am interested in a programming example instead
 ===========================================================
 
 TL;DR, but I am interested in a programming example instead
 ===========================================================
 

-Assuming you have an OpenGL context already set up (currently you need
-a classic OpenGL context; a GL 3.2+ core context won't do):
+Assuming you have an OpenGL context already set up (either a classic OpenGL
+context, a GL 3.x forward-compatible or core context, or a GLES3 context):

 
 <code>
   using namespace movit;
 
 <code>
   using namespace movit;


@@ -91,12 +93,12 @@ OK, I can read a bit. What do you mean by “modern”?
 Backwards compatibility is fine and all, but sometimes we can do better
 by observing that the world has moved on. In particular:
 
 Backwards compatibility is fine and all, but sometimes we can do better
 by observing that the world has moved on. In particular:
 

-* It's 2014, so people want to edit HD video.
-* It's 2014, so everybody has a GPU.
-* It's 2014, so everybody has a working C++ compiler.
+* It's 2015, so people want to edit HD video.
+* It's 2015, so everybody has a GPU.
+* It's 2015, so everybody has a working C++ compiler.

   (Even Microsoft fixed theirs around 2003!)
 
   (Even Microsoft fixed theirs around 2003!)
 

-While from a programming standpoint I'd love to say that it's 2014
+While from a programming standpoint I'd love to say that it's 2015

 and interlacing does no longer exist, but that's not true (and interlacing,
 hated as it might be, is actually a useful and underrated technique for
 bandwidth reduction in broadcast video). Movit will eventually provide
 and interlacing does no longer exist, but that's not true (and interlacing,
 hated as it might be, is actually a useful and underrated technique for
 bandwidth reduction in broadcast video). Movit will eventually provide