I could see multiple posts in which developers have raised this issue. But could not find any solid solution. Is there any work around to read Raw bayer data ? or we have to use only nvcamerasrc?
Seems the r24.2 have problem to set the width, height of the fmt_formats via yavta. You could add some message in the camera_common_s_fmt() at file kernel/drivers/media/platform/tegra/camera/camera_common.c to figure out why it failed to set the resolution.
You mean the raw file? You may need some raw viewer tools like raw2bmp of raw2rgb.
I am not sure if Bayer file is recorded properly or not. Because file is too big… I converted it to Tiff file and tried viewing it through Irfan view. But could not succeed.
The r24.2 implement v4l2 driver base on the new v4l2 framework. You can get the 1920x1080 raw data from below command, yavta may not fully support now.
We are planning to connect three Bayer sensors to TX1 and do simultaneous YUV conversion and encoding. Each sensor will be having different lens. In this case, Can single ISP configuration work for all three sensors?.
FYI We are going to get this ISP configuration from third party.
OKay. So using Two TX1 ISP for processing three RAW bayer sensors (with different lens) simultaneously is not possible with TX1 or We can have multiple ISP configuration file to achieve this ??
Our concern is - We need to process all three simultaneously. So Could You please Let us know how ISP will handle that?
ISP config files are for image tuning. One ISP config setting file for one sensor if they have any different. If you load the same config file to different sensor lens module you may have some image quality problem.
Yes We understand that ISP is used for image tuning. But our concern is - How these different ISP configuration file will be used by nvcamerasrc plugin.
For example,
Assume we have created three different ISP configuration files - one for each Bayer sensor.
As Bayer to YUV conversion is needed, We will be using nvcamerasrc. As per our use case, this conversion needs to happen simultaneously for all three Bayer sensors.
Below are the questions:
There are only two ISP blocks in TX1. But We have 3 configuration files and three Bayer sensors. How nvcamerasrc should be invoked in this scenario ?
Can two ISPs handle three Bayer sensors at a time ?
Okay Shane. Thanks for providing detailed information!
Let me consolidate our design…
We will be connecting one YUV sensor and 3 Bayer sensors through MIPI-CSI. We will be creating 3 ISP configuration files - one for each Bayer sensor. We will use gstreamer plugins like v4l2src(for YUV sensor) and nvcamerasrc (for three Bayer sensors) to encode and record MP4 files of each sensor simultaneously.
Note: Using v4l2src and nvcamerasrc together is suppported from R24.2
Could You please Let me know if the above design is possible in R24.2 ?
YUV sensor will be 1080p and three Bayer sensors will be 720p.
As you said, 30 fps cannot be achieved. Any rough number of fps, we will get for above configuration?
Could You please let me know how the different bayer sensors can be referenced in gstreamer while using nvcamerasrc. Generally sensor-id will be used. Please confirm whether with R24.2 also we need to use sensor-id only or a different method.