HEVC Encoding options not showing up via Docker for Windows

Plex Media Server
,
1

Server Version#: Version 1.41.4.9399

I am running Plex through WSL2 via Docker for Windows. My CPU is an AMD Threadripper 2950x and GPU is a NVIDIA RTX 2080 TI. My compose file is below. nvidia-smi works and lists the 2080 TI in both WSL and the Docker container, and when hardware acceleration is enabled, I can verify it is actually using hw decoding and encoding via Tautulli. However, my GPU is never listed under the Hardware Transcoding Device…it only shows auto. Similarly, the HEVC options are not showing up. I cannot figure out how to fix this because it might be a specific nuance with how Docker for Windows makes the GPU available into the container, but it seems to work when it comes to the actual transcoding? I assume both my CPU and GPU should be able to do HEVC encoding.

Also, is this feature only available via HW Transcoding? Per the release notes, it implies it can work with a supported CPU, and I assume my 2950x is more than powerful enough to do it as well.

  plex:
    image: plexinc/pms-docker:plexpass
    container_name: plex
    environment:
      - PLEX_UID=${PUID}
      - PLEX_GID=${PGID}
      - UMASK=${UMASK}
      - TZ=${TZ}
      - NVIDIA_VISIBLE_DEVICES=all
      - NVIDIA_DRIVER_CAPABILITIES=all
    volumes:
      - ${CONFDIR}/plex:/config
      - previews:/config/Library/Application Support/Plex Media Server/Media
      - ${CACHEDIR}/plex/transcodes:/transcode
      - ${CACHEDIR}/plex/cache:/config/Library/Application Support/Plex Media Server/Cache
      - ${CACHEDIR}/plex/codecs:/config/Library/Application Support/Plex Media Server/Codecs
      - ${CACHEDIR}/plex/plugins:/config/Library/Application Support/Plex Media Server/Plug-in Support/Caches
      - ${LOGDIR}/plex/logs:/config/Library/Application Support/Plex Media Server/Logs
      - ${LOGDIR}/plex/crashes:/config/Library/Application Support/Plex Media Server/Crash Reports
      - ${LOGDIR}/plex/diagnostics:/config/Library/Application Support/Plex Media Server/Diagnostics
      - drivepool:/mnt/media:ro
    ports:
      - 32400:32400
      - 33400:33400
    deploy:
      resources:
        reservations:
          devices:
            - driver: nvidia
              count: 1
              capabilities: [gpu]
    hostname: ${HOSTNAME}
    logging: *default-logging
    labels: *default-labels
    restart: unless-stopped
2

Can’t help with the Docker stuff.

HEVC encoding is performed using the GPU, not the CPU. It requires a GPU capable of encoding HEVC 10-bit video (the 2080 is good to go).

In addition to the HEVC Encoding (Experimental) Public Release announcement, details are available in the HEVC Encoding Forum Preview thread.

The Nvidia Encode/Decode Matrix lists the capabilities of their GPUs.

Information for Intel Quick Sync is available on Wikipedia: Intel Quick Sync Video - Wikipedia

3

Ah understood regarding software encoding. The public release announcement is a bit unclear here because it mentions supported CPUs as below. Based on the matrix, the 2080ti should work for HEVC encoding. However, it is still not showing up as an option for me. Hardware transcoding is working, it just doesn’t seem to list the GPU as an option under Hardware Transcoding Device.

image
image835×351 31.8 KB

1 Like
4

Same situation. It says that hardware transcoding works, but no option for HEVC. Another interesting thing is that docker doesn’t give me the option to choose my GPU, there is only auto.

EDIT: I found a solution. I needed to add the contents of /dev/dri as devices, in my case:

devices:
  - /dev/dri/card1:/dev/dri/card1
  - /dev/dri/renderD128:/dev/dri/renderD128

Use cat /dev/dri to list yours.

5

For anyone still seeing this, there should be some improvements in the next release.

6

Unfortunately, it is still not showing up for me. Do you have more details on what the compose/expectation should be for it to show up? The Hardware Transcoding Device list still only shows Auto no matter if I map the /dev/dri devices or just use the deploy option. HW Transcoding is working in both cases

7

@rg9400 i would wait for 1.41.5 in a week or two

8

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.