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. Intel media-engine generations
  5. Intel Elkhart Lake and Jasper Lake media capabilities
Search Results for

    Show / Hide Table of Contents

    Intel Elkhart Lake and Jasper Lake media capabilities

    Elkhart Lake and Jasper Lake expose a documented low-power Intel media feature set whose AVC, HEVC and VP9 operations differ from newer AV1-capable implementation columns.

    Elkhart Lake and Jasper Lake combine modest general-purpose CPU resources with a dedicated Intel media path. CPU-core performance and media support need to be read separately.

    Intel's Media Driver groups these platforms in its EHL/JSL column.

    Identify the declared codec operations

    Selected rows in the pinned implementation table are:

    Configuration row Full-Feature build Free-Kernel build
    AVC D/E D/E
    HEVC 10-bit D/E D/E
    VP9 10-bit D/E D/E
    HEVC 10-bit 4:2:2 D D
    AV1 10-bit Not listed Not listed

    The rows preserve direction and sample configuration. A HEVC 4:2:2 decode declaration is a different fact from encoding that configuration.

    D/E also uses the source's operation legend. It does not say that an Emby build exposes every listed operation, profile limit or filter combination.

    HEVC and AV1 sources make different demands

    For an original selected-source comparison, assume a movie's compatible H.264 audio/video route and a HEVC Main 10 video route are both implemented on the device. Dedicated reconstruction can avoid asking the CPU to perform all of that video work.

    An otherwise similar AV1 source requires its own decoder. The EHL/JSL snapshot does not list the AV1 rows, while Tiger Lake-related columns do.

    A newer codec source can therefore change the CPU path or source-selection result without changing the server's device name. Xe-LP media capabilities explains the next relevant comparison.

    General CPU and media processing still cooperate

    Container parsing, audio handling and server coordination remain general software work. A CPU-side subtitle or colour operation can also introduce a different frame path after supported decoding.

    For an Emby server on a low-power system, these remaining stages can be significant even when decoding and encoding are supported by the media path.

    See Also

    • Intel Quick Sync Video (QSV)
    • Intel Kaby Lake media capabilities
    • Intel Xe-LP media capabilities
    • How to read a hardware codec support matrix
    • Driver-dependent media capabilities

    References

    • Intel Media Driver: Capability matrix snapshot
    • Intel: Published hardware media reference (2024)
    • Intel: Media Driver for VA-API
    • Emby: Hardware acceleration on Linux
    On this Page
    2026 © EMBY LLC. Please see our terms of use and privacy policy.
    Back to Top