We have found a strange issue that seems nvvideoconvert and nvvidconv gst plugin conflict in the same process.
we have an gst application needs run two pipelines with deepsteam nvvideoconvert in one pipeline and a traditional nvvidconv plugin in another pipeline.
In order to make our problem more simple, we create a test application which very simple, use gst_parse_launch to create two pipelines with the below pipeline description.
#define PIPE_STR0 “videotestsrc ! nvvideoconvert ! video/x-raw, width=640, height=480 ! xvimagesink”
#define PIPE_STR1 “filesrc location=test0105.mp4 ! h264parse ! nvv4l2decoder ! nvvidconv ! xvimagesink”
And in my application call gst_parse_launch(pipe_str, NULL) launch these two pipe
Then the second pipe will fail and show “internal data stream error” and xwindows is not displayed correctly.
But if we use gst-launch to create this pipeline in a different process, it will succeed without any error.
Could you help us confirm this is a limitation or something we don’t know happen when nvvideoconvert and nvvidconv were used at the same process with the different pipelines? thanks