<?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 Managed to get this working, in Intel® Integrated Performance Primitives</title>
    <link>https://community.intel.com/t5/Intel-Integrated-Performance/Resize-Image-using-ROI-Processing/m-p/1095844#M25029</link>
    <description>&lt;P&gt;Managed to get this working, mostly. &amp;nbsp;Seems the 'get ROI' functions are for the 'Intel tiled image' use case. &amp;nbsp;For my use case the functions only return {0, 0} origin and offset. &amp;nbsp;If I use my own offset added to the source image pointer I can crop the source image as needed. &amp;nbsp;Still have some issues with the U and V planes in specific scenarios but this is likely a bug in my calculations.&lt;/P&gt;

&lt;P&gt;Feel free to close this.&lt;/P&gt;</description>
    <pubDate>Fri, 04 Mar 2016 11:32:06 GMT</pubDate>
    <dc:creator>Bob_Kirnum</dc:creator>
    <dc:date>2016-03-04T11:32:06Z</dc:date>
    <item>
      <title>Resize Image using ROI Processing</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/Resize-Image-using-ROI-Processing/m-p/1095843#M25028</link>
      <description>&lt;P&gt;I've been trying to update our video tiling (for displaying multiple input images in a single output image) implementation to support a particular scenario. &amp;nbsp;Simply put, I need to resize an input image of arbitrary dimensions / aspect ratio into a region &lt;SPAN style="font-size: 13.008px; line-height: 19.512px;"&gt;(also of arbitrary dimensions / aspect ratios and position in the destination image)&amp;nbsp;&lt;/SPAN&gt;of an output / destination image &lt;SPAN style="font-size: 13.008px; line-height: 19.512px;"&gt;(also of arbitrary dimensions / aspect ratios)&lt;/SPAN&gt;. &amp;nbsp;We have had much of this working for sometime with one key limitation, we have not tried cropping the source image. &amp;nbsp;The existing functionality works even after upgrading a while back to the newer ippiResizeNearest API.&lt;/P&gt;

&lt;P&gt;I am now struggling to allow for cropping of the source image such that it fits into the destination region, maintaining the source image aspect ratio. &amp;nbsp;Let's say, for example, the source image is 720p, the &amp;nbsp;destination image is also 720p, and the destination region within the destination image is VGA (or something smaller with similar aspect ratio). &amp;nbsp;Since 720p is wider than VGA I want to crop the left and right of the source image and resize to fit into the region. &amp;nbsp;As far as I can tell, the only use case close to this has to do with tiling an image into n smaller images and resizing these tiles individually. &amp;nbsp;Seems more to enable parallel processing of the tiles.&lt;/P&gt;

&lt;P&gt;Anyway, I have all the details needed for the source / destination ROI, source / destination offsets, etc., but the&amp;nbsp;ippiResizeNearest (nor any other resize API I have found) does not accept the source offset, just the width / height of the ROI. &amp;nbsp;Is there something I am missing here? &amp;nbsp;I believe this was pretty easy to implement using the old 'resize square pixel' API. &amp;nbsp;The documentation seems to indicate the source ROI is driven off the destination ROI and you must retrieve the ROI and offsets with a 'get' API.&lt;/P&gt;

&lt;P&gt;Given a simple example . . .&lt;/P&gt;

&lt;P&gt;Source image 1280x720&lt;/P&gt;

&lt;P&gt;Output image 1280x720&lt;/P&gt;

&lt;P&gt;Region in output image 600x360&lt;/P&gt;

&lt;P style="font-size: 13.008px; line-height: 19.512px;"&gt;Source ROI IppiRect {40, 0, 1200, 720} (x, y, w, h) - takes the center 1200 pixel width and full height&lt;/P&gt;

&lt;P style="font-size: 13.008px; line-height: 19.512px;"&gt;Destination ROI IppiRect {?, ? 600, 360} (x, y, w, h) - scales the cropped source by half and places in region (wherever it is located in destination image)&lt;/P&gt;</description>
      <pubDate>Wed, 02 Mar 2016 20:32:43 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/Resize-Image-using-ROI-Processing/m-p/1095843#M25028</guid>
      <dc:creator>Bob_Kirnum</dc:creator>
      <dc:date>2016-03-02T20:32:43Z</dc:date>
    </item>
    <item>
      <title>Managed to get this working,</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/Resize-Image-using-ROI-Processing/m-p/1095844#M25029</link>
      <description>&lt;P&gt;Managed to get this working, mostly. &amp;nbsp;Seems the 'get ROI' functions are for the 'Intel tiled image' use case. &amp;nbsp;For my use case the functions only return {0, 0} origin and offset. &amp;nbsp;If I use my own offset added to the source image pointer I can crop the source image as needed. &amp;nbsp;Still have some issues with the U and V planes in specific scenarios but this is likely a bug in my calculations.&lt;/P&gt;

&lt;P&gt;Feel free to close this.&lt;/P&gt;</description>
      <pubDate>Fri, 04 Mar 2016 11:32:06 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/Resize-Image-using-ROI-Processing/m-p/1095844#M25029</guid>
      <dc:creator>Bob_Kirnum</dc:creator>
      <dc:date>2016-03-04T11:32:06Z</dc:date>
    </item>
  </channel>
</rss>

