<?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 ipp 7.0 h264 decoder issues in Intel® Integrated Performance Primitives</title>
    <link>https://community.intel.com/t5/Intel-Integrated-Performance/ipp-7-0-h264-decoder-issues/m-p/784686#M1857</link>
    <description>&lt;P&gt;my
issue concerns decoding reassembled access units (complete frame) containing
more than 1 nalu.&lt;/P&gt;

&lt;P&gt;with
the previous version of ipp lib, the decoding was ok but there was crashes some
time when a nalu is lost.&lt;/P&gt;

&lt;P&gt;after
upgrading to the new ipp version, i found that almost all h264 decoder code was
changed. but when tried to test it, the first issues are:&lt;/P&gt;

&lt;P&gt;after successfully decoding the first AU (contains more than 1 NALU), the
decoder starts returning poorly decoded frames. when I looked closer, it seems
that the decoder some times can't find nalu start code!!!!. after checking my
inputs it seems that the decoder has changed the content of the input AU
probably when moving the pointer to the next nalu.&lt;/P&gt;

&lt;P&gt;&lt;/P&gt;&lt;P&gt;is
there someone experienced the same issue!&lt;/P&gt;

&lt;P&gt;thank
you&lt;/P&gt;

&lt;P&gt;&lt;/P&gt;&lt;BR /&gt;</description>
    <pubDate>Thu, 10 Mar 2011 15:49:10 GMT</pubDate>
    <dc:creator>fsabah</dc:creator>
    <dc:date>2011-03-10T15:49:10Z</dc:date>
    <item>
      <title>ipp 7.0 h264 decoder issues</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/ipp-7-0-h264-decoder-issues/m-p/784686#M1857</link>
      <description>&lt;P&gt;my
issue concerns decoding reassembled access units (complete frame) containing
more than 1 nalu.&lt;/P&gt;

&lt;P&gt;with
the previous version of ipp lib, the decoding was ok but there was crashes some
time when a nalu is lost.&lt;/P&gt;

&lt;P&gt;after
upgrading to the new ipp version, i found that almost all h264 decoder code was
changed. but when tried to test it, the first issues are:&lt;/P&gt;

&lt;P&gt;after successfully decoding the first AU (contains more than 1 NALU), the
decoder starts returning poorly decoded frames. when I looked closer, it seems
that the decoder some times can't find nalu start code!!!!. after checking my
inputs it seems that the decoder has changed the content of the input AU
probably when moving the pointer to the next nalu.&lt;/P&gt;

&lt;P&gt;&lt;/P&gt;&lt;P&gt;is
there someone experienced the same issue!&lt;/P&gt;

&lt;P&gt;thank
you&lt;/P&gt;

&lt;P&gt;&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 10 Mar 2011 15:49:10 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/ipp-7-0-h264-decoder-issues/m-p/784686#M1857</guid>
      <dc:creator>fsabah</dc:creator>
      <dc:date>2011-03-10T15:49:10Z</dc:date>
    </item>
    <item>
      <title>ipp 7.0 h264 decoder issues</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/ipp-7-0-h264-decoder-issues/m-p/784687#M1858</link>
      <description>Iamtotallywrong inmy previous descriptionof the problem.Indeed,myproblemisthat ata given timeduringthe receptionof thevideostreamwhenthereareNalus belonging toakeyframethat arelost,thedecodercrashes trying todecodethe followingNalus.thecrashoccursatseveralplaces, eginfoo_external_p where pNRefPicList0 whichisempty(containsNULL pointers).&lt;BR /&gt;&lt;BR /&gt;Icanavoidthis by for example droppingreceived Nalus til reception of the next keyframe. but this is not so good as you know: it is the responsibility of the decoder to manageandrecover&lt;BR /&gt;&lt;BR /&gt;is there aworkaround for this?&lt;BR /&gt;&lt;BR /&gt;thank youin advance</description>
      <pubDate>Mon, 14 Mar 2011 16:38:16 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/ipp-7-0-h264-decoder-issues/m-p/784687#M1858</guid>
      <dc:creator>fsabah</dc:creator>
      <dc:date>2011-03-14T16:38:16Z</dc:date>
    </item>
    <item>
      <title>ipp 7.0 h264 decoder issues</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/ipp-7-0-h264-decoder-issues/m-p/784688#M1859</link>
      <description>for more information, it seems that the decoder crashes when trying to do deblocking. there's no check if some parts of the picture aren't present (lost)&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;could anyone help fixing this issue?&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;thank you&lt;/DIV&gt;</description>
      <pubDate>Mon, 14 Mar 2011 17:10:21 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/ipp-7-0-h264-decoder-issues/m-p/784688#M1859</guid>
      <dc:creator>fsabah</dc:creator>
      <dc:date>2011-03-14T17:10:21Z</dc:date>
    </item>
    <item>
      <title>ipp 7.0 h264 decoder issues</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/ipp-7-0-h264-decoder-issues/m-p/784689#M1860</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;You may get more feedback if you provide some test data that triggers the problem(s) with an appropriate description of how to do it. From you immediate description (of post #1), it could sound as if you have run into the issue of forum thread #76615, though I have not checked if IPP v. 7.0 has already fixed this. You could check it out.&lt;BR /&gt;&lt;BR /&gt;Unless related to the issue of forum thread #76615, the second problem with crashes during deblocking as described in post #2 does sound worrying. Can you provide more information on how to reproduce it?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;- Jay</description>
      <pubDate>Thu, 31 Mar 2011 11:48:53 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/ipp-7-0-h264-decoder-issues/m-p/784689#M1860</guid>
      <dc:creator>IDZ_A_Intel</dc:creator>
      <dc:date>2011-03-31T11:48:53Z</dc:date>
    </item>
  </channel>
</rss>

