Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Intel QSV transcoding broken in ls211 #392

Closed
1 task done
x5nder opened this issue Apr 4, 2024 · 10 comments
Closed
1 task done

[BUG] Intel QSV transcoding broken in ls211 #392

x5nder opened this issue Apr 4, 2024 · 10 comments

Comments

@x5nder
Copy link

x5nder commented Apr 4, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

When upgrading from ls210 to ls211 on Unraid, hardware transcoding with Intel QSV is no longer working. Plex throws an error. Downgrading to ls210 immediately fixes the issue. Also reported here: https://forums.unraid.net/topic/130080-plex-hardware-transcoding-suddenly-not-working-transcoder-crashing/

Expected Behavior

No response

Steps To Reproduce

Start Plex. Start playing a 4K file. Open video settings, manually select 1080p quality. Up to ls210: file gets transcoded and plays in lower quality. On ls211: Plex throws an error.

Environment

- OS: Unraid 6.12.8
- How docker service was installed: Unraid Community Apps

CPU architecture

x86-64

Docker creation

(default Unraid settings)

Container logs

-
Copy link

github-actions bot commented Apr 4, 2024

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

@homerr
Copy link
Member

homerr commented Apr 10, 2024

Is there nothing being logged by the container at all?

@HannesJo0139
Copy link

HannesJo0139 commented Apr 16, 2024

Edit - It was not related to this one.

@Rolodo
Copy link

Rolodo commented Apr 19, 2024

Same for me some files don't transcode anymore.
I can provide stuff if you let me know what and how to get them.

Thanks

@LinuxServer-CI
Copy link
Contributor

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

@factorywiz
Copy link

factorywiz commented Jun 21, 2024

I have had a very similar issue with two different model Synology NAS units using QSV (one Intel Celeron J3455 and one J4125). Hardware accelerated transcoding works for 1080p source files but not 4K source files. 4K source files go into software transcoding immediately, the CPU maxes out, etc. If I downgrade my container to 1.40.2.8395-c67dce28e-ls218 or below - 4K files will transcode with the (hw) tag again. Only 4K files seem to be affected.

@Elwyr
Copy link

Elwyr commented Jun 29, 2024

I have had a very similar issue with two different model Synology NAS units using QSV (one Intel Celeron J3455 and one J4125). Hardware accelerated transcoding works for 1080p source files but not 4K source files. 4K source files go into software transcoding immediately, the CPU maxes out, etc. If I downgrade my container to 1.40.2.8395-c67dce28e-ls218 or below - 4K files will transcode with the (hw) tag again. Only 4K files seem to be affected.

Same experience here on a Synology 920+, downgrading to ls218 works for now, thanks.

@QuigonJohnn
Copy link

QuigonJohnn commented Jun 30, 2024

I have had a very similar issue with two different model Synology NAS units using QSV (one Intel Celeron J3455 and one J4125). Hardware accelerated transcoding works for 1080p source files but not 4K source files. 4K source files go into software transcoding immediately, the CPU maxes out, etc. If I downgrade my container to 1.40.2.8395-c67dce28e-ls218 or below - 4K files will transcode with the (hw) tag again. Only 4K files seem to be affected.

Same experience here on a Synology 920+, downgrading to ls218 works for now, thanks.

I'm having the same issue with 4K media on the 920+, but downgrading the container doesn't solve the problem for me.

Edit: Setting my 'VERSION' variable to 'docker' does fix the problem after I downgrade the container.
This installs Plex Version 1.40.2.8395, which is not the latest public version. The logs show that it couldn't pull a different version:

Upgrade attempt failed, this could be because either plex update site is down, local network issues, or you were trying to get a version that simply doesn't exist, check over the VERSION variable thoroughly & correct it or try again later

Unfortunately this means I can't use the latest docker image with the older 1.40.2.8395 version of Plex for testing, as I get the same error. I suspect this is a bug with recent versions of Plex itself, as that has happened before.

@factorywiz
Copy link

factorywiz commented Jul 1, 2024

I believe you are correct @QuigonJohnn . After making this comment I found that there was actually mention of a PLEX issue breaking it for certain generations of CPU/iGPU. Here is the link.

https://forums.plex.tv/t/hdr-tone-mapping-not-compatible-with-hw-accelerated-transcoding-anymore-ds920/880627

Multiple mentions of it affecting Apollo Lake and Gemini Lake iGPUs. Appears the container is fine except for the underlying Plex bug.

@LinuxServer-CI
Copy link
Contributor

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

@LinuxServer-CI LinuxServer-CI closed this as not planned Won't fix, can't repro, duplicate, stale Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

8 participants