This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DLPDLCR230NPEVM: How to properly mitigate the effect of image processing?

Part Number: DLPDLCR230NPEVM
Other Parts Discussed in Thread: DLP230NP, DLPC3436

Hi,

Currently we are testing dlp230np evm.

What confuses us is how the dlp image processing work. Please note that we have already received dlp4500lc and dlp3100lc as well, to turn off the image processing. However, we are in a situation to minimize the effects of the image processing while still working with the dlp230np. More specifically speaking, what we are trying to do is mitigating the effect of the image processing, by monitoring how individual pixels with varying intensity(or luminosity) are displayed — which is done by capturing the output of the projector via the synchronized camera. We assumed that there should be one to one correspondence between the actual pixel intensity and the pixel intensity that we have in the input source, regardless of the histogram of the input source. I think this might be correct or not. In other words, we are trying to mitigate the effect of image processing by using some type of 1d lut function with the each individual pixel’s intensity as input. Do you think our approach is correct? Or what is the best way to mitigate the effect of image processing?

Thank you

  • Hello Kim,

    Welcome to DLP forum and thank you for your interest in DLP technology.

    The DLP230NP along with DLPC3436 controller is designed for display application. The image processing is an integral part of  the application to provide best visual experience to human eye.

    The typical image processing for display is not only spatial  (with in a frame) but also temporal ( across frames). It is very likely that your suggested method will not work.

    I also want to remind you that we can not support any such reengineering activity.

    regards,

    Vivek