Announcement

Collapse
No announcement yet.

Dehaze Crashes ACDsee Pro Version 10.2

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Dehaze Crashes ACDsee Pro Version 10.2

    Every time I use the Dehaze function in Develop mode it crashes my ACDsee Pro version 10.2 Build 659. Windows 10 64bit operating system. Other Devlop tools work fine. Anyone else seeing this?

  • #2
    Can you describe your computing environment a bit more completely? For example, what level of Windows 10 are you on? Can you tell us what display card you are using and how much onboard ram is on the card? How much ram is on the computer? What size are your photos? Are they jpgs or tiffs, or did they get converted from raw? Are you running other programs concurrently with ACDSee Pro?

    Comment


    • #3
      Host Name:
      OS Name: Microsoft Windows 10 Pro
      OS Version: 10.0.14393 N/A Build 14393
      OS Manufacturer: Microsoft Corporation
      OS Configuration: Standalone Workstation
      OS Build Type: Multiprocessor Free
      Registered Owner:
      Registered Organization:
      Product ID:
      Original Install Date: 9/22/2016, 7:59:09 AM
      System Boot Time: 12/15/2016, 6:38:06 AM
      System Manufacturer: Dell Inc.
      System Model: OptiPlex 390
      System Type: x64-based PC
      Processor(s): 1 Processor(s) Installed.
      [01]: Intel64 Family 6 Model 42 Stepping 7 GenuineIntel ~2800 Mhz
      BIOS Version: Dell Inc. A11, 10/14/2013
      Windows Directory: C:\WINDOWS
      System Directory: C:\WINDOWS\system32
      Boot Device: \Device\HarddiskVolume2
      System Locale: en-us;English (United States)
      Input Locale: en-us;English (United States)
      Time Zone: (UTC-06:00) Central Time (US & Canada)
      Total Physical Memory: 4,069 MB
      Available Physical Memory: 1,404 MB
      Virtual Memory: Max Size: 7,483 MB
      Virtual Memory: Available: 3,930 MB
      Virtual Memory: In Use: 3,553 MB
      Page File Location(s): C:\pagefile.sys
      Domain:
      Logon Server:
      Hotfix(s): 7 Hotfix(s) Installed.
      [01]: KB3176935
      [02]: KB3176936
      [03]: KB3176937
      [04]: KB3199209
      [05]: KB3199986
      [06]: KB3209498
      [07]: KB3206632
      Network Card(s): 1 NIC(s) Installed.
      [01]: Realtek PCIe GBE Family Controller
      Connection Name: Ethernet
      DHCP Enabled: Yes
      DHCP Server:
      IP address(es)
      [01]:
      [02]:
      Hyper-V Requirements: VM Monitor Mode Extensions: Yes
      Virtualization Enabled In Firmware: Yes
      Second Level Address Translation: Yes
      Data Execution Prevention Available: Yes

      NVIDIA System Information report created on: 01/01/2017 11:32:47
      System name:
      [Display]
      Operating System: Windows 10 Pro, 64-bit
      DirectX version: 11.0
      GPU processor: GeForce 8400 GS
      Driver version: 342.01
      Direct3D API version: 10
      CUDA Cores: 8
      Core clock: 567 MHz
      Shader clock: 1400 MHz
      Memory data rate: 800 MHz
      Memory interface: 64-bit
      Total available graphics memory: 2546 MB
      Dedicated video memory: 512 MB DDR2
      System video memory: 0 MB
      Shared system memory: 2034 MB
      Video BIOS version: 62.98.71.00.51
      IRQ: 16
      Bus: PCI Express x16 Gen2
      Device Id: 10DE 06E4 05CD196E
      [Components]
      NvGFTrayPluginr.dll 2.11.4.125 NVIDIA GeForce Experience
      NvGFTrayPlugin.dll 2.11.4.125 NVIDIA GeForce Experience
      nvui.dll 8.17.13.4201 NVIDIA User Experience Driver Component
      nvxdsync.exe 8.17.13.4201 NVIDIA User Experience Driver Component
      nvxdplcy.dll 8.17.13.4201 NVIDIA User Experience Driver Component
      nvxdbat.dll 8.17.13.4201 NVIDIA User Experience Driver Component
      nvxdapix.dll 8.17.13.4201 NVIDIA User Experience Driver Component
      NVCPL.DLL 8.17.13.4201 NVIDIA User Experience Driver Component
      nvCplUIR.dll 7.8.840.0 NVIDIA Control Panel
      nvCplUI.exe 7.8.840.0 NVIDIA Control Panel
      nvWSSR.dll 6.14.13.4201 NVIDIA Workstation Server
      nvWSS.dll 6.14.13.4201 NVIDIA Workstation Server
      nvViTvSR.dll 6.14.13.4201 NVIDIA Video Server
      nvViTvS.dll 6.14.13.4201 NVIDIA Video Server
      NVSTVIEW.EXE 7.17.13.4201 NVIDIA 3D Vision Photo Viewer
      NVSTTEST.EXE 7.17.13.4201 NVIDIA 3D Vision Test Application
      NVSTRES.DLL 7.17.13.4201 NVIDIA 3D Vision Module
      nvDispSR.dll 6.14.13.4201 NVIDIA Display Server
      NVMCTRAY.DLL 8.17.13.4201 NVIDIA Media Center Library
      nvDispS.dll 6.14.13.4201 NVIDIA Display Server
      PhysX 09.13.1220 NVIDIA PhysX
      NVCUDA.DLL 8.17.13.4201 NVIDIA CUDA 6.5.51 driver
      nvGameSR.dll 6.14.13.4201 NVIDIA 3D Settings Server
      nvGameS.dll 6.14.13.4201 NVIDIA 3D Settings Server

      Comment


      • #4
        I see also that when I try to view a GIF in the View Tab, the screen flashes white and the GIF does not display correctly. The same GIF displays fine in ACDsee's "second monitor" window. This behavior is the same no matter which monitor I use to display the GIF. Here's a link to a google GIF that displays incorrectly: https://www.google.com/doodles/matil...-99th-birthday

        Thank you for the quick response.

        Comment


        • #5
          Originally posted by billbremer View Post
          System Type: x64-based PC
          Total Physical Memory: 4,069 MB
          I'd say this isn't a good combination. Try again with at least 8GB RAM. From my experience AC is very sensitive with a lack of RAM.
          Last edited by Emil; 01-07-2017, 05:48 AM.

          Comment


          • #6
            We run ACDSee Ultimate on a PC I assembled in 2008. It’s running Windows 7 64 bit with only 4GB of DDR2 RAM. It runs in the Develop Mode very well, except for when I use the Dehaze tool - the processor goes to 100% utilization. Per Emil's suggestion, I added another 4GB of RAM from my spares box, however, that didn't fix the problem. The Dehaze tool benefits greatly from a good graphics processor unit, hence I think updating the video card would resolve my issue. So, billbremer, it could be your RAM, or the video card (on board or discrete), or perhaps try re-installing ACDSee Pro one more time.

            Comment


            • #7
              Here is a performance chart from my WIn10 box with only Ult10 and Antivirus turned on.
              System: ​4 cores, 16G Ram, 2G Video RAM

              ​The heartbeats are created by moving the DeHaze in the Develop mode. Edit mode DeHaze is similar
              These are pretty good size bumps.... even if they have enough system RAM in the sandbox , the CPU still gets hit hard. I am not sure how hard the GPUs get hit as I have no way to monitor those) I can see were this could be troublesome with a bit older hardware.

              ​Looks like your system shares system RAM with the video RAM. Combined with the 4GB to start, my guess is there some swapping and memory management going on.


              ​When you use dehaze, does the disk start spinning?
              ​(In the past I've noted a direct relationship between memory swapping and application stability. I am wondering if that is the case this time?)



              ​Of note, here is the minimum system requirements from the ACDSee website for Ult10. (For what it is worth, this does seem to be a bit low as I think Win10/7 both require a larger system than what is proposed. I wonder if there is a copy paste error in the website)

              From http://www.acdsee.com/en/support/acdsee-pro-10
              • Intel® Pentium® III / AMD Athlon processor or equivalent (Intel® Pentium® 4 / AMD Athlon XP or equivalent recommended)
              • 512 MB RAM (1 GB RAM recommended)
              • 310 MB free hard drive space (1 GB recommended)
              • High Color display adapter at 1024 x 768 resolution (1280 x 1024 recommended)

              Comment


              • #8
                I'm getting a crash every time I try to use Levels in Edit mode (Ultimate feature, 10.2). I'm pretty sure that never happened in 10.1. I've submitted steps to reproduce this and the crash logs to https://acdsystems.desk.com/customer...tal/emails/new

                ​On my PC I found the crash logs are in C:\Users\<my user id>\AppData\Local\Temp\ACDSeeCrashDumps\ACDSeeUlti mate10

                Comment


                • #9
                  FWIW, Levels in edit mode with v10.2 seem OK with my install.

                  Comment


                  • #10
                    I use ACDSee Pro on a VM (it get's 4GB RAM) because I switched to Linux and Dehaze runs very slow. I hardly use it anymore. But it works. Maybe because I still use a 6 MP camera.

                    Comment


                    • #11
                      4GB RAM is a pretty small footprint. Is it a Win10 VM? Is the slowness due to disk swap? Can you change the performance of the virtual GPU in a VM?


                      ​I found a nice GPU monitor (TechPowerUp GPU-Z).... also using the CPU monitor.... I did a couple experiments

                      Opened a RAW file in Develop mode in ACDSee...
                      ​At a medium rate, I moved the DeHaze slider left to right; right to left.. These are the changed from idle I saw when moving the slider.
                      ​GPU: ~50%, ~256MB VRAM
                      ​CPU: 60%; ~200MB

                      Opened a RAW file in EDIT mode in ACDSee...
                      ​At a medium rate, I moved the DeHaze slider left to right; right to left.. These are the changed from idle I saw when moving the slider.
                      ​GPU: ~80%, ~256MB VRAM
                      ​CPU: No Change; it's like EDIT mode does touch the CPU for DeHaze (at least on my system)

                      ​(With smaller JPG files, I couldn't see much difference)

                      ​From this, it seems there may be different hardware related bottlenecks depending on editing mode. In both cases a fast GPU seems like a really good idea. If the system has a relatively slow (and/or low RAM) GPU, I would probably stay away from DeHaze in EDIT mode.

                      Comment


                      • #12
                        Win10 was the reason to switch to linux, so it is a Win7-VM with no internet-connection. I don't know how I could change the GPU in the VM. ACDSee Pro runs reasonable fast, considering it is a VM. Just Dehaze is very slow.


                        Comment

                        Working...
                        X