457
edits
Image Stitching for NVIDIA Jetson/Performance/Orin: Difference between revisions
Image Stitching for NVIDIA Jetson/Performance/Orin (view source)
Revision as of 18:11, 8 August 2024
, 8 Augustno edit summary
No edit summary |
|||
| Line 14: | Line 14: | ||
For reference, you will find in each section the homographies calibration file used for the testing. The performance results can vary depending on the homographies, but on average the following results represent the overall performance of the element. | For reference, you will find in each section the homographies calibration file used for the testing. The performance results can vary depending on the homographies, but on average the following results represent the overall performance of the element. | ||
= | == Pipeline structure == | ||
{{Review|I would move this section before the sections talking about performance}} | |||
{{Review|Also, you can put the 3 pipelines used for 2, 3 and 6 inputs}} | |||
To replicate the results using your images, videos, or cameras, you can use the following pipeline as a base for the case of 2 cameras, then you can add the other inputs for the other cases. Also, you can adjust the resolution if needed. | |||
<source lang=bash> | <source lang=bash> | ||
INPUT_0=<VIDEO_INPUT_0> | |||
INPUT_1=<VIDEO_INPUT_1> | |||
gst-launch-1.0 -e cudastitcher name=stitcher \ | |||
homography-list="`cat homographies.json | tr -d "\n" | tr -d " "`" \ | |||
filesrc location=$INPUT_0 ! qtdemux ! h264parse ! nvv4l2decoder ! queue ! nvvidconv ! stitcher.sink_0 \ | |||
filesrc location=$INPUT_1 ! qtdemux ! h264parse ! nvv4l2decoder ! queue ! nvvidconv ! stitcher.sink_1 \ | |||
stitcher. ! perf print-cpu-load=true ! fakesink -v | |||
</source> | </source> | ||
== | == Calibration Files === | ||
=== 1920x1080 === | === 1920x1080 === | ||
| Line 189: | Line 195: | ||
</source> | </source> | ||
=== 4k === | |||
=== | |||
In the case of 4K resolution, for two,three and six inputs the homographies files are the following: | In the case of 4K resolution, for two,three and six inputs the homographies files are the following: | ||
| Line 353: | Line 355: | ||
} | } | ||
</source> | </source> | ||
= Orin AGX = | |||
== Platform Setup == | |||
For the AGX Orin, the testing was done with JP 6. While for Orin NX with JP 5.1.2. | |||
Also, for the examples with Jetson Clocks, you can activate this mode as follows. | |||
<source lang=bash> | |||
sudo /usr/bin/jetson_clocks | |||
</source> | |||
== Framerate == | |||
=== 1920x1080 === | |||
The next graph shows the amount of fps for each setup of inputs with and without jetson clocks. | |||
[[File:FPS 1920X1080 AGX ORIN.png|thumb|center|1050x500px|FPS on 1920x1080 images with and without jetson_clocks.sh]] | |||
=== 4K === | |||
The next graph shows the amount of fps for each setup of inputs with and without jetson clocks. | |||
[[File:FPS RESULTS STITCHER 4K.png|1050x500px|thumb|center|FPS on 3840x2160 images with and without jetson_clocks.sh]] | [[File:FPS RESULTS STITCHER 4K.png|1050x500px|thumb|center|FPS on 3840x2160 images with and without jetson_clocks.sh]] | ||