<?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: viterbi example in (Windows) 5.3.1.064 in Intel® Integrated Performance Primitives</title>
    <link>https://community.intel.com/t5/Intel-Integrated-Performance/viterbi-example-in-Windows-5-3-1-064/m-p/910168#M14051</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;if you have some specific functionality requests it would be nice to submit them to &lt;A href="http://premier.intel.com"&gt;Intel Premier Support&lt;/A&gt;, so they will be used as a input at the next IPP version planning stage.&lt;/P&gt;
&lt;P&gt;Regards,&lt;BR /&gt; Vladimir&lt;/P&gt;</description>
    <pubDate>Tue, 05 Aug 2008 17:06:30 GMT</pubDate>
    <dc:creator>Vladimir_Dudnik</dc:creator>
    <dc:date>2008-08-05T17:06:30Z</dc:date>
    <item>
      <title>viterbi example in (Windows) 5.3.1.064</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/viterbi-example-in-Windows-5-3-1-064/m-p/910166#M14049</link>
      <description>&lt;P&gt;We use viterbi decoders in multiple applications, so were looking forward to support for it in the IPP. As I understand, viterbi decoders have a 'state' parameter and a traceback 'depth' parameter. But during integration, it appears that the example is always setting the 'depth' equal to the 'state' (16, 32 or 64), thereby making the depth essentially non-configurable.&lt;/P&gt;
&lt;P&gt;I'm trying to re-work the example to make depth configurable, but am starting to wonder if this (depth = state) is a requirement of the associated IPP viterbi functions (GetVarPointDV, CalcStatesDV, BuildSymblTableDV4D, UpdatePathMetricsDV).&lt;/P&gt;
&lt;P&gt;So my questions are:&lt;/P&gt;
&lt;P&gt;Is there a way to make 'depth' configurable in the example / using the existing IPP functions?&lt;/P&gt;
&lt;P&gt;If not, is this a 'bug' in these functions? (Will it be fixed? Should I submit this as a support issue?)&lt;/P&gt;
&lt;P&gt;-Thanks in advance for any help&lt;/P&gt;</description>
      <pubDate>Fri, 28 Mar 2008 18:43:38 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/viterbi-example-in-Windows-5-3-1-064/m-p/910166#M14049</guid>
      <dc:creator>astrasel</dc:creator>
      <dc:date>2008-03-28T18:43:38Z</dc:date>
    </item>
    <item>
      <title>Re: viterbi example in (Windows) 5.3.1.064</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/viterbi-example-in-Windows-5-3-1-064/m-p/910167#M14050</link>
      <description>I was able to modify the example to specify a depth != state, so it can be done. Would be nice if Intel were to provide a more general solution.</description>
      <pubDate>Fri, 28 Mar 2008 22:40:14 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/viterbi-example-in-Windows-5-3-1-064/m-p/910167#M14050</guid>
      <dc:creator>astrasel</dc:creator>
      <dc:date>2008-03-28T22:40:14Z</dc:date>
    </item>
    <item>
      <title>Re: viterbi example in (Windows) 5.3.1.064</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/viterbi-example-in-Windows-5-3-1-064/m-p/910168#M14051</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;if you have some specific functionality requests it would be nice to submit them to &lt;A href="http://premier.intel.com"&gt;Intel Premier Support&lt;/A&gt;, so they will be used as a input at the next IPP version planning stage.&lt;/P&gt;
&lt;P&gt;Regards,&lt;BR /&gt; Vladimir&lt;/P&gt;</description>
      <pubDate>Tue, 05 Aug 2008 17:06:30 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/viterbi-example-in-Windows-5-3-1-064/m-p/910168#M14051</guid>
      <dc:creator>Vladimir_Dudnik</dc:creator>
      <dc:date>2008-08-05T17:06:30Z</dc:date>
    </item>
  </channel>
</rss>

