<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated on Fri, 25 May 2012 13:06:56 -0700 -->
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <atom:link href="http://software.intel.com/en-us/articles/mpeg4-decoding-crash-occasionally/feed/" rel="self" type="application/rss+xml" />
    <title>Intel Software Network Comments Feed</title>
    <link>http://software.intel.com/en-us/articles/mpeg4-decoding-crash-occasionally</link>
    <description></description>
    <language>en-us</language>
    <item>
      <title>By mdaoud</title>
      <description><![CDATA[ Is this problem found in IPP 6.1 UMC samples as well? ]]></description>
      <link>http://software.intel.com/en-us/articles/mpeg4-decoding-crash-occasionally/#comment-39452</link>
      <pubDate>Wed, 17 Feb 2010 11:32:26 -0800</pubDate>
      <guid isPermaLink="true">http://software.intel.com/en-us/articles/mpeg4-decoding-crash-occasionally/#comment-39452</guid>
    </item>
    <item>
      <title>By Ying H (Intel)</title>
      <description><![CDATA[ Hello, 
As I recalled, the problem is reported in IPP 5.3 update 3. The problem is produced by SSE instruction itself, which required 128 bit data chunk. It is not a bug, so we haven't fixed it in function ippiDecodeDCIntra_MPEG4 internal and provide workaround to pad the input data by several zero bytes at that time. I guess, the problem should be still in IPP 6.1. What is your problem? You may add more information by IPP forum <<http://software.intel.com/en-us/forums/intel-integrated-performance-primitives/>>

Regards,
Ying
     ]]></description>
      <link>http://software.intel.com/en-us/articles/mpeg4-decoding-crash-occasionally/#comment-39533</link>
      <pubDate>Sat, 20 Feb 2010 02:14:55 -0800</pubDate>
      <guid isPermaLink="true">http://software.intel.com/en-us/articles/mpeg4-decoding-crash-occasionally/#comment-39533</guid>
    </item>
  </channel></rss>
