What's the difference between uridecodebin and nvurisrcbin

Please provide complete information as applicable to your setup.

• Hardware Platform (Jetson / GPU)
• DeepStream Version
• JetPack Version (valid for Jetson only)
• TensorRT Version
• NVIDIA GPU Driver Version (valid for GPU only)
• Issue Type( questions, new requirements, bugs)
• How to reproduce the issue ? (This is for bugs. Including which sample app is using, the configuration files content, the command line used and other details for reproducing)
• Requirement details( This is for new requirement. Including the module name-for which plugin or for which sample application, the function description)

In deepstream-test3-app, there is 2 kind of decode bin. But I don’t understand what’s there difference?

Only support file-loop and cudadec-memtype? And I want to add some probs for nvurisrcbin’s child element, is there any doc for them?

Decodebin child added: nvurisrc_bin_src_elem
Decodebin child added: nvurisrc_bin_queue
Decodebin child added: nvurisrc_bin_nvvidconv_elem
Decodebin child added: nvurisrc_bin_src_cap_filter_nvvidconv
Decodebin child added: nvurisrc_bin__fakesink
Decodebin child added: tee0
Decodebin child added: nvurisrc_bin_fakequeue

But from the their child bin, it seems more difference.

/* Source element for reading from the uri.

  • We will use decodebin and let it figure out the container format of the
  • stream and the codec and plug the appropriate demux and decode plugins. */
    if (PERF_MODE) {
    uri_decode_bin = gst_element_factory_make (“nvurisrcbin”, “uri-decode-bin”);
    g_object_set (G_OBJECT (uri_decode_bin), “file-loop”, TRUE, NULL);
    g_object_set (G_OBJECT (uri_decode_bin), “cudadec-memtype”, 0, NULL);
    } else {
    uri_decode_bin = gst_element_factory_make (“uridecodebin”, “uri-decode-bin”);

In short, nvurisrcbin has rtsp reconnection and smart record features.


You can view the properties of nvurisrcbin through gst-inspect-1.0 nvurisrcbin