Changes between Version 50 and Version 51 of CSC

Timestamp:

04/18/16 07:38:29 (5 years ago)

Author:

Antoine Martin

Comment:

--

CSC

@@ -19 +19 @@
 
 On the server side we currently (as of v0.11) support 4 modules for doing this step:
+* [/browser/xpra/trunk/src/xpra/codecs/csc_libyuv/colorspace_converter.pyx csc_libyuv] which uses [https://code.google.com/p/libyuv/ libyuv]'s optimized CPU code (new in 0.17 - the fastest option)
 * [/browser/xpra/trunk/src/xpra/codecs/csc_swscale csc_swscale] which uses [http://www.ffmpeg.org/ FFmpeg]'s swscale library (CPU based)
 * [/wiki/CSC/OpenCL csc_opencl] (GPU or CPU based via [http://www.khronos.org/opencl/ OpenCL])
-* [/browser/xpra/trunk/src/xpra/codecs/csc_libyuv/colorspace_converter.pyx csc_libyuv] which uses [https://code.google.com/p/libyuv/ libyuv]'s optimized CPU code (new in 0.17, in progress)
 * [/browser/xpra/trunk/src/xpra/codecs/csc_opencv/colorspace_converter.pyx csc_opencv] which uses [http://opencv.org] (new in 0.17, in progress)
 * [/browser/xpra/trunk/src/xpra/codecs/csc_cython/colorspace_converter.pyx csc_cython]: a much slower fallback module written in Cython
@@ -35 +35 @@
 
 The best way to choose a CSC module is to test them all and [/wiki/CSC/Performance compare them].
+If you can use [/wiki/Encodings/nvenc NVENC], then do so: the CSC step is builtin and will use the GPU hardware.
+Otherwise, use {{{libyuv}}} or {{{swscale}}}.
+If you are CPU starved and have GPU cycles to spare, then you may want to try {{{opencl}}}.
 }}}
 
@@ -40 +43 @@
 == Specify a module or mode ==
 
-As of version 0.12 (r5376), one can choose which csc modules get loaded into the server using the {{{--csc-modules=}}} command line option. ie:
+As of version 0.12 (r5376), one can choose which csc modules are loaded using the {{{--csc-modules=}}} command line option. ie:
 {{{
-xpra start :10 --csc-modules=libyuv,opencl,swscale
+xpra --csc-modules=libyuv,opencl,swscale
 }}}