02-21-2018, 04:44 PM
(02-21-2018, 01:01 PM)spawnflagger Wrote: (it's also possible that the Rock64 implementation introduced some clock limit that's not inherent to the chip, but rather some PCB capacitance, etc., that limits it)This is the Question. Pine64 should clarify this problem. There is only few "marketing" public documents.
(02-21-2018, 01:01 PM)spawnflagger Wrote: also a clarification: I'm only referring to the 4K refresh rate capability of the graphics chip, not the CPU/GPU/VPU frame rate decoding capability with any codec. It's impressive that it can decode 4K content at or near 60fps, but pointless to do so at any frame rate greater than the refresh rate. There's still a lot of movie content that is 24fps, so it's useful to set display resolution of 3840x2160@24Hz in those cases, but that resolution spec was part of HDMI 1.4, back in 2009...Not exactly true. Now you can decode and display in 60FPS (of cause in YUV420, TMDS Clk: 297MHz) and after resolving some problems HDR/HLG (of cause in YUV420-10bit, TMDS Clk: 371MHz). Rock64 is capable of sending "frame metadata" to support static HDR (HDMI2.0a) and HLG (HDMI2.0b).
I left this community in Aug 2019 due to PINE64 refusal to produce/deliver ROCK64-1G version 3 after more than one year of changing statuses to "planning", "evaluating", "releasing", "availability", "estimated availability" and finally "no schedule" . ROCK64 is dead platform without any advantage. Buy Raspberry PI 4 !