I have begun working with a Basler MIPI camera on Nano, and I wanted to reach out to get a sense of what others are using for an interface to create gstreamer pipelines.
The camera doesn’t immediately show available resolutions and frame rates in response to:
v4l2-ctl --list-formats-ext
Instead, the device displays:
ioctl: VIDIOC_ENUM_FMT
Index : 0
Type : Video Capture
Pixel Format: 'RGGB'
Name : 8-bit Bayer RGRG/GBGB
Index : 1
Type : Video Capture
Pixel Format: 'RG10'
Name : 10-bit Bayer RGRG/GBGB
Index : 2
Type : Video Capture
Pixel Format: 'RG12'
Name : 12-bit Bayer RGRG/GBGB
Index : 3
Type : Video Capture
Pixel Format: 'AR24'
Name : 32-bit BGRA 8-8-8-8
Index : 4
Type : Video Capture
Pixel Format: 'UYVY'
Name : UYVY 4:2:2
Index : 5
Type : Video Capture
Pixel Format: 'NV16'
Name : Y/CbCr 4:2:2
Index : 6
Type : Video Capture
Pixel Format: 'YUYV'
Name : YUYV 4:2:2
I have started using the Python library from Basler, and found this great repo which is working very well:
But I am wondering if I’m overlooking av4l2-ctl way to attach the camera to a standard gst pipeline for testing and creating network streams.
Thanks for responding. I am familiar with gst-launch-1.0 and have used it frequently with cameras.
This specific situation is different for me in that the way that the Basler camera presents itself to v4l. I have provided the detail in my original question.
Would you be able to speak to using gst with an interface difference such as this? Or point me at a forum link that deals with it specifically?
Just to close this out - This particular Basler camera requires a driver link and is not available as a typical v4l2 camera as shown by the suggestion above.