GstCUDA - Evaluating GstCUDA
| ← |
⌂ Home |
→ |
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.
| Feature | Professional | Evaluation |
|---|---|---|
| cudafilter Element | Y | Y |
| cudaexamplefilter Element | Y | Y |
| Unlimited Processing Time | Y | N (1) |
| Source Code | Y | N |
Testing the Binary
Under Construction
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
| ← |
⌂ Home |
→ |