I’ve had to dig into signal transport for 4k/UHD over the last week or so. Essentially I have a test-signal generator (SRI Visualizer TG100) running at a maximum raster of 4096×2160 at a maximum of 25 progressive frames/sec (and only 4:2:2 colour sampling; Y, Cr, Cb) with a 6G single-link output (so really 4 x 1.5G links) and HDMI 1.4 (so the same raster as the SDi). The monitors are the 24″ and 30″ Canon IPS 4k native monitors.
The Canon monitors will take quad-link HD/SDi and (in the case of the 24″) HDMI. So, feeding the SRI single-link into a Blackmagic 4k multiplex (to produce quad-link) and then into the Canon produces four quads in the wrong colour-space!
For an insight into what the multiplex is doing it’s worth looking at the two standards for quad-link SDi. Put aside if it’s 4 x 1.5G or 4 x 3G (that allows an increase to 50 or 60P OR 4:4:4 colour). But, in this case we’re de-mux’ing a 6G to 4 x 1.5G signals.
The original 4k-over-four-BNCs standard
The more recent standard; each link looks like an HD version
Clearly the converter is producing 2SI but the Canon expects SD quad-link. In fact the guys at Canon tell me they have a firmware update early in 2016 to address this. The other error is that the Canon has mistaken the 4:2:2 video as RGB – but it has at least got the raster correct.
So, what to do? Well, by throwing in another converter and taking the HDMI out of the SRI means the BM mux will get an older SD quad-link input;
This produced what we need; clearly HDMI has not concept of mutliplexed pixels and so we’re now fully in SD quad-link;
tugging BNC no.4 shows the monitor is now in quad mode
The monitor gets it all right
The other thing that you have to pay attention to in “True 4k” displays (for the film snobs!) is that feeding 3840×2160 signal into a 4096×2160 monitor and letting the monitor scale-up to fill the line risks killing your resolution;
The aliasing should only the present in the top-most block, the other alias frequencies you can see here are due to my iPhone’s camera!
Some very strange aliasing when a 3840-pixel line is mapped to 4096 pixels
As ever with display devices, pixel-pixel (native resolution) is always preferred