<?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: depth quality for D435 in Items with no label</title>
    <link>https://community.intel.com/t5/Items-with-no-label/depth-quality-for-D435/m-p/516518#M6801</link>
    <description>&lt;P&gt;Can you tell me please if you are starting and stopping the camera repeatedly, and the quality is getting worse and worse each time?  I ask this question because the current version of the RealSense SDK 2.0 has a "memory leak" bug in it. It is referred to in the SDK's release notes as follows:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;B&gt; Memory leak when repeatedly closing and opening the device (DSO-8362)&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Memory leaks cause performance to degrade over time, because the computer's memory is not being released correctly when a process is closed and so over time, more and more of the computer's memory gets used up, leaving less resources for programs to use.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This memory leak bug will likely be fixed soon, perhaps in the next release of the SDK.  In the meantime, if you are experiencing a memory leak then the memory can be restored to normal by rebooting the computer.&lt;/P&gt;</description>
    <pubDate>Wed, 28 Feb 2018 13:34:32 GMT</pubDate>
    <dc:creator>MartyG</dc:creator>
    <dc:date>2018-02-28T13:34:32Z</dc:date>
    <item>
      <title>depth quality for D435</title>
      <link>https://community.intel.com/t5/Items-with-no-label/depth-quality-for-D435/m-p/516517#M6800</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I received a D435 to evaluate last week.&lt;/P&gt;&lt;P&gt;At first, the depth accuracy was acceptable..as following shows..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;then the depth quality degrades gradually... the point cloud is really uneven. and the reconstruction result looks like this...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I checked the depth quality using the Depth.Quality.Tool.exe provided and have uploaded the saved report to the following link.&lt;/P&gt;&lt;P&gt;&lt;A href="https://drive.google.com/file/d/1BBajoQzVXNtTeKvvBn3xC59MI5kdm8Y7/view?usp=sharing"&gt;https://drive.google.com/file/d/1BBajoQzVXNtTeKvvBn3xC59MI5kdm8Y7/view?usp=sharing&lt;/A&gt; &lt;A href="https://drive.google.com/file/d/1BBajoQzVXNtTeKvvBn3xC59MI5kdm8Y7/view?usp=sharing"&gt;https://drive.google.com/file/d/1BBajoQzVXNtTeKvvBn3xC59MI5kdm8Y7/view?usp=sharing&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could you help check what is the issue? is it a hardware problem?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Faye&lt;/P&gt;</description>
      <pubDate>Wed, 28 Feb 2018 11:18:13 GMT</pubDate>
      <guid>https://community.intel.com/t5/Items-with-no-label/depth-quality-for-D435/m-p/516517#M6800</guid>
      <dc:creator>jli84</dc:creator>
      <dc:date>2018-02-28T11:18:13Z</dc:date>
    </item>
    <item>
      <title>Re: depth quality for D435</title>
      <link>https://community.intel.com/t5/Items-with-no-label/depth-quality-for-D435/m-p/516518#M6801</link>
      <description>&lt;P&gt;Can you tell me please if you are starting and stopping the camera repeatedly, and the quality is getting worse and worse each time?  I ask this question because the current version of the RealSense SDK 2.0 has a "memory leak" bug in it. It is referred to in the SDK's release notes as follows:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;B&gt; Memory leak when repeatedly closing and opening the device (DSO-8362)&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Memory leaks cause performance to degrade over time, because the computer's memory is not being released correctly when a process is closed and so over time, more and more of the computer's memory gets used up, leaving less resources for programs to use.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This memory leak bug will likely be fixed soon, perhaps in the next release of the SDK.  In the meantime, if you are experiencing a memory leak then the memory can be restored to normal by rebooting the computer.&lt;/P&gt;</description>
      <pubDate>Wed, 28 Feb 2018 13:34:32 GMT</pubDate>
      <guid>https://community.intel.com/t5/Items-with-no-label/depth-quality-for-D435/m-p/516518#M6801</guid>
      <dc:creator>MartyG</dc:creator>
      <dc:date>2018-02-28T13:34:32Z</dc:date>
    </item>
    <item>
      <title>Re: depth quality for D435</title>
      <link>https://community.intel.com/t5/Items-with-no-label/depth-quality-for-D435/m-p/516519#M6802</link>
      <description>&lt;P&gt;nope, I am pretty sure this is not a memory leak problem. I didn't repeatedly close and open the device. Even I restart the system, and the depth quality is till not good.&lt;/P&gt;</description>
      <pubDate>Thu, 01 Mar 2018 03:50:34 GMT</pubDate>
      <guid>https://community.intel.com/t5/Items-with-no-label/depth-quality-for-D435/m-p/516519#M6802</guid>
      <dc:creator>jli84</dc:creator>
      <dc:date>2018-03-01T03:50:34Z</dc:date>
    </item>
    <item>
      <title>Re: depth quality for D435</title>
      <link>https://community.intel.com/t5/Items-with-no-label/depth-quality-for-D435/m-p/516520#M6803</link>
      <description>&lt;P&gt;May I ask please if the location where you are doing the scan has fluorescent lighting (like ceiling strip-lights)?  This has been shown to have a negative effect on RealSense depth scans because fluorescent lights flicker at a rate that cannot be seen easily by the human eye and can create noise in the depth image.&lt;/P&gt;</description>
      <pubDate>Thu, 01 Mar 2018 09:13:22 GMT</pubDate>
      <guid>https://community.intel.com/t5/Items-with-no-label/depth-quality-for-D435/m-p/516520#M6803</guid>
      <dc:creator>MartyG</dc:creator>
      <dc:date>2018-03-01T09:13:22Z</dc:date>
    </item>
  </channel>
</rss>

