<?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>i.MX ProcessorsのトピックWhy Gstreamer encoding takes more cpu load while encoding .yuv than .mp4</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Why-Gstreamer-encoding-takes-more-cpu-load-while-encoding-yuv/m-p/2193990#M241703</link>
    <description>&lt;P&gt;In the case of the &lt;STRONG&gt;i.MX VPU Hantro&lt;/STRONG&gt;, while encoding a &lt;STRONG&gt;1080p video&lt;/STRONG&gt;, I considered two different approaches:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;MP4 → YUV → H.264&lt;/STRONG&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;MP4 → H.264&lt;/STRONG&gt;&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;I noticed that the first approach consumes significantly more CPU load compared to the second approach. Is that intermediate conversion required?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;1) Approach 1&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;gt;decode mp4 to yuv&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;gst-launch-1.0 filesrc location=5MB_1080p.mp4 !&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; qtdemux !&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; h264parse !&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; imxvpudec_h264 !&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; filesink location=1080p.yuv&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;CPU load: 90 %&lt;/P&gt;&lt;P&gt;&amp;gt;encode yuv to h264&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;gst-launch-1.0 filesrc location=1080p.yuv !&amp;nbsp; videoparse width=1920 height=1080 format=nv12 framerate=30/1 !&amp;nbsp; imxvpuenc_h264 ! h264parse ! filesink location=1080p.h264&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;CPU load: 35.9%&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;2) Approach 2&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;gt; Decode and Encode in a Single Pipeline&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;gst-launch-1.0 filesrc location=5MB_1080p.mp4 !&amp;nbsp; qtdemux name=demux demux.video_0 ! h264parse ! imxvpudec_h264 ! imxvpuenc_h264 ! h264parse ! filesink location=enc.h264&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;CPU load: 6.6%&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 28 Oct 2025 06:07:19 GMT</pubDate>
    <dc:creator>Hariharan1</dc:creator>
    <dc:date>2025-10-28T06:07:19Z</dc:date>
    <item>
      <title>Why Gstreamer encoding takes more cpu load while encoding .yuv than .mp4</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Why-Gstreamer-encoding-takes-more-cpu-load-while-encoding-yuv/m-p/2193990#M241703</link>
      <description>&lt;P&gt;In the case of the &lt;STRONG&gt;i.MX VPU Hantro&lt;/STRONG&gt;, while encoding a &lt;STRONG&gt;1080p video&lt;/STRONG&gt;, I considered two different approaches:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;MP4 → YUV → H.264&lt;/STRONG&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;MP4 → H.264&lt;/STRONG&gt;&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;I noticed that the first approach consumes significantly more CPU load compared to the second approach. Is that intermediate conversion required?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;1) Approach 1&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;gt;decode mp4 to yuv&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;gst-launch-1.0 filesrc location=5MB_1080p.mp4 !&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; qtdemux !&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; h264parse !&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; imxvpudec_h264 !&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; filesink location=1080p.yuv&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;CPU load: 90 %&lt;/P&gt;&lt;P&gt;&amp;gt;encode yuv to h264&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;gst-launch-1.0 filesrc location=1080p.yuv !&amp;nbsp; videoparse width=1920 height=1080 format=nv12 framerate=30/1 !&amp;nbsp; imxvpuenc_h264 ! h264parse ! filesink location=1080p.h264&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;CPU load: 35.9%&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;2) Approach 2&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;gt; Decode and Encode in a Single Pipeline&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;gst-launch-1.0 filesrc location=5MB_1080p.mp4 !&amp;nbsp; qtdemux name=demux demux.video_0 ! h264parse ! imxvpudec_h264 ! imxvpuenc_h264 ! h264parse ! filesink location=enc.h264&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;CPU load: 6.6%&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 28 Oct 2025 06:07:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Why-Gstreamer-encoding-takes-more-cpu-load-while-encoding-yuv/m-p/2193990#M241703</guid>
      <dc:creator>Hariharan1</dc:creator>
      <dc:date>2025-10-28T06:07:19Z</dc:date>
    </item>
    <item>
      <title>Re: Why Gstreamer encoding takes more cpu load while encoding .yuv than .mp4</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Why-Gstreamer-encoding-takes-more-cpu-load-while-encoding-yuv/m-p/2194163#M241712</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/224949"&gt;@Hariharan1&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;yes, you are right, At approach 1,&amp;nbsp;The primary causes of high CPU load are: extensive data writes to disk and data shuffling during the decoding process. But approach 2,&amp;nbsp;There are no intermediate disk write and read operations; data is directly transferred in memory. So, in your current scenario, approach 2 is the best choice.&lt;/P&gt;
&lt;P&gt;B.R&lt;/P&gt;</description>
      <pubDate>Tue, 28 Oct 2025 09:13:07 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Why-Gstreamer-encoding-takes-more-cpu-load-while-encoding-yuv/m-p/2194163#M241712</guid>
      <dc:creator>pengyong_zhang</dc:creator>
      <dc:date>2025-10-28T09:13:07Z</dc:date>
    </item>
  </channel>
</rss>

