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

It seems I’m maybe talking to a wall here?

Intel Media Driver is not able to burn subtiltes, where the i965 is able to without a problem.

And as Plex refuses to fix that problem with iHD I’m bound to use i965, but its broken since at least 1.32.2.

I need i965 in order to use subtitle burning.

iHD fails to burn subtitles (slow as hell) on my J4125.

Intel Media Driver has never burned subtitles in hardware.
Plex has never burned subtitles in hardware.

No, you do not need i965 to burn subtitles.
Subtitles are burned by the CPU. not the i965 hardware interface.

You’re mixing QSV with VAAPI.

Plex does not use the “QSV” interface. We (all) unfortunately interchange the two terms.

Plex HW transcoding is:

  • VAAPI (Intel and AMD)
  • Nvidia DEC / Nvidia ENC

Sigh, how many times should I explain that again?

I KNOW that subtitle burning is carried out by the CPU, but everytime thats brought up you miserably fail to explain the following simple fact:

HW transcoding with i965 and subtitle burning WORKS (with 2-3 times speed)

HW transcoding with iHD and subtitle burning DOESN’T WORK (0.1-0.2 times speed)

→ i965 is needed for subtitle burning

Sigh,

Again,

Gemini Lake HW transcoding is BROKEN in versions above 1.31.3.6999

It works for ApolloLake now but not for GeminiLake

Is this your NAS?

Sigh and that is related to my issue?

So when you fix GeminiLake I will be able to use i965 and Subtitle burning again?

EDIT: Just to be clear, HW transcoding itself works with iHD, but not with subtitle burning. Neither prior nor past 1.31.3

Your BEST CHOICE here

  1. Reinstall PMS 1.31.3.6999

  2. Do not upgrade until after GeminiLake is fixed.

BE ADVISED - i965 drivers have been removed unless the CPU requires it. (It was an Engineering decision. i965 usage is no longer optional)

If you wish you manually install system-level i965 drivers then that is your choice.

Should I be concerned that rolling my previously-able-to-hw-transcode QNAP (with a J4125) back to the 1.31.3.6999 official PMS Docker image didn’t fix the hardware transcoding issue?

I’m stuck with 1.32.5.7328 and synology won’t let me rollback. How do we fix transcoding, what options are there?

To rollback you need to uninstall the package.
Make sure you select uninstall only as this keeps all the settings in place.

Then download an older version from here:
(NOTE, make sure you choose the right DSM6 or DSM7 or it will give an error and fail to install)

And manually install as usual.
The latest one that worked for me (DS918+ w. Celeron J3455 and DSM7) was:
PlexMediaServer-1.32.0.6918-6f393eda1-x86_64_DSM7.spk

Once done it may take a few minutes to work on the database and then it’ll be good to go.

thank you, what is the right process to uninstall in synology that i won’t lose my database and existing settings?

When you start the uninstall request of the package you’re presented with a choice of what to keep. It’s pretty self evident which one is the one to use (the default selection afair)

There’s plenty of “are you sure” confirmations before it does anything :slight_smile:

@T_ChaY do you still experience problems with HW transcoding in the latest version of PMS or has the issue been fixed for you? I too run my PMS inside Docker on a DS1019+ but for me the problem resides. I had to go back to 1.32.1.6999 to fix it.

are things fixed in 1.32.5.7349?

Gemini Lake CPUs are not yet fixed.
We’re working on it.
We have to go through the code changes from the previous team line by line and figure out where it’s wrong.

I will provide PMS 1.32.1.6999 for those who wish it while this gets sorted out.

any progress?

No progress to report yet.

I am getting closer but don’t have anything tangible I can report.

any progress, theres a lot of people using this cpu.

Follow this thread for updates: PMS 1.32.6+ HW transcoding issues and corrections

TL;DR: For Gemini Lake (Celeron J4xxx), hardware accelerated transcoding working for SDR media in current beta, 1.32.6.7521. Tone mapping still not working.

EDIT: If you were referring to Apollo Lake (Celeron J3xxx), it was fixed in 1.32.5.7349. You can run current public, 1.32.5.7516, or beta releases.

New versions still don’t work for me (Celeron J3xxx)
Added to your linked post as requested