[mirror88]

Thank you for explaining this. I wasn't aware the refresh rate issue only affects 2160p in 4:4:4 mode, or that it was different depending on deep color settings. I don't have any native 2160p motion bars for testing, but I guess I can just upscale my 1080p motion bars. I'll check tonight and see if I can spot the stutter.

So then the pop-up says it is correctly switching to 2160p/23.976 or 2160p/24.000, but in reality it's actually outputting 23.982/23.988? Yikes, if that's the case, are we sure it's sending the proper framerates for all the other framerates at different resolutions? How, for example, would I know it's correctly sending out 59.940 or 60.000, for example, or that it's converting 25.000/50.000 to 60.000 properly with various settings selected? Doesn't this call into question all other refresh rates too? What could cause it to have an issue specifically with 23.976 but only at 2160p with deep color enabled?

It sounds like this is an issue that they definitely need to fix ASAP. 

Until I checked for it specifically, I wasn't also aware that it affected only 2160p. You should be OK to use your 1080p test pattern and output it at 2160p. You will have to disable the adjust resolution option in settings.

23.982 and 23.988 are the actual refresh rates for 2160p 23.976fps content when the output is set to 12 or 10-bit YCbCr 4:4:4 resp. Other frame rates are not affected. 24.000/25.000/30.000/50.000/60.000 are perfect. 29.970/59.940 have minor offsets but I wouldn't worry about it.

It is likely to be some minor error (? typo) in the HDMI transmitter code that is causing this. Zidoo should be able to fix it quickly. 

 Thanks for your feedback. We solved 23.976 refresh rate offsets issue
It will be include the next firmware.
Also solved the "COCO" audio drops issue and "Thor: Ragnarok" 1:55 exit playback issue.