-
Notifications
You must be signed in to change notification settings - Fork 231
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How do I process live camera inputs to generate surround view? #799
Comments
Can you describe a bit more your environment or requirements? |
Thank you for your quick reply! I am using a MIPI module of 6 cameras connecting to an NVIDIA Jetson Xavier AGX. I want to use 4 of these cameras to generate a surround view from a small autonomous vehicle. I am using Python but can use C++ if needed, on Ubuntu 18.04. I wanted to test the tool using a gstreamer pipeline for now.
I am new to gstreamer and was using the below pipeline. Does
Would you have suggestion on redirecting the output so that
|
The application |
We implemented a xcam video filter for FFmpeg, exported some functions (https://github.com/intel/libxcam/blob/master/capi/context_priv.h#L31) which can be used through FFmpeg command line like this. For surround view application, our implementation only support stitch four cameras. you need to specify parameters and provide camera calibration files also. For some reasons we did not submit this xcam video filter to FFMpeg community successfully, if you want to try I can send this filter to you through email.
|
xcam ffmpeg submission lives at https://patchwork.ffmpeg.org/project/ffmpeg/patch/20200731145710.114479-1-wei.zong@intel.com/#56952 not dure how applicable it to current ffmpeg git tree ..... |
The test-surround-view only works with file inputs. How can I do live stitching with a live stream (like "appsink")?
If I send the GStreamer stream to a file, this file grows very fast and I cannot handle its size. I am not sure how to read the inputs in a live fashion.
Thank you
The text was updated successfully, but these errors were encountered: