GstCUDA - Evaluating GstCUDA: Difference between revisions
mNo edit summary |
No edit summary |
||
Line 13: | Line 13: | ||
* gst-launch-1.0 --gst-version | * gst-launch-1.0 --gst-version | ||
* uname -a | * uname -a | ||
* Jetpack and L4T version | |||
<center> | <center> | ||
[[File:RR Contact Us.png|200px|link=http://www.ridgerun.com/contact]] | [[File:RR Contact Us.png|200px|link=http://www.ridgerun.com/contact]] |
Revision as of 20:19, 27 November 2017
← |
⌂ 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
Under Construction
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 |
→ |