X-Git-Url: https://git.sesse.net/?p=movit;a=blobdiff_plain;f=README;h=06afddee89782e1228eb3dab5f973b293e0db53a;hp=62c99d0c936b9ec4ee8b5f6ae5a146c9217e8ee1;hb=5e771df1523ea3f7926c0b5a115c29d134c53f11;hpb=c06f1c4cc39bbebe13fe8e42a9278a55b5d0a216

diff --git a/README b/README
index 62c99d0..06afdde 100644
--- a/README
+++ b/README
@@ -17,17 +17,15 @@ TL;DR, please give me download link and system demands
 
 OK, you need
 
-* A C++98 compiler. GCC will do. (I haven't tried Windows, but it
+* A C++11 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.)
+  If you also have the Google microbenchmark library, you can get some
+  benchmarks as well.
 * The [epoxy] library, for dealing with OpenGL extensions on various
   platforms.
 
@@ -93,15 +91,15 @@ 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:
 
-* 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.
+* 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 2015
+While from a programming standpoint I'd love to say that it's 2016
 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
+bandwidth reduction in broadcast video). Movit may eventually provide
 limited support for working with interlaced video; it has a deinterlacer,
 but cannot currently process video in interlaced form.
 
@@ -128,9 +126,9 @@ decoding.
 Exactly what speeds you can expect is of course highly dependent on
 your GPU and the exact filter chain you are running. As a rule of thumb,
 you can run a reasonable filter chain (a lift/gamma/gain operation,
-a bit of diffusion, maybe a vignette) at 720p in around 30 fps on a two-year-old
+a bit of diffusion, maybe a vignette) at 720p in around 30 fps on a four-year-old
 Intel laptop. If you have a somewhat newer Intel card, you can do 1080p
-video without much problems. And on a mid-range nVidia card of today
+video without much problems. And on a low-range nVidia card of today
 (GTX 550 Ti), you can probably process 4K movies directly.
 
 
@@ -208,4 +206,5 @@ What do you mean by “open-source”?
 ==================================
 
 Movit is licensed under the [GNU GPL](http://www.gnu.org/licenses/gpl.html),
-either version 2 or (at your option) any later version.
+either version 2 or (at your option) any later version. You can find the full
+text of the license in the COPYING file, included with Movit.