<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic i.MX8 QuadMax MJPEG VPU Decoding in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/i-MX8-QuadMax-MJPEG-VPU-Decoding/m-p/1487087#M192354</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I think I've run into a limitation of the NXP BSP and would like to confirm that with you. I'm running a Torizon build based on the NXP&amp;nbsp;&lt;SPAN&gt;5.4.70-2.3.3. The board is powered by an i.MX8 QuadMax. The problem I was seeing was that I couldn't read and decode the MJPEG frames from my USB camera fast enough to produce the manufacturer advertised 1920x1080&amp;nbsp; at 60FPS.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;I first confirmed the camera was not the bottleneck by testing it both on Windows and on my target platform, but without the JPEG decoding. With a bare GStreamer pipeline I was able to get the advertised 60FPS. As soon as I add&amp;nbsp;&lt;STRONG&gt;v4l2jpegdec&lt;/STRONG&gt;, my framerate drops to 20 FPS max. Adding a 'queue' element before it or changing the capture mode to use DMA only changed things by ~10%.&amp;nbsp;&lt;/P&gt;&lt;P&gt;When checking the BSP release notes, I noticed that it doesn't seem like MJPEG HW decoding is not actually supported for my processor (please see below). Which would explain why when trying to use the proper element of &lt;STRONG&gt;v4l2video1jpegdec,&amp;nbsp;&lt;/STRONG&gt;all I was getting was a still frame.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can someone from the NXP team please confirm this for me? Also, if it is true, are there any plans to add it or any possible workarounds (even if it means changing the processor / camera).&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;</description>
    <pubDate>Sun, 10 Jul 2022 21:31:31 GMT</pubDate>
    <dc:creator>odd_bikes</dc:creator>
    <dc:date>2022-07-10T21:31:31Z</dc:date>
    <item>
      <title>i.MX8 QuadMax MJPEG VPU Decoding</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX8-QuadMax-MJPEG-VPU-Decoding/m-p/1487087#M192354</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I think I've run into a limitation of the NXP BSP and would like to confirm that with you. I'm running a Torizon build based on the NXP&amp;nbsp;&lt;SPAN&gt;5.4.70-2.3.3. The board is powered by an i.MX8 QuadMax. The problem I was seeing was that I couldn't read and decode the MJPEG frames from my USB camera fast enough to produce the manufacturer advertised 1920x1080&amp;nbsp; at 60FPS.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;I first confirmed the camera was not the bottleneck by testing it both on Windows and on my target platform, but without the JPEG decoding. With a bare GStreamer pipeline I was able to get the advertised 60FPS. As soon as I add&amp;nbsp;&lt;STRONG&gt;v4l2jpegdec&lt;/STRONG&gt;, my framerate drops to 20 FPS max. Adding a 'queue' element before it or changing the capture mode to use DMA only changed things by ~10%.&amp;nbsp;&lt;/P&gt;&lt;P&gt;When checking the BSP release notes, I noticed that it doesn't seem like MJPEG HW decoding is not actually supported for my processor (please see below). Which would explain why when trying to use the proper element of &lt;STRONG&gt;v4l2video1jpegdec,&amp;nbsp;&lt;/STRONG&gt;all I was getting was a still frame.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can someone from the NXP team please confirm this for me? Also, if it is true, are there any plans to add it or any possible workarounds (even if it means changing the processor / camera).&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Sun, 10 Jul 2022 21:31:31 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX8-QuadMax-MJPEG-VPU-Decoding/m-p/1487087#M192354</guid>
      <dc:creator>odd_bikes</dc:creator>
      <dc:date>2022-07-10T21:31:31Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX8 QuadMax MJPEG VPU Decoding</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX8-QuadMax-MJPEG-VPU-Decoding/m-p/1488637#M192464</link>
      <description>&lt;P&gt;pls refer to the link as below:&lt;/P&gt;
&lt;P&gt;"&lt;A href="https://community.nxp.com/t5/i-MX-Processors/i-MX8X-m-jpeg-to-h264-VPU-transcoding-speed/td-p/1290668" target="_blank"&gt;https://community.nxp.com/t5/i-MX-Processors/i-MX8X-m-jpeg-to-h264-VPU-transcoding-speed/td-p/1290668&lt;/A&gt;"&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 13 Jul 2022 08:55:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX8-QuadMax-MJPEG-VPU-Decoding/m-p/1488637#M192464</guid>
      <dc:creator>joanxie</dc:creator>
      <dc:date>2022-07-13T08:55:14Z</dc:date>
    </item>
  </channel>
</rss>

