So, I have a problem with the Jetson Multimedia API. According to the Jetpack r35.5.0 release notes (see here, pages 12 and 13) there is a change in the JPEG decoder, a new flag mjpeg_decode is introduced. As a result, the code I compiled for a Jetson board with Jetpack 35.4.1 is not runnable on 35.5.0. This is expected behavior, as it is clearly stated in the release notes that the new jpeg library and headers must be used now. So far so good.
Now, I downloaded the r36.2.0 L4T Jetpack container from the official Nvidia catalogue (i.e. from here). But when I take a look at the Multimedia API that ships with this container (under /usr/src/jetson_multimedia_api) the files jpeglib.h and NvJpegDecoder.h are the same from Jetpack version r35.4.1 NOT r35.5.0, i.e. the mjpeg_decode flag is missing.
I am confused now. Is this an old version of the multimedia API? Was the change introduced in r35.5.0 reverted again in r36.2.0? I was not able to find anything in the r36.2.0 release notes regarding this topic.
Q: Is there any example of running RTSP streaming?
Q: Is there an example for running UDP streaming?
Q: I have a USB camera. How can I launch it on AGX Orin?
For further issues, please share a method to replicate the issue through gstreamer command, or either sample. We will set up developer kit and check.
Hey, thanks for the very fast reply, but I think we kind of misunderstand each other. Let me rephrase my question:
According to the API reference r35.5.0 (see here) the NvJpegDecoder has the method disableMjpegDecode(), in API reference r36.2.0 (see here) the NvJpegDecoder does NOT have this method but in API reference r36.3.0 (see here) the NvJpegDecoder does have this method again.
So, the disableMjpegDecode() method was first added, then removed and then added again? This seems very strange and confusing to me.
One last question: wouldn’t it make sense to also provide an L4T Jetpack container here for r35.5.0?
This question was already asked before here but one Nvidia moderator said it’s not necessary because the 35.4.1. containers should also work for 35.5.0. But that is simply not true, right? Because of the change of the JPEG library my code that was compiled in a 35.4.1. container is definitely not runnable on a Jetson with 35.5.0.