The differences between the two pipelines are:
-
Second pipeline uses HW decoder. This would be efficient on Jetson as it wouldn’t load CPU. But it would only work on a Jetson.
First pipeline uses uridecodebin, that would select decoder at runtime from available ones. On Jeston it would select the HW decoder, but would also work on another platform such as x86/Windows [EDIT: may need to remove nvvidconv into BGRx and directly use videoconvert into BGR]. In fact, this one would work with any supported encoding, not only jpeg. -
Second difference is that the second pipeline uses jpegparse. This may ignore framerate and turn into async mode (framerate=0/1).
For decoding, have you tried the opencv code I shared above ?
You may find some more details here (you would just replace the capture pipeline with the one I shared in my previous post):