kayjay010101

I've only posted this here, so apart from duckstin reporting the same issue (and then retracting it), I haven't heard anything. Saw users on Reddit reporting the issue as part of the newest Plex update the same day I posted my comment here, so I assume we just have to wait for Plex to fix it themselves in the next update. But I haven't actively kept up with how that's going - as long as it's working for me I'm in no hurry to update. They might have already fixed it, I don't know. I see some Reddit users reporting only 1.43.0 is "transcode safe" and all 1.43.1 updates are broken, but rolling back from 1.43.1.10611 to 1.43.1.10540 fixed transcoding for me ¯\_(ツ)_/¯ I think there's a lot of noise coming from some users not realizing the issue isn't affecting all hardware equally, from what I've seen only certain Intel GPUs are confirmed as having their transcoding broken by the update. But I don't know how widespread the issue is or anything, like mentioned, I just rolled back and haven't kept up with it No idea about your update issue, seems like an issue with your unraid installation perhaps?

HW transcoding seems to be broken on the newest release of Plex (1.43.1.10611), at least for intel GPUs Rolling back to binhex/arch-plexpass:1.43.1.10540-1-01 works fine

Fantastic work, really nice of you to do this for the community! Could you add the HP ProLiant DL380 G7? There's the 8 bay SFF model, a 16 port bay model (which I have) and a 6 bay LFF model

128GB DDR4 2400MHz ECC. Got it for free from work, apparently our datacenter has a massive DDR4 surplus and actually a DDR3 deficit. So they just have a bunch of DDR4 ECC lying around.

This seems to be a common problem now, multiple people have this issue lately. I've switched to WireGuard and it's 1000x easier to setup and use

I keep getting "We're having a problem transferring data. Please check your internet connection just in case and try again" every time I try to download something on battle.net... I don't get this when not using lancache.. any ideas what the problem could be? EDIT: It was my VPN. Disabled my proxy and instantly it went back to working!

If you do manage to completely get it to work as a cache drive, I'd be forever thankful if you could make a guide on how others can do so as I'd really like to make use of my ioDrive 2.

Have the exact same issue after watching spaceinvaderone's video. None of the commands posted in the last 2 or 3 pages have had any effect