Originally Posted by Mike Garrett
Has been reported to JVC.
Originally Posted by SirMaster
What about RGB 24 10bit 444?
Why do we need 12bit?
Because some players and drivers (for example nVidia) don't offer 10bits. It's 8bits or 12bits. Also 10bits is only an option for RGB. YCC is always 12bits, you can't transport it over HDMI any other way.
Originally Posted by RapalloAV
Did they say anything Mike, Im sure you have a black like i have...
As discussed, I've reported the issue again yesterday evening in detail (with screenshots showing the issue) to Mike who has forwarded to JVC. I also reported detailed timecodes to illustrate the blooming of highlights with the DI in HDR (very visible with the iris fully open). I have copied my report to
so they can try to reproduce and report independently to JVC, as their voice might be heard better than ours.
I think the main reason why people are not complaining is because you can't see there is an issue if you keep colorspace on Auto, which most people do. You only see the chroma issue if you use video levels (forcing ycc422 means you have to use PC levels) or if you check chroma quality with a pattern. If you use PC levels, which most HTPC users/gamers do, you won't see the issue either because the levels will be correct even if the JVC forces YCC422 when it shouldn't. If your source dither properly (madVR does), there is no added banding when selecting 8bits dithering even with 10bits content. It's not ideal as it can add a bit of noise near black, but it's perfectly usable as a temporary workaround.
I think this colorspace issue should be solved, and I hope it will be solved, but using RGB 8bits or YCC422 in the meantime is a good workaround. That way there is no weird chroma downscaling/upsclaing happening behind the source's back. You either keep the source's original chroma 444 upscaling (RGB 8bits) or you ask the source to do half the upscaling (420 to 422) and let the JVC do the second half (422 to 444).
I have my HTPC with madVR set to RGB 8bits 444 (to make the most of madVR's NGU chroma upscaling) and the Oppo and UB900 set to YCC422 12bits. With UHD content, there is no significant visible downside that way.
To be fair, this was an issue on older models as well, at least it was there on my rs500. I just never took the time to figure out why my levels were messed up when using RGB 12bits in the HTPC and I thought it was a driver issue, until I did a deep dive with the rs2000 and found out. I couldn't really test 8bits with the RS500 due to the magenta bug, which is gone on the new models, so I had no choice but use 12bits