Part Number: DLPC3439
our design is based on DLP4710 device and DLPC3439 chipset, version of fw 7.3.2, (DLP LightCrafter 4710 Gen2). Input parallel interface is directly connected to video decoder using YCbCr 4:2:2, bus width is 16 bits, 1 pixel per clock. Input range is limited - black color corresponding to level 16 (dec) and white color corresponding to level 235 (dec) - this behaviour is legit under ITU-R BT.601. Unfortunately, output range of the image is also limited. My question is - how to expand output video levels to full range from black to white ? (for example how to edit internally stored CSC coeficients for YCbCr conversion).
Welcome to DLP forum and thank your interest in DLP technology.
Could you please upload a representative input image and also list the issues you are observing? We will investigate once we have the data.
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to Vivek Thakur:
I have just one issue with output range of luminance levels, otherwise complete system works perfect. Parallel interface in mode 16-bit YCrCb 4:2:2 expect full range of levels from 0 to 0xff (256 luminance levels), but my video decoder provide just limited range from 0x10 to 0xEB, i.e. from 16 to 235 (220 luminance levels) . This range is also according to ITU-R BT. Rec. 601. As consequence of that limited range our system lose ability to display full black and full white color. My question is, how to edit or adjust internal color space convertor (CSC) ? In DLPC3439 Software Programmer's Guide (# DLPU035) at page 21 ther is Note 5 and Note 7 - that should be a solution.
In reply to Zdenek Zechovsky:
We will review it and get back to in couple of days.
From what i am looking into the controller software programmer's guide of DLP3439, there is no command to update the CSC 9 coefficient setting as you requested. We will figure out and let you know the process.
If a post answers your question, please click on "Verify Answer" button
In reply to Sanjeev:
This will require a new firmware build. Currently team is occupied with prior commitments. We will be bale to work on this request (creating a new firmware) week of 28th September.
Meanwhile, hopefully you can continue your development.
Thanks and regards,
it is clear to me that modification of the firmware is time-consuming and not trivial. In any case thank you in advance for your colaboration.
Thank you for your understanding.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.