<?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 Re: ipp6.0 h264 encoder code review in Intel® Integrated Performance Primitives</title>
    <link>https://community.intel.com/t5/Intel-Integrated-Performance/ipp6-0-h264-encoder-code-review/m-p/882173#M10328</link>
    <description>&lt;DIV style="margin:0px;"&gt;Hello,&lt;BR /&gt;&lt;BR /&gt;I have the same problem like you. I want to review the h.264 code but its very complicated.&lt;BR /&gt;&lt;BR /&gt;I tried to use Doxygen to generate some helpful HTML meta-data, but unfortunately, the IPP comments dont follow the Doxygen recommendation. Please, my question is what steps youre following to understand the code?&lt;BR /&gt;&lt;BR /&gt;Thanks.&lt;/DIV&gt;</description>
    <pubDate>Fri, 13 Mar 2009 21:33:38 GMT</pubDate>
    <dc:creator>transcoding</dc:creator>
    <dc:date>2009-03-13T21:33:38Z</dc:date>
    <item>
      <title>ipp6.0 h264 encoder code review</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/ipp6-0-h264-encoder-code-review/m-p/882172#M10327</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;Being a junior programmer, I have to dig into this most complicated codec... &lt;BR /&gt;&lt;BR /&gt;2 programming questions at this point:&lt;BR /&gt;&lt;BR /&gt;1. what does this mean:&lt;BR /&gt;#define H264ENC_UNREFERENCED_PARAMETER(X) X&lt;BR /&gt;&lt;BR /&gt;2. Why every time I run the code, for function calls it automatically goes into PIXBITS==8, rather than 16, is it because the following header is onlycalled once?then how can I step into the 16 case?&lt;BR /&gt;&lt;BR /&gt;#define PIXBITS 8&lt;BR /&gt;#include "umc_base_bitstream_tmpl.h"&lt;BR /&gt;#undef PIXBITS&lt;BR /&gt;&lt;BR /&gt;#if defined (BITDEPTH_9_12)&lt;BR /&gt;&lt;BR /&gt;#define PIXBITS 16&lt;BR /&gt;#include "umc_base_bitstream_tmpl.h"&lt;BR /&gt;#undef PIXBITS&lt;BR /&gt;&lt;BR /&gt;#endif // BITDEPTH_9_12&lt;BR /&gt;&lt;BR /&gt;Thanks for any help and hint!&lt;BR /&gt;&lt;BR /&gt;Best &lt;BR /&gt;R</description>
      <pubDate>Wed, 11 Mar 2009 21:38:20 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/ipp6-0-h264-encoder-code-review/m-p/882172#M10327</guid>
      <dc:creator>sarading32</dc:creator>
      <dc:date>2009-03-11T21:38:20Z</dc:date>
    </item>
    <item>
      <title>Re: ipp6.0 h264 encoder code review</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/ipp6-0-h264-encoder-code-review/m-p/882173#M10328</link>
      <description>&lt;DIV style="margin:0px;"&gt;Hello,&lt;BR /&gt;&lt;BR /&gt;I have the same problem like you. I want to review the h.264 code but its very complicated.&lt;BR /&gt;&lt;BR /&gt;I tried to use Doxygen to generate some helpful HTML meta-data, but unfortunately, the IPP comments dont follow the Doxygen recommendation. Please, my question is what steps youre following to understand the code?&lt;BR /&gt;&lt;BR /&gt;Thanks.&lt;/DIV&gt;</description>
      <pubDate>Fri, 13 Mar 2009 21:33:38 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/ipp6-0-h264-encoder-code-review/m-p/882173#M10328</guid>
      <dc:creator>transcoding</dc:creator>
      <dc:date>2009-03-13T21:33:38Z</dc:date>
    </item>
    <item>
      <title>Re: ipp6.0 h264 encoder code review</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/ipp6-0-h264-encoder-code-review/m-p/882174#M10329</link>
      <description>1. This only serves to remove a common compiler warning such as "parameter foo is not referenced".&lt;BR /&gt;An exemple would be void function(int foo) { }, which could also be fixed by void function(int /*foo*/) { }&lt;BR /&gt;&lt;BR /&gt;2. The H.264 encoder is implemented using C++ templates. The algorithms are implemented on a type, T, which is defined later. T could be 'unsigned char' or 'unsigned short', in the same way that you have std::vector&lt;CHAR&gt; or std::vector&lt;SHORT&gt;. Instead of implementing both function(char) and function(short), you implement template &lt;TYPENAME t=""&gt; function(T), and then the proper version is called depending on the argument. For the H.264 encoder, this allows support for 8-bit images and 16-bit images without copy-pasting common code. With templates, code is lazilly compiled only if it's used, so you won't end up with function(int) if you don't need a 32-bit version. umc_base_bitstream_tmpl.h is included twice to tell it to force compilaton of both 8-bit and 16-bit versions (template instantiation).&lt;BR /&gt;&lt;/TYPENAME&gt;&lt;/SHORT&gt;&lt;/CHAR&gt;</description>
      <pubDate>Sat, 14 Mar 2009 06:20:59 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/ipp6-0-h264-encoder-code-review/m-p/882174#M10329</guid>
      <dc:creator>Martin_B_4</dc:creator>
      <dc:date>2009-03-14T06:20:59Z</dc:date>
    </item>
  </channel>
</rss>

