<?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 Search range in H264 encoder in Intel® Integrated Performance Primitives</title>
    <link>https://community.intel.com/t5/Intel-Integrated-Performance/Search-range-in-H264-encoder/m-p/985087#M21696</link>
    <description>&lt;DIV&gt;&lt;FONT size="2"&gt;
&lt;P&gt;Hi all&lt;/P&gt;
&lt;P&gt;I wonder if the parameter search_x (Maximum of absolute value of horizontal part of motion vector.)and search_y (Maximum of absolute value ofvertical part of motion vector.) mean the search window size in the ME process. If yes, why is it specified so small as 4x4 in the sample.par file which is included in the H264_IPP4.1 encoder? That's bcos normally, we deal with 16x16 or 8x8. Can you tell me the meaning of the search x and search y below?&lt;/P&gt;
&lt;P&gt;Thank you very much in advanced for all the help&lt;/P&gt;
&lt;P&gt;Yours&lt;/P&gt;
&lt;P&gt;Nicky&lt;/P&gt;
&lt;P&gt;--------------------------------------------------------------------------&lt;/P&gt;
&lt;P&gt;H264 Sequence. &lt;/P&gt;
&lt;P&gt;foreman_cif.yuv /* name of source files */&lt;/P&gt;
&lt;P&gt;300 /* number of frames */&lt;/P&gt;
&lt;P&gt;1 299 /* 1(reserved) , N (# of frames in between I frames) */&lt;/P&gt;
&lt;P&gt;0 /* Number of B frames between I (or P) and next P */&lt;/P&gt;
&lt;P&gt;352 /* horizontal_size */&lt;/P&gt;
&lt;P&gt;288 /* vertical_size */&lt;/P&gt;
&lt;P&gt;3 /* frame_rate_code: 3 means 25 Hz, 6 means 50 Hz */&lt;/P&gt;
&lt;P&gt;0 16 16 16 0 /* method(0 - quant_codes, 1 - CBR, quant_codes (I P B) &amp;amp; bitrate !!!ALL must be specified */&lt;/P&gt;
&lt;P&gt;14 4 0 /* extra block split, search x,search_y, implicit weighted biprediction(reserved)*/&lt;/P&gt;
&lt;P&gt;352 /* display_horizontal_size */&lt;/P&gt;
&lt;P&gt;288 /* display_vertical_size */&lt;/P&gt;&lt;/FONT&gt;&lt;/DIV&gt;</description>
    <pubDate>Wed, 13 Jul 2005 16:30:44 GMT</pubDate>
    <dc:creator>nicky_hoang270582</dc:creator>
    <dc:date>2005-07-13T16:30:44Z</dc:date>
    <item>
      <title>Search range in H264 encoder</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/Search-range-in-H264-encoder/m-p/985087#M21696</link>
      <description>&lt;DIV&gt;&lt;FONT size="2"&gt;
&lt;P&gt;Hi all&lt;/P&gt;
&lt;P&gt;I wonder if the parameter search_x (Maximum of absolute value of horizontal part of motion vector.)and search_y (Maximum of absolute value ofvertical part of motion vector.) mean the search window size in the ME process. If yes, why is it specified so small as 4x4 in the sample.par file which is included in the H264_IPP4.1 encoder? That's bcos normally, we deal with 16x16 or 8x8. Can you tell me the meaning of the search x and search y below?&lt;/P&gt;
&lt;P&gt;Thank you very much in advanced for all the help&lt;/P&gt;
&lt;P&gt;Yours&lt;/P&gt;
&lt;P&gt;Nicky&lt;/P&gt;
&lt;P&gt;--------------------------------------------------------------------------&lt;/P&gt;
&lt;P&gt;H264 Sequence. &lt;/P&gt;
&lt;P&gt;foreman_cif.yuv /* name of source files */&lt;/P&gt;
&lt;P&gt;300 /* number of frames */&lt;/P&gt;
&lt;P&gt;1 299 /* 1(reserved) , N (# of frames in between I frames) */&lt;/P&gt;
&lt;P&gt;0 /* Number of B frames between I (or P) and next P */&lt;/P&gt;
&lt;P&gt;352 /* horizontal_size */&lt;/P&gt;
&lt;P&gt;288 /* vertical_size */&lt;/P&gt;
&lt;P&gt;3 /* frame_rate_code: 3 means 25 Hz, 6 means 50 Hz */&lt;/P&gt;
&lt;P&gt;0 16 16 16 0 /* method(0 - quant_codes, 1 - CBR, quant_codes (I P B) &amp;amp; bitrate !!!ALL must be specified */&lt;/P&gt;
&lt;P&gt;14 4 0 /* extra block split, search x,search_y, implicit weighted biprediction(reserved)*/&lt;/P&gt;
&lt;P&gt;352 /* display_horizontal_size */&lt;/P&gt;
&lt;P&gt;288 /* display_vertical_size */&lt;/P&gt;&lt;/FONT&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 13 Jul 2005 16:30:44 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/Search-range-in-H264-encoder/m-p/985087#M21696</guid>
      <dc:creator>nicky_hoang270582</dc:creator>
      <dc:date>2005-07-13T16:30:44Z</dc:date>
    </item>
    <item>
      <title>Re: Search range in H264 encoder</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/Search-range-in-H264-encoder/m-p/985088#M21697</link>
      <description>&lt;DIV&gt;Hello,&lt;/DIV&gt;
&lt;DIV&gt;&lt;/DIV&gt;
&lt;DIV&gt;search_x, search_y parameters are the ranges of search for motion estimation algorithm. The values set for 4 in sample.par file just as an example. You can vary these numbers. Values 8 and 16 are also possible.&lt;/DIV&gt;
&lt;DIV&gt;&lt;/DIV&gt;
&lt;DIV&gt;With best regards,&lt;/DIV&gt;
&lt;DIV&gt; Sergey.&lt;/DIV&gt;</description>
      <pubDate>Wed, 27 Jul 2005 16:59:51 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/Search-range-in-H264-encoder/m-p/985088#M21697</guid>
      <dc:creator>sburakov</dc:creator>
      <dc:date>2005-07-27T16:59:51Z</dc:date>
    </item>
    <item>
      <title>Re: Search range in H264 encoder</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/Search-range-in-H264-encoder/m-p/985089#M21698</link>
      <description>&lt;DIV&gt;&lt;/DIV&gt;
&lt;P&gt;FYI&lt;/P&gt;
&lt;P&gt;Based on my analysis, so very limited search range is still working reasonable well, becausesearching isnotrestrictedby absolute values of &lt;FONT size="2"&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;search x and search y&lt;/P&gt;
&lt;P&gt;butthese are justrelativelimits around a best initial motion predictor (see umc_h264_me.cpp for more details)&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 07 Oct 2005 21:54:21 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/Search-range-in-H264-encoder/m-p/985089#M21698</guid>
      <dc:creator>andrewk88</dc:creator>
      <dc:date>2005-10-07T21:54:21Z</dc:date>
    </item>
  </channel>
</rss>

