GstCUDA - Evaluating GstCUDA

← Supported Platforms

⌂ Home

→ Building and Installation Guide

---

This page serves as a guide to test the GstCUDA evaluation binary provided by RidgeRun.

Requesting the Evaluation Binary

In order to request an evaluation binary for a specific architecture, please contact us providing the following information:

• Platform (i.e.: TX1, TX2)
• gst-launch-1.0 --gst-version
• uname -a
• Jetpack and L4T 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 600 frames maximum processing limitation allows to test GstCUDA for 10 seconds on a 60fps pipeline, or for 20 seconds on a 30fps pipeline.

The following table summarizes the features available in both the professional and evaluation version of the element.

Table 1. Features provided in the evaluation version

Feature	Professional	Evaluation
cudafilter Element	Y	Y
cudaexamplefilter Element	Y	Y
CUDA algorithm examples Library	Y	Y
Unlimited Processing Time	Y	N (1)
Source Code	Y	N

(1) The evaluation version will limit the processing time to a maximum of 600 frames.

Testing the Binary

First, make sure the dependencies are fulfilled:

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

Also, be sure that [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