i’ve pinged the issue internally to see if we can get some 
on it.
1 Like
I just want to say for the record that I ended up ponying up the cash to get a Quadro P2000 as I just couldn’t deal with this issue anymore. It seemed to be the best card to handle this sort of function plus I didn’t have to run extra cabling to power the card. I’m less than thrilled having to do it but I had to do something and sticking with the 1.17 version was starting to cause random connectivity issues where my devices would randomly stop playing videos… Probably from the constant downgrade/upgrading of PMS.
The best resolution i found was to switch to Emby, no problems with QSV on my HD530 
1 Like
@elan any update when you pinged the engineers?
Also, are you guys still hiring remote SWE interns?
Getting pretty obvious that they dont care about fixing this.
Going on at least 7 months with this issue. Would be great to get some dev focus time on this Plex team!
With options like Jellyfin getting more and more mature, it’s becoming difficult to justify these kind of glaring core feature failures.
I’ve been using Plex for years and have loved it. But over the last I’d say, 3 years, it’s becoming more and more clear the focus has shifted to securing reoccurring cash flow. I understand this is a part of growing any company, but when you abandon core features like this it really tarnishes your reputation and brand.
Fix the core platform bugs BEFORE adding more features and pushing these out. E.g. I’d rather rely on 3rd party apps to do things like monitor my Plex server for now while you let the dev team focus on fixing issues. Then when they’re squashed you can turn focus to other fun new features.
1 Like
Hey @elan another week gone by. Any update on the timeline for this to get corrected?
Gotta imagine your dev team has a kanban board or ticket system around somewhere showing who is assigned to this and when it’s supposed to be completed for release.
2 Likes
Still no fix in the latest server beta. What a joke.
@elan any update? Was it finally addressed? Is the cause somehow clear? Can we trust that this issue is now in the priority lane?
@elan I’d also like to hear an update. I’ve been patiently following this thread for a while now after recently purchasing the Plex Pass and a new Intel i5 9th gen system. To experience this issue (which wasn’t on my radar initially and only came to light when transcoding) is a frustration.
4 Likes
Sorry guys, I don’t have any specific updates at the moment. I’ve pinged the appropriate people to see what the deal is and why we haven’t been able to schedule this one.
(And yes, we do still hire remote engineers/interns, we’re fully remote 
)
It took 2 months to tell us that?
1 Like
I forgot to cancel my renewal last month, and was charged for another year. I ended up switching to emby. Happy to pay them for a yearly sub and have none of the issues I’ve experienced with Plex over the years. Good luck everyone.
2 Likes
I just loaded Jellyfin along side Plex. Their HW transcoding with Intel Quick Sync has worked perfectly.
Did a direct comp from the same source files. Where Plex looked like a blocky terrible mess Jellyfin looked exactly like it was supposed to (both doing HW transcoding from same machine).
1 Like
I had some meetings about this yesterday and today, and managed to get the priority escalated. An engineer has started looking at the issue, and hopefully we’ll get it resolved before long.
I apologize personally for how long this has taken, and I appreciate all the pings I’ve gotten on this thread to raise awareness internally.
7 Likes
Thank you for @elan for the update. Appreciated, look forward to hopefully seeing a resolution soon.
2 Likes
Is this issue supposedly specific to Windows? I ask because I have noticed that transcoding output of 1080p HEVC files down to 720P when using hardware transcoding on my Synology DS920+ is not great quality with some clear colour bleeding issues. If i disable hardware transcoding the output is considerably better (but obviously the J4125 CPU struggles with this). Interestingly transcoding but to 1080p also seems fine.
This topic is about harware transcoding via GPU specifically with integrated intel graphic chips. So your issue is something different but might be expected behavior.
@elan Thank you for the update, appreciated!
Glad this is finally getting some eyes.
The timing of HW-transcoding quality issues between 1.17 vs. 1.18+ is coincidental with added support of zero-copy hardware transcoding. My gut feeling is it’s still related moving to zero-copy, since it was in “Beta” during the 1.17 days, but I could be entirely wrong.
1 Like
Thank you @elan
