Yes. However, this was for the nvstreammux case where I could access the peer pads to reach the uridecodebin element.
My problem with nvmultiurisrcbin is that I cannot access the samenvstreammux src pad or even the nvurisrcbins’ created internally by nvmultiurisrcbin.
I can only access the whole nvmultiurisrcbin’s src pad (shown on the right part of image) and calling src_pad.get_peer() does not return the nvstreammux src pad (previous element) but the next element’s sinkpad in the pipeline.
I don’t see how I can modify the source code to expose these pads or the internal (and closed source) nvstreammux which is called by libraries within the gst-nvmultiurisrcbin source code.
- Do you mean to modify the gst-nvmultiurisrcbincreator.cpp with some custom logic and rebuild the plugin?
- I am using Python and pyds bindings. Do I have to implement or re-build the bindings?
I also read This topic is similar but was also not solved with the provided answers (I have reviewed test5 with src_attribs_all.txt config but it doesn’t provide a clear solution. Any help to make this more clear is much appreciated!