Curiosity got the better of me, so I just took delivery of one of these - many thanks to Futeko for their usual stirling service!
So this is a really odd little box.
First the good news - the Dune Shell is pretty much implemented as the 4K Pro and can be skinned as comprehensively as other Dunes.
It also fully supports yaDis - not that you'd expect issues with either of these, but thought it was worth mentioning, because beyond that, it's a bit of a s*** show.
Firstly, despite Dune's claims further up this thread, this box does not (yet?) support 23.976fps.
If you set either "1080p 23.976Hz" or "4K 2160p 23.976Hz" in video settings, the box refuses to push out anything other than 24fps as reported by an HDfury Vertex.
Even setting the gui to say 4K60 with auto framerate set to "ALL" still results in a framerate of 24fps with 23.976fps material.
This results in a frame repeat every 40s or so.
Similarly, 29.970fps material is output at 30fps.
Secondly, and probably more importantly, the only way to convince the box to output HDR is to set it to convert SDR to HDR, so it's full time HDR or nothing!!
If you set HDR to "auto" as most will want to, when playing HDR material it will output mostly zeros in the SEI message (as seen on the Vertex), so staying in SDR obviously resulting in the low contrast washed out presentation you get when showing HDR on an SDR monitor.
This is going to confuse a lot of people, particularly if you don't have an HDFury device to figure out what's actually going on.
So if you set HDR to "Convert SDR to HDR" this will output a valid SEI and switch to HDR, but obviously it will "convert" 709 SDR to 2020 HDR which is not really desirable.
(HDR to SDR is pretty awful, so not really worth mentioning).
And as for HDR metadata - wow!
Let's say that sometimes it works, mostly it doesn't, but it's hellishly confusing.
Sometimes it will show MDL, MaxCLL and MaxFALL as zero, sometimes it will display correctly.
Sometimes it will show zero for Movie "A" and then present the correct values for Movie "A" when playing Movie "B" and occasionally, but not always, carrying those old values over into the GUI after Movie "B" has stopped - Absolutely bonkers!!
Chroma banding, although still marginally present, is improved over previous models in 4K 12-bit 422 indicating that maybe the 8-bit pipeline in that mode has been fixed by Realtek, however the most desirable mode is 4K 10-bit 444 ...But... this mode is not recognised by the Vertex - something I've only ever seen before on a Zidoo X9S.
There also seem to be some network issues - if you leave the box using DHCP then it seems to get itself very confused over network availability - setting a static IP seems to fix that, and that's what I would always do, but I know some will just stick with DHCP.
This is on the latest firmware (although shipping firmware was the same) and I know it's early days for firmware yet, but come on, it's not like Dune haven't been developing on the Realtek platform for long.
That said, hopefully at least some of these issues will get fixed in upcoming releases, but I'm very dubious over the framerate and HDR metadata given this is ostensibly the same box as the Pro 4K just with a lesser GPU and fewer IO.
If it worked, it'd be a nice little box.
One thing I forgot to mention - in
's post above, the reply he got from Dune about frame rate and meta data reads:
"We've tested RealBox 4K using HDFury in 4Kp23.976 HDR 4:2:0 10-bit and 12-bit HDMI video modes when playing 4Kp23.976 HDR 10-bit content and here are the results:
1) HDFury indicates that MaxCLL/MaxFALL are passed
2) HDFury indicates that frame rate is 23.973"
Well they can't possibly have "tested RealBox 4K using HDFury in 4Kp23.976 HDR 4:2:0 10-bit and 12-bit HDMI video modes"
because there is no legal HDMI mode for 4:2:0 at 23.976fps!