Remove some unneeded conversions from ResampleEffect. Speeds up texture generation...

[movit] / README

diff --git a/README b/README
index 8e47db753733cbe0610259b6d640ce30f34e512a..bc6a5a87a58e80c0ab4821888cfa6643d5f2d2e4 100644 (file)
--- a/README
+++ b/README
@@ -20,12 +20,8 @@ OK, you need
 * A C++98 compiler. GCC will do. (I haven't tried Windows, but it
   works fine on Linux and OS X, and Movit is not very POSIX-bound.)
 * GNU Make.
 * A C++98 compiler. GCC will do. (I haven't tried Windows, but it
   works fine on Linux and OS X, and Movit is not very POSIX-bound.)
 * GNU Make.

-* A GPU capable of running GLSL fragment shaders,
-  processing floating-point textures, and a few other things (all are
-  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.
-  GLES3 (for mobile devices) will also work.
+* A GPU capable of running OpenGL 3.0 or newer. 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
 * 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


@@ -93,9 +89,9 @@ 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 2016, so people want to edit HD video.
-* It's 2016, so everybody has a GPU.
-* It's 2016, so everybody has a working C++ compiler.
+* It's 2017, so people want to edit HD video.
+* It's 2017, so everybody has a GPU.
+* It's 2017, so everybody has a working C++ compiler.

   (Even Microsoft fixed theirs around 2003!)
 
 While from a programming standpoint I'd love to say that it's 2016
   (Even Microsoft fixed theirs around 2003!)
 
 While from a programming standpoint I'd love to say that it's 2016