Hello,

I'm very new to all of this and am looking to calibrate a DM series monitor from FSI which requires a back 1D + 3D workflow described in short in their calibration guide. The guide instructs you to bypass both LUTs in the monitor settings and then profile using a Grey Ramp RGB or Grey Ramp RGB Large and then create a LUT from that. Now I'm wondering if I should follow the ColourSpace 3D LUT guide on the pre-calibration steps (peak white/gamma/grey scale) and then proceed with the grey ramp?

Thank you!

Yes, it would be best to follow the pre-calibration info.

Steve

Thanks Steve.

I was just reading this post https://lightillusion.com/forums/tips-tricks-17/calibration-luts-order-adjustments-1214.html. If the monitor requires a back 1D + 3D LUT workflow, does it mean that the signal path is 3D -> 1D ? If so, would it be smarter to follow the normal 3D LUT workflow and generate individual 1D and 3D LUTs as described in the post?

1D + 3D is 1D first, and 3D after.
The order the LUT info is written in is based on the LUT order.
How you choose to generate the LUTs is entirely your choice, making sure you follow the info on 'LUT Order Issues'.

Steve

Thanks.

My thinking was that maybe taking the 1D LUT from a full focused patch set workflow uploaded as 1D + 3D might give better results than just taking it from Grey Ramp RGB Large. I can definitely try both and see.

One thing that has come up is that the monitor uses extended range natively. FSIs instructions are to use extended patch scale and to create the LUT with extended range + 100 nits max luma settings. The guides are for BoxIO/Resolve with the SDI port but I'm using PGenerator connected to the DVI port. I'm also calibrating for legal range material. Would you have any idea if extended range is still the correct way to go here in the patch scale setting? Another thing I'm not sure of in this situation is the monitor's black level setting for the DVI input, would legal be correct?

You will really need to ask FSI.
Also, there is no guarantee the DVI input has anything to do with the SDI input.

Steve