GstCUDA - Evaluating GstCUDA: Difference between revisions

From RidgeRun Developer Wiki
No edit summary
No edit summary
Line 21: Line 21:


== Features in the Evaluation Version ==
== Features in the Evaluation Version ==
The GstCUDA evaluation version contains all the features of the full version, but with the exception that is limited to only process 600 frames as maximum. Also, it is provided in a binary way, so you won't have access to the source code.
The GstCUDA evaluation version contains all the features of the full version, but with the exception that is limited to only process 600 frames as maximum. Also, it is provided in a binary way, so you won't have access to the source code.


Line 68: Line 69:


== Testing the Binary ==
== Testing the Binary ==
'''''Under Construction'''''
 
First, make sure the dependencies are fulfilled:
 
<syntaxhighlight lang='bash'>
sudo apt-get install \
libgstreamer1.0-dev \
libgstreamer-plugins-base1.0-dev \
gstreamer1.0-plugins-base \
libgstreamer-plugins-bad1.0-dev \
gstreamer1.0-plugins-bad \
libegl1-mesa-dev \
gtk-doc-tools
</syntaxhighlight>
 
Also, be sure that [ https://developer.ridgerun.com/wiki/index.php?title=GstCUDA_-_Building_and_Installation_Guide#CUDA_L4T_package | CUDA L4T package] is successfully installed.
 
To use the binary provided by RidgeRun, export the location of the evaluation binary in your environment.
<syntaxhighlight lang="bash">
export GST_PLUGIN_PATH=${GST_PLUGIN_PATH}:/path/to/evaluation/binary/
</syntaxhighlight>
where ''/path/to/evaluation/binary'' is the location in your file system where you have the binary provided by RidgeRun.
 
Additionally, you may just copy the binary into the standard GStreamer plug-in search path.
 
Finally, test that the plugin is being properly picked up by GStreamer by running:
<syntaxhighlight lang="bash">
gst-inspect-1.0 rtspsink
</syntaxhighlight>
 
You should see the inspect output for the evaluation binary.





Revision as of 21:24, 27 November 2017


Supported Platforms


Home

Building and Installation Guide


CUDA L4T package] is successfully installed.

To use the binary provided by RidgeRun, export the location of the evaluation binary in your environment.

export GST_PLUGIN_PATH=${GST_PLUGIN_PATH}:/path/to/evaluation/binary/

where /path/to/evaluation/binary is the location in your file system where you have the binary provided by RidgeRun.

Additionally, you may just copy the binary into the standard GStreamer plug-in search path.

Finally, test that the plugin is being properly picked up by GStreamer by running:

gst-inspect-1.0 rtspsink

You should see the inspect output for the evaluation binary.


Example Pipelines

Please refer to the Examples page for reference pipelines.


Troubleshooting

The first level of debug to troubleshoot a failing evaluation binary is to inspect GStreamer debug output.

GST_DEBUG=2 gst-launch-1.0

If the output doesn't help you figure out the problem, please contact support@ridgerun.com with the output of the GStreamer debug and any additional information you consider useful.

If the plug-in is not being recognized, please provide the output of the following command:

gst-inspect-1.0 libgstcuda.so




Supported Platforms


Home

Building and Installation Guide