Part Number: TDA2HG
The following picture is the result that we run on the ubuntu with GL_TEXTURE_2D with RGB input
This picture is we run the surround view on tda2hg with GL_TEXTURE_EXTERNAL_OES with nv12 input
please see the difference between this two picture (with red-highlighted),
we are using the same surround view algorithm with same calibration table data.
the only difference is the first picture is using GL_TEXTURE_2D and second is using GL_TEXTURE_EXTERNAL_OES.
Is the issue the appearance of the green bands with GL_TEXTURE_EXTERNAL_OES as opposed to GL_TEXTURE_2D? Can you confirm?
As you noted GL_TEXTURE_2D expects RGB data and with EXTERNAL_OES YUV data can be used. If you are noticing differences, can you confirm if the sources are as expected and no difference is seen in the source images?
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 Gowtham Tammana:
Gowtham TammanaIs the issue the appearance of the green bands with GL_TEXTURE_EXTERNAL_OES as opposed to GL_TEXTURE_2D? Can you confirm?
yes, mark it as the green band is blend.
Gowtham TammanaAs you noted GL_TEXTURE_2D expects RGB data and with EXTERNAL_OES YUV data can be used. If you are noticing differences, can you confirm if the sources are as expected and no difference is seen in the source images?
yes, the source image is same except the no color on above picture that we take Y from NV12 to RGB, you can check the vehicles in both picture, there is the same scene.
In reply to user5312037:
With your second note, its little more clear. The issue you are seeing is the image not be calibrated the same from RGB standalone output compared to NV12 TDA output. Its not the appearance of the green color in the output image. Is that correct.
The calibration file seems to ok, the output image wouldn't look that close if there was something wrong with it. Can you confirm if you are using the same lens file as well with both the tests.
Also can you share on the details of the TI baseline release you are using here.
Gowtham TammanaWith your second note, its little more clear. The issue you are seeing is the image not be calibrated the same from RGB standalone output compared to NV12 TDA output. Its not the appearance of the green color in the output image. Is that correct.
Gowtham TammanaAlso can you share on the details of the TI baseline release you are using here.
we'are using visionSDK 3.0.5
Can you also confirm if the same lens file is being used.
Could you confirm that the CALMAT.BIN in the standalone app matches the files found at /home/root/.calibtable on the target file system? Also, could you confirm that the LENS.BIN file you are using in the standalone app matches the file found at /opt/vision_sdk/LENS.BIN on the target file system?
In reply to Lucas Weaver:
we are not use the surround usecase of visionSDK, thus there is no such file "/opt/vision_sdk/LENS.BIN" used.
we are using the QT with our standalone parameters, and confirmed that parameters of the desktop(ubuntu) and the target are same
I see that you mentioned that you are not using VisionSDK version of usecase and have your own QT version.
Is there any component that is being used from VisionSDK usecase here. If so what are they. Is the calibration scheme also different to that of SDK here.
From SDK perspective, the calibration scheme is not dependent on the format of the images and the use of RGB/NV12 format shouldn't have any impact on the final image.
Here is our AVM with QT architecture
As you seen that we can test with picture, that should not related with camera capture.the display out is located on IPU2 which run the visionSDK.
Is any simple OpenGl test to validate such issue?
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.