#Proseries error code 1618 update

The following assume the input and output frame rates are the same. Patrick did some video delay measurements with different options.

#Proseries error code 1618 update

if Kris corrects my ass here, I'll update the post! For me (square meters for my screen is approx 4.7), this calculated lumens to 2608, so quite close to the spreadsheet value. Lumens = Nits x Screen Area (in square meters) * Pi (3.14159). The measured peak lumens was 2634.įrom this site, there is the following calculation:

To check the max nit value was correct (besides Kris confirming the values!) I used a Lux to Lumen spreadsheet to input my screen size parameters, throw distance, and center screen LUX measurement. 159 x2 gave the the low ratio target of 317, so ratio 28 was closest (311) (all math approximate here) Multiplied by 0.9 screen gain, the NIT value at center screen was 159.ġ59 圆 gave me 953 for the MAX NIT value.

Multiplied actual NIT value x2 for low ratio/'effective NIT' setting in the DTM menuSo my measured LUX value was 555 or so. Multiplied actual NIT value 圆 for MAX NITS in the CMS HDR setting Multiplied this by SCREEN GAIN for actual NIT value Converted LUX to nits (LUX/3.1459) - (used the inverse of this calculation: )

Measured LUX using a AEMC CA813 light meter with a 100% white Radiance Test pattern, making sure I was in the projector picture mode I use for HDR content.