Originally Posted by bathes2051
I tried that with a UB820, f/w 2.07.
If I force the 820 to output 4:2:2 with 12bits preferred, the JVC does not report 12bits.
If I leave the 820 at 4:4:4(Auto), it does.
The Panasonic description says that this setting can still output 4:2:2 to favor 12bits, hopefully this is what’s happening.
So it seems that Auto colorspace everywhere is the best choice with 2.07 (note that I hadn't tried with the previous f/w).
Yes with the Panasonic (at least that's the way my UB900 works) you can select priority to bit depth or priority to chroma. As long as it sends 422 12bits or RGB/444 8bits, you're fine. What you want to avoid (if at all possible) is RGB 12bits or 444 12bits.
Just to clarify, the colospace setting in the JVC has no effect in V2.07 with 12bits content. You can select anything, it will always force YCC422 internally when it detects a 12bits input. So the only control you have to avoid a chroma downconversion is by making sure that the source sends 8bits 4:4:4 or 12bits 422. Any 12bits RGB or YCC444 content will be downconverted to YCC422.
Selecting Colorspace to Auto in the JVC is recommended with any version of the software:
With pre-2.07 versions, setting colorsapce to auto in the JVC "works" with all inputs (RGB and YCC 422 or 444). However, it downconverts internally RGB and YCC444 to YCC422 when it detects 12bits content. Selecting any other option than auto when you're not sending YCC422 produces a garbled picture and makes it obvious that the JVC is doing a chroma down-conversion behind the source's back. So manually selecting the format sent by your source is an obvious way to see if the content is molested, but auto is the only "safe" option with previous f/w. Unless you're sending YCC422, all the other options will produce a garbled picture with 12bits content.
With V2.07, setting colorspace to auto in the JVC, like the other options, still forces YCC 422 internally with 12bits content, but you can't see as easily when the JVC does a chroma down-conversion behind the source's back when anything but YCC 422 is sent. If you manually select YCC444 or RGB, it has no effect. The other options are simply disabled and have the same behaviour as auto in the previous f/w. In other words, you can't force YCC444 or RGB in 12bits anymore, so you don't get the tell-tale garbled content. There is zero change compared to using auto with previous versions. But now you can use any option for colorspace in the JVC, it doesn't make any difference with 12bits content. Auto = RGB = YCC 444 = YCC422, all are down-converted to YCC422 (well, except YCC422 which stays as it is).
Again, this is NOT a big problem, it's only important to know this so that you select the best setting in the source, especially for gaming/desktop content which should be using 8bits RGB for best results.
With video content, it shouldn't really make much of a difference 99% of the time with actual content.