<?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 Image Processing with a negative stride? in Intel® Integrated Performance Primitives</title>
    <link>https://community.intel.com/t5/Intel-Integrated-Performance/Image-Processing-with-a-negative-stride/m-p/914352#M14785</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I've come across an urgent issue for a client while pulling images from a webcam and doing some processing on them. I call numerous image processing functions, like ippiConvert, Rgb2Gray, Norm's, etc. What I found is that jpg's read from disk in my app using vc++ come out as top-down images, with a positive stride. Processing images from disk works great.&lt;BR /&gt;&lt;BR /&gt;However, images pulled from the webcam come through as a negative stride, or bottom-up images. Can the performance primitive functions handle this? I'm guessing it should work fine, as long as the stride matches the image dimensions and color depth...&lt;BR /&gt;&lt;BR /&gt;I'm finding the output of my processing remains unchanged despite changing input images from the webcam.&lt;BR /&gt;&lt;BR /&gt;Any comments or suggestions would be appreciated.&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;Matt&lt;BR /&gt;</description>
    <pubDate>Thu, 10 Aug 2006 04:05:23 GMT</pubDate>
    <dc:creator>yaddayadda22</dc:creator>
    <dc:date>2006-08-10T04:05:23Z</dc:date>
    <item>
      <title>Image Processing with a negative stride?</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/Image-Processing-with-a-negative-stride/m-p/914352#M14785</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I've come across an urgent issue for a client while pulling images from a webcam and doing some processing on them. I call numerous image processing functions, like ippiConvert, Rgb2Gray, Norm's, etc. What I found is that jpg's read from disk in my app using vc++ come out as top-down images, with a positive stride. Processing images from disk works great.&lt;BR /&gt;&lt;BR /&gt;However, images pulled from the webcam come through as a negative stride, or bottom-up images. Can the performance primitive functions handle this? I'm guessing it should work fine, as long as the stride matches the image dimensions and color depth...&lt;BR /&gt;&lt;BR /&gt;I'm finding the output of my processing remains unchanged despite changing input images from the webcam.&lt;BR /&gt;&lt;BR /&gt;Any comments or suggestions would be appreciated.&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;Matt&lt;BR /&gt;</description>
      <pubDate>Thu, 10 Aug 2006 04:05:23 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/Image-Processing-with-a-negative-stride/m-p/914352#M14785</guid>
      <dc:creator>yaddayadda22</dc:creator>
      <dc:date>2006-08-10T04:05:23Z</dc:date>
    </item>
    <item>
      <title>Re: Image Processing with a negative stride?</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/Image-Processing-with-a-negative-stride/m-p/914353#M14786</link>
      <description>Hi Matt: &lt;BR /&gt;&lt;BR /&gt;I think negative strides are not allowed, so imo your best bet is to use the inplace mirror functions before working with the images. Alternatively, you can delay the flip until rendering/saving (e.g., blit, GL, jpeg write, etc) without overhead. Keeping track of flip-noflip versions requires diligence and might complicate things, so using the mirror operation might be faster and less error prone. &lt;BR /&gt;&lt;BR /&gt;Tilman. &lt;BR /&gt;</description>
      <pubDate>Thu, 10 Aug 2006 12:54:12 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/Image-Processing-with-a-negative-stride/m-p/914353#M14786</guid>
      <dc:creator>Intel_C_Intel</dc:creator>
      <dc:date>2006-08-10T12:54:12Z</dc:date>
    </item>
  </channel>
</rss>

