As you already imagined, this depends on the workload on the device. IO bound operations should be much improved, as we now use eMMC storage. This provides really improved random write and read speed to the internal storage.
Video decoding capabilities (VPU) are also very improved: hence 4K playback and support for 10-bit HEVC and VP9.
Graphics performance is improved as well as CPU performance and tests (3DMark for example) show about a 1.5x improvement. Synthetic benchmarks rarely reflect real world performance, so we don’t use these numbers to represent the product. Simply put, you should find it fast, and we are exploring bringing a minimal desktop environment to take advantage of that.
Vero 4K will decode 4:2:0, 4:4:4 and 4:2:2.
Output (and whether it looks good) depends on your TV’s capabilities.
echo 2160p24hz420 > /sys/class/display/mode
could be used to adjust the video mode temporarily. It can be made persistent with a simple command line change, but we found that chroma doesn’t always look good depending on the display. We’ll try and pick sane defaults, but of course things will be tunable. It may not be possible for us to find a one-size-fits-all for this.
Atmos and DTS:X work. We know people have been after this for a while. No Dolby Vision.
HDR is supported, but may not always look good on your TV.
Vero 4K will do 4K60 decoding. You will need an HDMI 2.0 TV to get that output, as HDMI 1.4 is capped at 4K30. The device features a Quad Core A53 running at 1.6Ghz and a 5-core Mali-450MP GPU.
Sam