GstKinesisWebRTC: Evaluating GstKinesisWebRTC

From RidgeRun Developer Wiki



Previous: Description/Signals Index Next: Getting the code




This page serves as a guide to test the GStreamer Kinesis Webrtc for the NVIDIA Jetson Board 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.: NVIDIA Jetson TX1/TX2, Xavier, Nano, NXP i.MX8, i.MX6 etc...)
  • gst-launch-1.0 --gst-version
  • uname -a

Features in the Evaluation

To help you test GstKinesisWebrtc, RidgeRun can provide an evaluation version of the plug-in. The following table summarizes the features available in both the professional and evaluation version of the element.

Feature Professional Evaluation
GstKinesisWebrtc Element Y Y
Unlimited Processing Time Y N(1)
Source Code Y N
Table 1. Features provided in the evaluation version

(1) The evaluation version will limit the streaming time to 2 minute.

Testing the Binary

Dependencies

GstKinesisWebrtc dependencies can be found and installed by following the next link: Building GstKinesisWebRTC/Dependencies

Running the Binary

RidgeRun should've provided you with a shared object:

GStreamer Plug-in
libgstkinesiswebrtc.so

Usually, it comes within a tar file. Extract the content by using the following command:

tar -xvf gst-kinesis-webrtc-version-gst-version-platform-0.1.0-eval.tar

Inside, you should have a configuration.sh script. It adds automatically the path of the shared object in your environment. Please run it:

./configuration.sh

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

gst-inspect-1.0 kinesiswebrtcbin

You should see the inspect output for the evaluation binary.

Another way to use the binary provided is to manually export the location of the plugin in your environment.

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

where /path/to/evaluation/binary/plugin is the location in your file system where you have the plugin provided by RidgeRun. Additionally, you may just copy the binary into the standard GStreamer plug-in search path.

Example Pipelines

Please refer to the next pages for reference pipelines.



Previous: Description/Signals Index Next: Getting the code