Small user-interface text can also look better at 4:4:4.
Done way too much side by side and see no difference between 4:2:2 and 4:4:4.
4:2:0 definitely has an impact though.
We only have a 55 inch TV now though so a bigger TV might cause issues.
4:4:4 for us at least causes too many implications with other more important settings on limited bandwidth.
We use our HTPC as our main PC and have no issues with small text in documents etc at a 2.5 m viewing distance.
Edit - different story though on a monitor for gaming close up. We donāt game.
I looked in my AMD settings and canāt find a way to do that.
Content will automatically change from 60 p to 24 p but canāt see how to set manual settings for bit rate etc on the fly ?
I am an absolute novice with this stuff though. It is funny that I left Kodi years back for Plex because Kodi required too much tinkering and maintenance and Iām getting back to those days with Plex HTPC now 
I agree it isnāt an important difference within Plex or other 10-foot interfaces.
It can be significant when using a TV as a general-purpose monitor displaying text.
(Iām not advocating for either setting.)
1 Like
Yep, have read the RTings info and honestly, never see those issues on our 55 inch TV. At any distance.
Mind you, I also donāt use RTings settings for our display as they look hideous (as others have mentioned on AVS etc).
At 4:2:2 none of those issues are present. Either our panel is doing good things or the system is. Iām old and my eyes arenāt the best but Iāve annoyed the kids when they come over too many times to pick up differences and they canāt. The panel has been professionally calibrated, a few times over the years.
As I said, we use our 55 inch as a general purpose monitor - it is connected to our main computer and does server, player and PC duties.
Most would say a huge compromise but it works for us. The only issue we have is the limitation of HDMI 2b. Iāve used DP from the 3 available with the RX580X as well but that has its issues - we run audio via the AVR and hate the ghost monitor setup we have to employ. (note that our panel lists both 4:4:4 and 4:2:2 as UHD)
Some will have seen the issues we have had with media luminance, stutter, splash screen etc. We still have some compromises but at least the media plays.
As your link says
4:2:0 is almost lossless visually, which is why it can be found used in Blu-ray discs and a lot of modern video cameras. There is virtually no advantage to using 4:4:4 for consuming video content.
Edit - sorry Mitzsch, have derailed your thread enough,
1 Like
Okay, well at the time of writing, I thought that there is one available because of the new KODI 20 release having such a feature. Shame on me, I have not read carefully and found that it has nothing to do with the outputā¦ KODI 20 has only introduced a 10Bit capable swap chain, no 10bit forced outputā¦ Sorry!
Ah! RGB! Then IĀ“m also able to get this working with RGB for 4k60, I thought your normal resolution is YCbCr 8Bit, 4K60. RGB is the fallback format for Nvidia GPUs when the resolution set in the Nvidia control panel is not compatible with the display/bandwidth. So setting 23p to 10/12bit YCbCr and then back to a 60p mode gives you the default 8bit RGB. For AMD its YCbCr (at least with Polaris and Vega)
I have also seen conditions where RGB would show inferior visual results (although it shouldnātā¦)
Thatās why I always prefer YCbCr. 4:4:4 also for compatibility reasons, I had rare conditions where setting 4:2:2 or 4:2:0 caused the screen to lose the signalā¦
I guess having RGB (with crushed blacks) for the GUI and perfect 23p/10Bit/YCbCr for content is an okay-ish compromise until we have full HDMI 2.1. (at least for me)
Because there is no setting for that. Not for AMD nor for Nvidia. As described above Nvidia falls back to RGB 8Bit if the bandwidth would exceed the connection, AMD to YCbCr 8Bit.
@gbooker02
Also, thanks for fixing the Vulkan paused stuck in HDR bug with the new version 1.32.2!
May I ask what you have done?
Just un-pause: When it tells MPV to load the SDR file, it also sets pause=no.
I would be interested, if there are any plans on supporting HDR10+ in Plex HTPC?
1 Like
Windows and mpv need to support it first, then it should also work with Plex HTPC. I have no idea if or when they (ms/mpv-devs) plan to support HDR10+.
1 Like
Well, there is actually news on the HDR10+ side. MPV just got initial support for HDR10+ mapping yesterday (no passthrough I guess)
I now tried the power max mode in a long run and now I only get 1 dropped frame every 50-60 minutes, which equals madVR behavior and calculation. I will try to get my 23p mode closer to real 23p with madVR and maybe so I can also achieve perfect playback (madVR Custom Mode Tutorial)
4 Likes
Just want to add my playback experience with an Intel ARC A770 16Gb. (Driver: 31.0.101.4146- windows 10 - resizableBAR enabled). The gpu was connected through a DP to HDMI adapter (club3d cec-1080) to the AVR/TV. The HDMI port (also just converted from an internal DP port with a Realtek chip) was not strong enough to output an image when connected to the AVR first.
When it comes to 4K HDR playback itās truly perfect, every HDR metadata value is transmitted correctly to the TVā¦ The TV is switched correctly into HDR mode (unlike madVR) and also back to SDR. I have also not encountered any dropped frames during playback. (madVR measurement showed a dropped frame every 11-14h)
The only problem I have run into is a problem with changing the active signal resolution. Select a 1080p mode, just the desktop gets rescaled to 1080p, the active signal resolution is still the edid recommended one (2160p) in my case. I will let Intel knowā¦
1 Like
For everyone interested here is the corresponding github issue. [output] active signal resolution does not change, when new lower res mode is selected Ā· Issue #259 Ā· IGCIT/Intel-GPU-Community-Issue-Tracker-IGCIT Ā· GitHub
Intel is working on itā¦
++ also just want to bump this post - keep it from being closed.
Still rocking an RTX3050 Pc with HDR passthrough enabled without any problemsā¦
1 Like
++bump
The aforementioned Intel ARC 770 output bug is now supposed to be fixed. I will test this in a week or twoā¦
1 Like
++ bump
For anyone interested, the Intel ARC output bug is unfortunately not fixed. I already informed Intel about that in the linked GitHub issueā¦ Letās see if they fix itā¦
As for Plex HTPC and HDR playback on my RTX3050 system, Itās working like a charm!
1 Like
Now I did discover something new. I watched a very bright HDR movie file and had it paused. There I noticed the ātimeline - player status - pause overlayā is one pixel off on the left. In dark movies, itās not that visible but in this case, it was very noticeable. A very bright line ranging from top to bottom black bar of the movie. I have made a photo - see below. Itās only on the left side of the screen. At first, I thought that those are all ādead pixelsā or some TV weirdness of some sort. (pixel shift - oled wear controlā¦) but no, the TV does nothing wrongā¦ The Overlay seems to be exactly one pixel off. This is only visible with the HDR passthrough setting turned on - with it turned off the UI is rendered differently and the issue is not visible.
Is it supposed to be like that? @gbooker02
This is likely a byproduct of the UI rendered at half resolution and scaling it up in an MPV overlay. Or it could be an issue with Qt in capturing one of its windows into an image.
Hm, okay, thanks for the response. Do you think this might be fixable?
Possibly, though itās not terribly high on the priority list due to it being an experimental feature.
Also, are you seeing it off only on the left side and not any other sides?
1 Like
sorry for the delayed reply, I have checked it again and I could only see the āone-pixel-off-lineā on the left side.
Hi there, Iām not sure though Iāve red the whole topic. This is only to get real HDR on Windows with Plex HTPC right? Nothing about getting Dolby Vision?
I tested it with my set-up (Intel Core i5 12400k as GPU to decode), no matter if D3D11 or Vulkan, I get a black screen.
