PMS 1.32.4.7164 : Still have issues with HW Transcoding (Synology DS 1019+)

Plex Media Server NAS & Devices
,
1

Server Version#: 1.32.4.7164
Player Version#: 4.108.0

PMS running on Synology DS 1019+ . PMS running on Docker
DSM 7.1.1-42962 Update 4

Plex Media Server.log (646.9 KB)

Hi,

After noticing the recent HW transcoding problem, I switched to version 1.32.1.6999 as recommended and everything worked again.

Seeing the new version 1.32.4.7164, I wanted to test to see if the problem was solved. Unfortunately the problem still exists on my synology server with the processor: INTEL Celeron J3455 1.5 GHz.

You will find the logs in order to investigate in more detail. (see at Jun 06, 2023 00:44:57.346, line 2175)

2

Hi,

Same thing here but with a terra master F4-422 with intel J3455 1.5 GHz. I had to roll back to version 1.32.1.699 to have hardware transcoding. All version after that, the hardware transcoding doesn’t work. Please fix this.

Thanks

3

Spoke to the engineer tonight.

The ApolloLake fixes will be in the next PMS build/release from what I can see.

There is a fundamental change here for folks to understand.

  1. There is an educational change needed here. The i965 driver is old and dated. It shouldn’t be used. The Intel Media Driver is the established replacement for a few years now. Please refrain from i965.

  2. DO NOT USE VaapiDriver="i965" in Preferences.xml without first checking with first confirming the Intel Media Driver doesn’t work -and- you’ve reached out to us.

There might be an issue here and there but, if we don’t heard about them then we won’t know what needs fixing.

Bottom line – No VaapiDriver="i965" in Preferences.xml should ever be needed.

3 Likes
5

Apollo Lake

https://www.intel.com/content/www/us/en/products/sku/95597/intel-celeron-processor-j3355-2m-cache-up-to-2-50-ghz/specifications.html

6

Sorry if this has been asked before… I’m using a Synology DS720+ that has the Celeron 4125 / Gemini Lake family so is it ‘ok’ to upgrade from 1.32.1.6999 or should I wait?

Thanks!

7

Using LinuxServer.io docker container with the following mod:

This allows me to use the embedded AMD chip in my HP T730 which is hosting my Plex Server.

This version is also not hw transcoding anymore. Reverting to 1.32.1.6999 resolves the issue. I get the same error others are getting.

My video driver is:

VAAPI driver: Mesa Gallium driver 22.3.6 for AMD Ryzen Embedded V1756B with Radeon Vega Gfx (raven, LLVM 15.0.7, DRM 3.49, 6.1.0-0.deb11.7-amd64)

8

@rahzadan

Telling us there’s a problem but not providing the logs with them is like telling your Dr you’re sick but then not going in to be seen. :rofl:

May we have the DEBUG logs ZIP file which captures the failure?

9

I was also experiencing an issue with Plex 1.32.3.7162 (docker) not leveraging hardware transcoding as I would expect.

Rolling-back to an earlier version (1.31.3.6868) resulted in hardware transcoding working.

So based on what @ChuckPa mentioned about the VaapiDriver="i965" in Preferences.xml, I removed this reference and restarted Plex against the current version (1.32.3.7162 ) and once again hardware transcoding seems to be working again.

10

TO ALL FOLLOWING HERE:

There are only a very few CPUs which need the i965 driver.

The best first choice is to use the default Intel Media Driver due to the recent major upgrade of the media driver released a few versions ago. (1.32.0)

Some CPUs will need the upcoming ApolloLake correction but will then run without the i965 being manually selected.

11

@ChuckPa

Here are my server logs.

Plex Media Server Logs_2023-06-07_09-20-02.zip (13.0 KB)

Here is my Docker Compose:

Blockquote

version: “2.1”
services:
plex:
image: lscr.io/linuxserver/plex:latest
container_name: plex
network_mode: host
group_add:
- “106”
environment:
- PUID=1000
- PGID=1000
- TZ=Canada/Atlantic
- VERSION=1.32.1.6999-91e1e2e2c
- DOCKER_MODS=jefflessard/plex-vaapi-amdgpu-mod
devices:
- /dev/dri/

volumes:
  - /srv/dev-disk-by-uuid-f150e77a-a744-4146-b9e3-25f6530e62f9/plex/config:/config
  - /srv/dev-disk-by-uuid-f150e77a-a744-4146-b9e3-25f6530e62f9/plex/content:/content
  - /tmp:/transcode
restart: unless-stopped
12

Its definitely needed on the J3455 in order to get subtitle burning working.

No joy with the iHD driver.

1 Like
13

@pommesmatte

Thanks for confirming that.

I’m still running behind the :8ball: here due to health.

RUn with the i965 for now. The ApolloLake fix in the next PMS release should fix it up for you.

(there are too many ‘test builds’ in flight for me to keep track of right now – sorry)

1 Like
14

9 posts were merged into an existing topic: Unraid Nvidia Transcoding, cant get it to work

15

2 posts were merged into an existing topic: 1.32.2.7002

16

4 posts were split to a new topic: Unraid + Nvidia GPU HW transcoding issue

17

Same here. Qnap 453be with a Intel Celeron J3455. Waiting for the fix :slight_smile:

18

Should be fixed in 1.32.5.7210.

Hardware accelerated transcoding works on my Synology DS918+ with same CPU.

1 Like
19

i965 Driver is still broken in 1.32.5. No HW transcoding possible.

20

You don’t need to add the driver into the Plex data folder or reference it in preferences.xml.

Hardware transcoding works on my DS918+, with J3455 CPU, when running 1.32.5.

21

@pommesmatte

Forget the i965.

The Intel Media Driver update has fully obsoleted it on all but the old Sandy Bridge and Ivy Bridge CPUs.