From: Steinar H. Gunderson Date: Tue, 23 Jan 2018 21:14:06 +0000 (+0100) Subject: Typo fixes. X-Git-Tag: 1.6.0~1 X-Git-Url: https://git.sesse.net/?p=movit;a=commitdiff_plain;h=9be82157cfc320d6669d82ab9057862067b77325;hp=df680997fd54d7949a7d83edfa02d870e581527c Typo fixes. --- diff --git a/README b/README index aef8bc7..dfddd7a 100644 --- a/README +++ b/README @@ -116,13 +116,13 @@ fragment shaders. While “run on the GPU” does not equal “infinite speed” GPU programming is probably the _simplest_ way of writing highly parallel code, and it also frees the CPU to do other things like video decoding. -Although compute shaders are supported, and can be used or speedups if +Although compute shaders are supported, and can be used for speedups if available (currently, only the deinterlacer runs as a compute shader), it is surprisingly hard to get good performance for compute shaders for anything nontrivial. This is also one of the primary reasons why Movit uses GLSL and not any of the major GPU compute frameworks (CUDA and OpenCL), although it is also important that it is widely supported (unlike CUDA) and driver quality -general is fairly good (unlike OpenCL). +generally is fairly good (unlike OpenCL). 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,