Hardware Transcoding issues - ApolloLake & GeminiLake CPUs

@CT9AJ & all.

PMS 1.32.3.7089 contains:

NEW:

  • (NAS) - Synology - Add support for DS223 family models (rtd1619 & rtd1619b processors)

FIXES:

  • (Collections) Wording of collections display preference was confusing (#12176)
  • (DVR) Finding USB device even if it’s plugged into a different USB port (#14288)
  • (Photos) “Recently Added in Photos” may not include any items in a sub folder (#12469)
  • (PlayQueue) Playing an episode in a show that has a later aired unmatched episode could play the wrong episode (#13315)

Plex Media Server.2.log (5.3 MB)
Plex Media Server.(2).log (4.8 MB)
Had to split my log file up because it was too large. You will be able to find my failure in the one with (2)

How it works.

  • On PMS restart, the codecs manager (which now includes all drivers) scans the hardware

  • Any drivers / codecs which need updating are downloaded.
    (previously these were included in the package file)

@CT9AJ

Would you do a simple restart of PMS.

Run the quick test

Now do a normal logs ZIP file ?

(If you’ve been hoarding the logs – e.g. (LogNumFiles > 5) – you can remove from preferences )

Ok - let me install the engineer build again hehe.
By restart you just mean, stop —> start right?

Yes. Stop - Restart - catch the failure again.

Adjust for maximum :fire:

Download the logs ZIP
Attach.

(it’ll be 5-ish MB)
:sunglasses:

Ok. Steps I just took:

  • Installed engineer build above
  • Stopped PMS (after it was installed of course)
  • Restarted PMS
  • Went to play item that would transcode
  • CPU usage went up all the way

Logs attached.
Plex Media Server Logs_2023-05-25_09-54-07.zip (2.6 MB)

Thanks.

Reviewing now

EDIT: See it. Forwarded to Engineer. Thank you.

1 Like

I had the same issue when moving to 1.32.2. The HW transcoding no longer was working. I have a haswell generation cpu.
Did your team require more logs? I moved back to 1.32.1 but I can move back for logs.

We’re all good for now thank you.

The Engineer got most of the Intel Core -3xxx -4xxx and -5xxx working now.
The remaining pieces (last I checked) are the J-series J33xx J34xx J4125, etc.

2 Likes

Do Anyone have any update on when the J-series will be fixed?

roll back to build 6999 for now.
feature wise, the drowngrade is minimal.

1 Like

Rolled back to build 6999 for now and hw transcoding is working again on my ds1019+.

This is why I went over to Emby long ago, I have one user remaining. Anyways, I won’t spoil the fun.

Thanks for the info.

ALL:

For those with the J3355, J3455, J4125 problem, as well as those with older Intel Core -3xxx and -4xxx CPUs,

The engineer has a file for you to test with.

There are specific instructions :

  1. Place this file in the Cache/va-dri-linux-x86_64 directory under Plex Media Server

  2. unzip it

  3. It will look like this when done.

root@glockner:/vol/plexmediaserver/Plex Media Server/Cache/va-dri-linux-x86_64# ls -la
total 9176
drwxr-xr-x 2 plex plex      69 May 30 12:00 .
drwxr-xr-x 9 plex plex    4096 May 30 11:59 ..
-rwxrwxrwx 1 root root 7815088 May 30 10:49 i965_drv_video.so
-rw-r--r-- 1 root root 1576222 May 30 12:00 i965_drv_video.zip
root@glockner:/vol/plexmediaserver/Plex Media Server/Cache/va-dri-linux-x86_64# 
  1. Make certain DEBUG logging is enabled, VERBOSE is disabled.

  2. Restart Plex

  3. Test

  4. Play for 20 seconds.

  5. Regardless of success or failure,
    – Report result
    – Attach Logs ZIP file (we need to confirm the behavior reported in the logs)

Hey, was there supposed to be a file in your message?

OOOPS :rofl:

Test file to use for all J3455 / J4xxx CPUs (HEVC HDR w/ tone mapping)

1 Like

Thanks! Which build should we try doing this with now?

Build 7100 is the best one to try with as it’s the most current.

Just did it, CPU did not shoot up to 100% :slightly_smiling_face:

Here are logs:

Plex Media Server Logs_2023-05-30_11-41-25.zip (4.2 MB)

@CT9AJ

To confirm:

Without this i965 driver, you did not have HW hardware transcoding ?

Do you have Preferences.xml customized ? ( VaapiDriver="i965" )
Your GeminiLake (J4125) should not need it.