Emby Emby Emby Learn
  • Emby Home
  • Video
  • Audio
  • Media Files
    • Subtitles and captions
    • Photos and images
    • Metadata and discovery
    • Libraries and media collections
    • Playback and streaming
    • Media hardware acceleration
    • Displays and AV connections
    • Live TV and recording
  1. Emby Learn
  2. Media hardware acceleration
  3. Media-engine generations
  4. NVIDIA media-engine generations
  5. NVIDIA Pascal media capabilities
Search Results for

    Show / Hide Table of Contents

    NVIDIA Pascal media capabilities

    Pascal-family NVIDIA products have SKU-specific decode and encode resources, with selected HEVC capabilities and important encoder-presence exceptions in the published matrix.

    Pascal introduced media capabilities useful for mainstream H.264 and HEVC work, but the exact NVIDIA product is important. The family name alone does not establish that the device even includes an encoder.

    The current matrix supplies both feature columns and physical engine counts for named products.

    Use a concrete Pascal example

    For the GeForce GTX 1080 Ti row, selected entries include:

    Property Published declaration
    NVENC generation / count Sixth generation / two
    NVDEC generation / count Third generation / one
    HEVC ten-bit encoding Yes
    HEVC 4:2:0 ten-bit decoding Yes
    HEVC B-frame encoding No
    AV1 encode/decode No in the selected rows

    These facts concern the named product and matrix scope. Ten-bit encoding and picture-order tools are different feature questions.

    The two encoders are physical resources. They are not a rule that the server can run exactly two playback clients.

    A smaller Pascal product exposes a different role

    The GeForce GT 1030 entry reports zero NVENC, while its decoder table lists a decode resource and its supported configurations.

    A GT 1030 can therefore participate in applicable reconstruction work without supplying the same target-encoding route as the GTX 1080 Ti.

    That is a concrete hardware-presence distinction, rather than a driver setting that adds the missing encoder. An Emby session needing a new video representation would need another usable encoder path.

    Codec tools remain separate columns

    A published HEVC encoder does not supply every HEVC profile, chroma format or coding tool. The selected row's absent HEVC B-frame feature illustrates that refinement.

    Preset and rate-control comparisons should preserve the actual supported tool set. A setting with the same label on another generation can run under a different available feature set.

    Hardware encoding explains why rate, prepared pictures and implementation choices must be held together in a picture-quality comparison.

    Source reconstruction and target compression form the route

    A supported HEVC Main 10 input can still need scaling, SDR preparation or subtitle processing before H.264 output. An AV1 source asks for a decoder not established by the selected Pascal rows.

    See Also

    • NVIDIA Turing media capabilities
    • NVIDIA NVDEC
    • NVIDIA NVENC
    • How to read a hardware codec support matrix
    • Concurrent encoder sessions, policy and capacity

    References

    • NVIDIA: Video encode/decode support matrix
    • NVIDIA SDK 13.1: NVENC capabilities and session policy
    • NVIDIA SDK 13.1: NVDEC capabilities
    • NVIDIA SDK 13.1: NVENC programming guide
    On this Page
    2026 © EMBY LLC. Please see our terms of use and privacy policy.
    Back to Top