NoMachine Support

Your questions answered

Knowledge Base

Searching in: Feature Requests
Filter the search results
Target version:
Products:
Status:
Last update:
Searching in: Feature Requests
ID: FR04R03973
Added on:  2020-04-16
Last update: 2020-07-24
Priority: Low
Products: NoMachine Server
Target: 6
Status:  Approved
Adding more information to the UI about the codec in use

We can consider the codec string as divided into two distinct parts separated by a slash ("/"): the first part indicates the framework used for encoding and the second part the framework used for decoding.

In the first part of the string the video encoding is specified by the codec name, like H264, VP8 or MJPEG.

The encoding framework can be HW assisted, and in this case the codec will be followed by one of these identifiers: 
NVENC -> Nvidia hardware encoder.
VCE -> AMD hardware encoder.
QS -> Intel QuickSync hardware encoder.

Nothing will be specified instead when the software encoding is used.


When the decoding framework (on the end-user device) is HW assisted, it will be specified in the second part of the string after the slash ("/"). It can be identified by any of the following:
DXVA -> hardware decoder on Windows
VDA -> hardware decoder on Mac
VAAPI -> the hardware decoder on Linux

Nothing will be specified instead when the software decoding is used.

Some examples:

Display 1360x768, codec H.264, audio Opus 22kHz stereo
(H.264 software encoding, software decoding)

Display 1360x768, codec H.264 NVENC, audio Opus 22kHz stereo
(H.264 NVENC hardware encoding/ software decoding)

Display 1360x768, codec H.264/DXVA, audio Opus 22kHz stereo
(H.264 software encoding/ DXVA hardware decoding)

Display 1360x768, codec H.264 QS/VDA, audio Opus 22kHz stereo
(H.264 QuickSync hardware encoding/ VDA hardware decoding)

Display 1360x768, codec VP8, audio Opus 22kHz stereo
(VP8 software encoding/ VP8 software decoding)


Notify me when the FR is implemented.