HW Transcoding Not Working for HVEC/H265 Content (1019+)

Plex Media Server NAS & Devices
,
1

Server Version#: 1.32.7.7484
Player Version#: 8.25 (iOS)

Transcoding HVEC content has functionally stopped working for me because without hardware transcoding, it is too slow to be usable. I’m using the Plex server in a docker container. The container states hardware permissions are good, and this is backed up by hardware transcoding working fine for non HVEC content. I believe this may have started with DSM 7 but I am not sure. I only recently upgraded. I also tried adding the i965 Vaapi line to my preferences.xml, but that did not appear to change anything. I found another forum post here with the same thing, but in a web link form, but when I try that I just get a 404 not found message. Any help is super appreciated.

1 Like
2

It may be related to this:

From what PMS version did you upgrade? (Some) versions 1.32.5.x and below worked fine. Also, try disabling HDR tone mapping in your Settings → [Server Name] → Transcoder settings. That seems to be the catalyst for some failures.

Regardless, you probably should post in the linked thread with the information requested.

3

If I may add here?

The J3455 CPU (DS1019+) is OK until 1.32.6 / 1.32.7

Options for you – Depending on how much you want to fuss with it

  1. Native - 1.29.2 - Solid but older (from Package Center)
  2. 1.31.3.6868 - native or docker (predates the start of the changes with the 1.32.x)
  3. 1.32.5.7210 - works and has ApolloLake HW transcoding working in it (pre-regression)
4

1.32.7.7484 also cannot perform hardware transcoding normally on the 918+ DSM 7.1 system.

Currently using 1.32.6.7371, the system can play 4K HDR videos directly, and HDR videos can also be played through hardware transcoding.

5

ALL:

I just finished testing -

Both 1.32.6 and 1.32.7 fail with HDR transcoding (tonemapping fails)

1.32.5.7349 - works
1.32.5.7210 - works

I can provide 1.32.5.7349 is anyone wants it.

Docker users only need pull 1.32.5.7349-8f4248874

Current diagnostic status

We think we found where the divergence (fault) occurred.
In order to test (confirm), we need to complete a full build of PMS

This build is currently running on the build system.

We will know more in the morning (US EDT time)

2 Likes
6

7349 is perfect and I’m never budging off it until some REALLY cool feature ever comes out, for my 1019+ :wink: If it aint broke, don’t fix it. With Plex as it is these days, new releases are simply beta IMO.

8

You have to unfortunately, this build has a major transcoding error which the newest build fixed

9

Would there be a reason autoscan docker stop working? Someone reported the new beta fixed 4k trans but autoscan stopped reaching plex

10

Automatic detection is a function of the Linux host (Synology DSM)

Here is the DSM-specific instructions to see if tweaking of DSM is needed

11

Sorry i asked this here which obv confused you, i am talking about

which we have to use if we use plex in a different machine with mounting drives, there are reports the last beta somehow made plex unreachable in this app

12

I suggest you discuss that with the author as there’s nothing we can do.

13

Thanks, going to be tricky since developments stopped on that

14

Any news yet?

15

Yes,

  1. :coffee: (I’m just waking up)
  2. I’ve got the new build running (testing)
  3. LOOKING GOOD
4 Likes
16

Random but does the new build change the way scanner is being called or the endpoint of the scanner?

17

Update:

Build was looking good but did not pass muster.

18

I’m on Synology, 1019+ and most videos are HVEC/H265. I haven’t noticed HW transcoding not working but then again PMS tends to Direct play for me but I worry about my friends and whether they are getting HW transcoding.

As a note, for a while, I didn’t have HW transcoding even configured and never noticed any streaming problems.

19

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