Jump to content

GStreamer pipelines for Jetson TX2: Difference between revisions

m
no edit summary
mNo edit summary
mNo edit summary
Line 1: Line 1:
<seo title="Jetson TX2 GStreamer Pipelines | H264 and H265 Encoding | RidgeRun" titlemode="replace" keywords="GStreamer, Linux SDK, Linux BSP,  Embedded Linux, Device Drivers, Nvidia, Xilinx, TI, NXP, Freescale, Embedded Linux driver development, Linux Software development, Embedded Linux SDK, Embedded Linux Application development, GStreamer Multimedia Framework,Jetson TX2 pipelines, Jetson TX2 GStreamer pipelines, Jetson TX2 GStreamer, H264, H265, H264 encoding, H265 encoding, omnivision OV5693."  description="This wiki guide from RidgeRun provides the GStreamer pipelines including H264 and H265 encoding used on Jetson TX2 module!"></seo>
<seo title="Jetson TX2 GStreamer Pipelines | H264 and H265 Encoding | RidgeRun" titlemode="replace" keywords="GStreamer, Linux SDK, Linux BSP,  Embedded Linux, Device Drivers, NVIDIA, Xilinx, TI, NXP, Freescale, Embedded Linux driver development, Linux Software development, Embedded Linux SDK, Embedded Linux Application development, GStreamer Multimedia Framework,Jetson TX2 pipelines, Jetson TX2 GStreamer pipelines, Jetson TX2 GStreamer, H264, H265, H264 encoding, H265 encoding, omnivision OV5693."  description="This wiki guide from RidgeRun provides the GStreamer pipelines including H264 and H265 encoding used on Jetson TX2 module!"></seo>


<table>
<tr>
<td><div class="clear; float:right">__TOC__</div></td>
<td valign=top>
{{GStreamer debug}}
{{GStreamer debug}}
</td>
</table>


== Introduction ==
== Introduction to NVIDIA Jetson TX2 GStreamer pipelines==


On this page you are going to find a set of pipelines used on Jetson TX2, specifically used with the Jetson board. The wiki page tries to describe some of the multimedia features of the platform like the NVIDIA model to handle the ISP through its custom (and close) plugin called nvcamerasrc. It also includes a brief description of the sample application called nvgstcapture-1.0 and ways to measure the ARM load. The goal is to provide you some example pipelines and introduction to the board. It is a work in progress.
On this page you are going to find a set of pipelines used on Jetson TX2, specifically used with the Jetson board. The wiki page tries to describe some of the multimedia features of the platform like the NVIDIA model to handle the ISP through its custom (and close) plugin called nvcamerasrc. It also includes a brief description of the sample application called nvgstcapture-1.0 and ways to measure the ARM load. The goal is to provide you some example pipelines and introduction to the board. It is a work in progress.
Line 30: Line 36:
</syntaxhighlight>
</syntaxhighlight>


Nvidia plugins:
NVIDIA plugins:


<syntaxhighlight lang='bash'>
<syntaxhighlight lang='bash'>
Line 125: Line 131:
==== nvcamerasrc ====
==== nvcamerasrc ====


This plugin was created by nvidia and it has access to the ISP that helps converting from bayer to yuv suitable for the video encoders. However, it seems that its usage is limited to the ov5693 sensor until NVIDIA releases its source code or until it adds support to v4l2 to use the ISP.
This plugin was created by NVIDIA and it has access to the ISP that helps converting from bayer to yuv suitable for the video encoders. However, it seems that its usage is limited to the ov5693 sensor until NVIDIA releases its source code or until it adds support to v4l2 to use the ISP.


<syntaxhighlight lang='bash'>
<syntaxhighlight lang='bash'>
Line 132: Line 138:
</syntaxhighlight>
</syntaxhighlight>


When the pipeline is launched a daemon appears on top nvcamera-daemon, one question about the daemon was posted on the [https://devtalk.nvidia.com/default/topic/926578/jetson-tx1/nvcamera-daemon/ Nvidia Embedded Computing Forum]
When the pipeline is launched a daemon appears on top nvcamera-daemon, one question about the daemon was posted on the [https://devtalk.nvidia.com/default/topic/926578/jetson-tx1/nvcamera-daemon/ NVIDIA Embedded Computing Forum]


ARM consumption: 45.7% of one core (4 cores available 400% - this means something like 11.25% of total)
ARM consumption: 45.7% of one core (4 cores available 400% - this means something like 11.25% of total)
Cookies help us deliver our services. By using our services, you agree to our use of cookies.