Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Intel 12th generation Alder Lake / Hybrid CPU

Featured Replies

36 minutes ago, jack0w said:

I'm not sure if all the steps I took are totally needed, I just figured if it ain't broke don't try and fix it!

 

Also to clarify settings in Plex Transcoder section, I have -

 

"Enable HDR tone mapping" disabled

 

"Use hardware acceleration when available" enabled

 

"Use hardware-accelerated video encoding" enabled

 

With those selected it uses HW.

 

If I enable HDR tone mapping as well, everything is done by the CPU.

 

HDR tone mapping doesn't work on my synology either, if enabled everything is done by the CPU. This seems more like a plex issue

  • Replies 759
  • Views 243.8k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • Hi first post here - not sure this is the best place but figure it might help someone else out as this thread is what saved me with my first Unraid build.     I just recently built my new Un

  • It means, "not supported" 👍

Posted Images

13 minutes ago, Nathan Fernandes said:

 

HDR tone mapping doesn't work on my synology either, if enabled everything is done by the CPU. This seems more like a plex issue

Agreed, at least it isn't crashing now though!

18 hours ago, jack0w said:

Just to share my experience.

 

Using an i3-12100 on a Z690 motherboard on unRAID 6.11.0-rc2

 

I now have HW transcoding working perfectly, the only thing that doesn't work is tone mapping.

 

With this -

 

echo "blacklist i915" > /boot/config/modprobe.d/i915.conf

 

Intel-GPU-TOP

 

GPU Statistics 

 

and /dev/dri in the official Plex docker container.

 

No other changes from default configuration.

 

I've played a 4K home movie in Plex, transcoded down to 720p without issues.

 

I've also converted it to a lower quality and downloaded it to a android phone with no problem either.

 

Both definitely using the GPU as can see low CPU usage and high GPU usage throughout.

 

I've had no crashes or errors in either my system or container logs. 

 

If I enable tonemapping, I don't get any errors or crashes, but instead of using the GPU it uses the CPU.

 

Hope this is useful to others!

The I3 is using uhd 730 from last gen so could be a difference. 
 

On 7/30/2022 at 5:48 PM, snazz said:

It sounds odd that you don't see any CPU activity while transcoding with only the HA setting enabled. I see CPU activity on my system in the same circumstances.

 

If not 100% sure this is accurate, but I assume transcoding video includes decoding of the original stream and encoding it in a different combination of format / bitrate / resolution, so i would expect to see CPU activity if the software encoding is occurring.

 

Maybe you're not actually transcoding in your testing? Is it direct streaming perhaps where only the container is different?

You are right it’s 5 % cpu usage with a 4K movie. As I tested with 1080p I just didn’t see the minimal usage. 

Probé Intel 12600 UnRAID (Version: 6.11.0-rc2 ), Docker Plex oficial (Versión 1.28.0.5999), tonos HDR deshabilitados, HW habilitado.
falla

Captura.JPG

plex.JPG

dev.JPG

intel GPU.JPG

Edited by xXx

Yeah @xXx I have everything installed just as you have there and I get the exact same errors.

1 hour ago, Titan84 said:

Yeah @xXx I have everything installed just as you have there and I get the exact same errors.

Disable "Use hardware-accelerated video encoding" and it should work. It's not ideal, but the best we can do for now.

 

Edit:

I did some transcode performance testing using a very high bitrate 4K HDR10 file with only "Use hardware acceleration when available" enabled. The results were disappointing. Using Tautulli to monitor the transcode speed, it was always under 1.0 (roughly .5 to .7) and the very limited stream buffer ran out after only a minute or two of playback. Performance was much better without HA enabled, even with only the 4 "E-cores" of my i5-12600k available to Plex....granted they were at 95% utilization due to the load. (The transcode speed was usually around 1.5 with this test file.) Obviously HDR tone mapping works with non-HA transcoding....so bottom-line recommendation: don't bother with enabling the HA setting until encoding is fixed (and probably wait for HDR tone mapping to be working for those of us that need it.)

Edited by snazz
Added info

If it was just to show the errors, it's all disabled and removed dev/dri

with Plex Docker 1.28.0.5999 from yesterday HA enabled and HA encoding enabled I don't get the Problems till now.

 

If I enable HDR Tone Mapping its over.

 

On the second play it dies again

 

3 13:59:20 Mycroft kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 12:1:8ed9fff2, in Plex Transcoder [14897] Aug 3 13:59:20 Mycroft kernel: i915 0000:00:02.0: [drm] Resetting rcs0 for stopped heartbeat on rcs0 Aug 3 13:59:20 Mycroft kernel: i915 0000:00:02.0: [drm] Plex Transcoder[14897] context reset due to GPU hang Aug 3 14:01:10 Mycroft kernel: i915 0000:00:02.0: [drm] Resetting vcs0 for preemption time out Aug 3 14:01:10 Mycroft kernel: i915 0000:00:02.0: [drm] *ERROR* vcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} Aug 3 14:01:10 Mycroft kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 12:4:28fffffd, in Plex Transcoder [19028] Aug 3 14:01:21 Mycroft kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 12:4:28fffffd, in Plex Transcoder [19028] Aug 3 14:01:21 Mycroft kernel: i915 0000:00:02.0: [drm] Resetting vcs0 for stopped heartbeat on vcs0 Aug 3 14:01:21 Mycroft kernel: i915 0000:00:02.0: [drm] *ERROR* vcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} Aug 3 14:01:21 Mycroft kernel: i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on vcs0 Aug 3 14:01:21 Mycroft kernel: i915 0000:00:02.0: [drm] *ERROR* vcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} Aug 3 14:01:21 Mycroft kernel: i915 0000:00:02.0: [drm] *ERROR* vcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} Aug 3 14:01:21 Mycroft kernel: i915 0000:00:02.0: [drm] *ERROR* vcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} Aug 3 14:01:21 Mycroft kernel: i915 0000:00:02.0: [drm] *ERROR* vcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} Aug 3 14:01:21 Mycroft kernel: i915 0000:00:02.0: [drm] *ERROR* vcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} Aug 3 14:01:21 Mycroft kernel: i915 0000:00:02.0: [drm] *ERROR* vcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} Aug 3 14:01:21 Mycroft kernel: i915 0000:00:02.0: [drm] *ERROR* vcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} Aug 3 14:01:21 Mycroft kernel: i915 0000:00:02.0: [drm] *ERROR* vcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} Aug 3 14:01:21 Mycroft kernel: i915 0000:00:02.0: [drm] *ERROR* vcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} Aug 3 14:01:22 Mycroft kernel: i915 0000:00:02.0: [drm] *ERROR* vcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} Aug 3 14:01:22 Mycroft kernel: i915 0000:00:02.0: [drm] *ERROR* vcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} Aug 3 14:01:22 Mycroft kernel: i915 0000:00:02.0: [drm] *ERROR* vcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} Aug 3 14:01:22 Mycroft kernel: i915 0000:00:02.0: [drm] *ERROR* Failed to reset chip Aug 3 14:01:22 Mycroft kernel: i915 0000:00:02.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by intel_gt_reset+0x26c/0x290 [i915] Aug 3 14:01:22 Mycroft kernel: [drm:__uc_sanitize [i915]] *ERROR* Failed to reset GuC, ret = -110 Aug 3 14:01:22 Mycroft kernel: i915 0000:00:02.0: [drm] *ERROR* vcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} Aug 3 14:01:22 Mycroft kernel: i915 0000:00:02.0: [drm] *ERROR* vcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} Aug 3 14:01:22 Mycroft kernel: i915 0000:00:02.0: [drm] *ERROR* vcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} Aug 3 14:01:22 Mycroft kernel: i915 0000:00:02.0: [drm] Plex Transcoder[19028] context reset due to GPU hang Aug 3 14:01:26 Mycroft kernel: Fence expiration time out i915-0000:00:02.0:Plex Transcoder[19028]:24f0! Aug 3 14:06:30 Mycroft kernel: PMS ReqHandler[17675]: segfault at 0 ip 0000000000000000 sp 000014705a37b1d8 error 14 Aug 3 14:06:30 Mycroft kernel: Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6. Aug 3 14:06:54 Mycroft kernel: PMS ReqHandler[31743]: segfault at 0 ip 0000000000000000 sp 000014d23a551f48 error 14 in iHD_drv_video.so[14d237853000+1bdf000] Aug 3 14:06:54 Mycroft kernel: Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.

Edited by feraay

We need a "sad" reaction.  I really appreciate everyone's efforts. 

 

Does anyone know if there is a corresponding post on the plex forums?

EDIT - Sorry to waste everyone's time, i looked just now and tried to transcode and plex server crashed. unraid itself has not crashed atleast but the only fix is a reboot of unraid itself. 

 

I have been following this thread for a couple months now. I am running a 15-12500 and a asus B660 motherboard, ddr4 ram. Ive been battling the same issues with unraid crashing that everyone else has with quicksync transcoding. With the recent version 6.11 RC2 and the latest plex update, i still had issues with HW transcoding causing crashes with plex container or unraid itelf. 

 

Two days ago I decided to turn on the monitor that i keep connected to my server, just for funsies. Since i rebooted and kept the monitor on (and it just sitting at the login prompt) i have had hw accel and hw decode and HDR tonemapping enabled without issues for two days now. Between me (local) and one remote user the server has  transcoded 4k and 1080p content 8 times now without any crash or issue. 

 

I cant account it 100% to the monitor plugged in, or if its just not my time to crash yet but I figured i would share this and see if anyone else can plug in a monitor or monitor dummy plug in to their server and see if they get any different results.

 

I'll update when this crashes (or if it does).  I did just notice on the GPU stats plugin mine is showing power usage even though the GPU is not being used right now. Last transcode was last night, without issues. but no crash. 

 

image.png.8ab11830e6b9f648b47bc023c8ae3f65.png

 

image.thumb.png.24cfe406bd13b6106402f5940321f381.png

Edited by philbar715

@philbar715 what's your plex version if you use it that is. I've tried this strategy with monitor plugged in but the issue still happens for me. What I've observed is that 2 days might be a false positive, you need to hit it badly, e.g. try a few transcodes at a time and it will happen faster. 

 

Thanks

2 hours ago, Alz7777 said:

@philbar715 what's your plex version if you use it that is. I've tried this strategy with monitor plugged in but the issue still happens for me. What I've observed is that 2 days might be a false positive, you need to hit it badly, e.g. try a few transcodes at a time and it will happen faster. 

 

Thanks

I am currently on plex 1.28.0.5999, linuxserver docker container. 

Woo! Getting closer!

 

New Plex version dropped this morning, version 1.28.1.6018 (beta update channel.) With this Plex version + Unraid 6.11.0-rc2, I'm now able to enable both "Use hardware acceleration when available" and "Use hardware-accelerated video encoding" without crashes or any errors in the Unraid or docker logs. CPU usage is minimal if not transcoding audio.

 

With everything set as above...If I enable HDR tone mapping, the CPU usage is pegged as if it's software transcoding and it can't keep up with transcoding a single 4K HDR10 stream (with 4 E cores only) for more than a few seconds at a time. This combo used to not work at all for me...had to disable HDR tone mapping for playback to even begin.

On 8/3/2022 at 6:44 PM, snazz said:

Woo! Getting closer!

 

New Plex version dropped this morning, version 1.28.1.6018 (beta update channel.) With this Plex version + Unraid 6.11.0-rc2, I'm now able to enable both "Use hardware acceleration when available" and "Use hardware-accelerated video encoding" without crashes or any errors in the Unraid or docker logs. CPU usage is minimal if not transcoding audio.

 

With everything set as above...If I enable HDR tone mapping, the CPU usage is pegged as if it's software transcoding and it can't keep up with transcoding a single 4K HDR10 stream (with 4 E cores only) for more than a few seconds at a time. This combo used to not work at all for me...had to disable HDR tone mapping for playback to even begin.

 

 

yes your are right. Working for me too. 

On 8/3/2022 at 12:44 PM, snazz said:

Woo! Getting closer!

 

New Plex version dropped this morning, version 1.28.1.6018 (beta update channel.) With this Plex version + Unraid 6.11.0-rc2, I'm now able to enable both "Use hardware acceleration when available" and "Use hardware-accelerated video encoding" without crashes or any errors in the Unraid or docker logs. CPU usage is minimal if not transcoding audio.

 

With everything set as above...If I enable HDR tone mapping, the CPU usage is pegged as if it's software transcoding and it can't keep up with transcoding a single 4K HDR10 stream (with 4 E cores only) for more than a few seconds at a time. This combo used to not work at all for me...had to disable HDR tone mapping for playback to even begin.

I switched mine to the beta channel, tested and I have the exact same experience.   My i5 hits about 50% usage when cpu transcoding HRD 4k.

It’s kind of funny


if you read in the Plex Forum they say since Build 1.28.1 HA is broken because of an Update of Intel IHD driver

Plex Forum

 

and for us 1.28.1 is better then 1.28.0 don’t get it.

I do have an 12700 and still are using the "blacklist" i used plex with hw transcoding for 4 days now without any problem or crashes at all (ofc without hdr tonemapping).

 

Now i started crashing with the following error:

Es ist ein Fehler beim Abspielen von „The Lost City - Das Geheimnis der verlorenen Stadt“ aufgetreten.

Fehlercode: s1002 (Netzwerk)

 

I have had this issue before and restored from a zfs snapshot and hw transcoding worked again.

This time no luck. I am not sure what caused the error. I did run "intel_gpu_top" before playing plex and i could hw transcode anymore. I am not sure if this was the reason it bricked...

 

Edit:
Reboot of unraid solved the issue. Lets see for how long.

Edited by Schmiddy

On 8/5/2022 at 8:06 AM, feraay said:

It’s kind of funny


if you read in the Plex Forum they say since Build 1.28.1 HA is broken because of an Update of Intel IHD driver

Plex Forum

 

and for us 1.28.1 is better then 1.28.0 don’t get it.

i'm on plex official container and updated to 1.28.1.6018.  I did have hw encoding (albeit crashing) on an earlier 1.27 version but now on 1.28.1.6018 and encoding is going straight to cpu. Havent changed anything else other than the update on my end.  Can still see renderd128  and card0 in the /dev/dri  folder.  i still have gputop installed and showing 1.1w on idle (which i don't quite get if it isn't doing anything?)   Any suggestions?

running the latest RC3 unraid and latest plex pass version of plex with HW transcoding/encoding/decoding enabled with HDR off it seems to transcode fine except when finished transcoding the gpu plugin still shows power draw. In my second screenshot is the value I have circled in green gpu power draw or CPU usage power draw? EDIT: I believe it is CPU power draw, i kicked off a cpu intensive task and watched the power jump.

 

No crashes yet, just noticed this odd behavior. 
 

image.png.57744ff45526c420b5fa9d0355867de3.png

image.thumb.png.9553360b14e6f4ad5a2bff2d5de971d3.png

Edited by philbar715

Yeah, my GPU stat's plugin also maintains the power draw bar at full after I have finished the transcode. I think it's the plugin though that just needs updating.

On 8/3/2022 at 12:44 PM, snazz said:

Woo! Getting closer!

 

New Plex version dropped this morning, version 1.28.1.6018 (beta update channel.) With this Plex version + Unraid 6.11.0-rc2, I'm now able to enable both "Use hardware acceleration when available" and "Use hardware-accelerated video encoding" without crashes or any errors in the Unraid or docker logs. CPU usage is minimal if not transcoding audio.

 

With everything set as above...If I enable HDR tone mapping, the CPU usage is pegged as if it's software transcoding and it can't keep up with transcoding a single 4K HDR10 stream (with 4 E cores only) for more than a few seconds at a time. This combo used to not work at all for me...had to disable HDR tone mapping for playback to even begin.

Are you using binhex-plexpass, or is there some way to switch the official container to beta?

4 minutes ago, flyize said:

Are you using binhex-plexpass, or is there some way to switch the official container to beta?

Just add the :plexpass tag to the container for the official one

on the linuxserver container there was already a version tag that I changed to 'latest'. honestly have not figured out how to add tags yet, unless tag=variable or label. 
image.thumb.png.90d6e376a2a2aa3063d1bcafa8e70375.png

 

1 hour ago, philbar715 said:

on the linuxserver container there was already a version tag that I changed to 'latest'. honestly have not figured out how to add tags yet, unless tag=variable or label. 
image.thumb.png.90d6e376a2a2aa3063d1bcafa8e70375.png

 

I can't get an image now, but there'll be a field "Repository" that has "plexinc/pms-docker" (or "plexinc/pms-docker:latest") you just add the tag to the end of that, so change it to "plexinc/pms-docker:plexpass"

Yay, I can also confirm that RC3 + Plexpass beta is working with the iGPU!!!

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.