Changes between Version 33 and Version 34 of Encodings/nvenc

Timestamp:

11/07/14 14:46:23 (8 years ago)

Author:

Antoine Martin

Comment:

--

Encodings/nvenc

@@ -34 +34 @@
 == Using NVENC ==
 
-If your CUDA or NVENC libraries are installed in an unusual location, it is your responsibility to ensure they can be loaded at runtime (usually adding the directory to the {{{LD_LIBRARY_PATH}}}).
+You must have recent enough nvidia drivers installed. How to install those drivers is entirely up to you: [http://www.nvidia.com/object/unix.html nvidia installers], [http://negativo17.org/nvidia-driver/ negativo17 repository], [http://rpmfusion.org/ rpmfusion], [http://elrepo.org/tiki/tiki-index.php elrepo], etc..
 
-If the nvenc codec loads, it should get used ahead of x264 when you specify the `h264` encoding, you can verify the encoder in use with:
+If your CUDA ({{{libcuda.so}}}) or NVENC ({{{libnvidia-encode.so}}}) libraries are installed in an unusual location, it is your responsibility to ensure they can be loaded at runtime, usually by adding the directory to the {{{LD_LIBRARY_PATH}}}.
+
+If the nvenc codec loads, it will be used ahead of x264 when you specify the `h264` encoding, you can verify the encoder in use with:
 {{{
 xpra info | grep "encoder="
 }}}
 
-Note: your client must be either 0.15 or newer. (older versions require the full CUDA SDK)
+Note: your xpra version must be either 0.15 or newer. (older versions require the full CUDA SDK and a more complicated setup)
 
 To force xpra to use nvenc as video encoder and no other, you can also use the {{{--video-encoders=}}} command line option:
@@ -57 +59 @@
 
 {{{#!div class="box"
-== License Key ==
-As of version 0.15, you can store the license keys in {{{nvenc.keys}}} (either globally in {{{/etc/xpra/}}} or per-user in {{{~/.xpra/}}}).
+== License Keys ==
+As of version 0.15, you can store the license keys in {{{nvenc.keys}}}, either globally in {{{/etc/xpra/}}} or per-user in {{{~/.xpra/}}}.
 
 Or you can also use the environment variable: