Announcement

Collapse
No announcement yet.

Very slow start. Why does ACDSee Photo Studio Pro 2022 need over 3 min to start up?

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

  • Very slow start. Why does ACDSee Photo Studio Pro 2022 need over 3 min to start up?

    Question to ACDSee programmers: Why does ACDSee Photo Studio Pro 2022 need 3 minutes to start up while for example FastStone Image Viewer and XnView start in less than 3 seconds on the same computer? Intel i7-9600K 3.60Ghz with 16GB RAM

  • #2
    Originally posted by fotodj View Post
    Question to ACDSee programmers: Why does ACDSee Photo Studio Pro 2022 need 3 minutes to start up while for example FastStone Image Viewer and XnView start in less than 3 seconds on the same computer? Intel i7-9600K 3.60Ghz with 16GB RAM
    3 minutes is a very long time, and the cause is most likely a local issue or a combination of things. For example Ultimate 2022 here takes only around 4 seconds from clicking on desktop icon to fully open in Manage mode (first opening after booting computer). Intel i7-10700 with 32GB RAM, database and home folder on local SSD drives, 50Mps internet, Ethernet connection to router.

    Start up delays can be due to network or internet access problems, the location, size and content of the startup folder, location and condition of the database, the use of 3rd party antivirus software, etc.

    Perhaps to narrow down possible causes you could individually try each of the following

    (a) Create a new folder on your C: drive. Place a single JPG image in that folder, and in Tools/Options/Manage Mode set the Home folder to that folder

    (b) Temporarily disable network/internet access. If your PC is Ethernet connected disable the Network adaptor, if it is wireless connected disable the wireless adapter. Note that you can't do this if your startup folder or your database are on a network drive.

    (c). If you are using 3rd party antivirus software, either try with it disabled, or whitelist ACDSee (see https://forum.acdsee.com/forum/main-...virus-software )

    Comment


    • #3
      Originally posted by fotodj View Post
      Question to ACDSee programmers: Why does ACDSee Photo Studio Pro 2022 need 3 minutes to start up while for example FastStone Image Viewer and XnView start in less than 3 seconds on the same computer? Intel i7-9600K 3.60Ghz with 16GB RAM
      Did you get resolution? It should be zippy like your other apps.

      Comment


      • #4
        I have the same issue. I was using ACDSee 12 and was happy with it except it was taking 2 1/2 minutes to load up/launch into the Manage mode. I read someplace that this problem would be addressed in an upcoming revision. So I upgraded to ACDSee Home 2023 and it STILL takes 2 1/2 minutes to load. This has to be a problem with ACDSee because NONE of my many other programs have this problem. I believe that I have wasted $45 to upgrade to a version that does nothing more for me.

        Comment


        • #5
          Originally posted by DougLock View Post
          ... This has to be a problem with ACDSee because NONE of my many other programs have this problem.
          If it was just a problem with ACDSee then my Ultimate 2021 would not be taking just 3.53 seconds from double clicking the icon to open in Manage Mode, my Ultimate 2022 would not be taking just 4.10 seconds, and my Ultimate 2023 just 3.35 seconds. All of these times are first opening following a boot up. And I have CAD packages that take way longer than this to open on the same PC.

          There are a whole lot of things that can effect start up times on individual installations. (see my post earlier in this thread).

          I suggest you contact Customer Support at https://www.acdsee.com/en/support/form/

          Comment


          • #6
            Hello,

            my Ultimate 2023 takes exactly 3 seconds to open for the first time.
            My computer: 13th Gen Intel(R) Core(TM) i9-13900KS 3.20 GHz 64.0MB Ram, Windows 11

            Previously had "loading problems" with Ultimate 2021, after uninstalling Avira the problems were gone. I also disabled face recognition and indexing.​
            Last edited by gfxtom; 06-13-2023, 01:34 AM.

            Comment


            • #7
              It takes no more than 5 seconds here - i7 processor.

              Comment


              • #8
                Intel(R) Pentium(R) Gold G5420 CPU @ 3.80GHz 3.79 GHz :

                39 seconds 1st start (after reboot), 3 seconds next.
                Last edited by brajaq; 06-14-2023, 10:46 PM.

                Comment


                • #9
                  Another comparison, older PC on same network as my current i7-10700.

                  i7-2600 Sandy Bridge CPU @ 3.79 GKHz 16GB RAM (this PC is now around 12 years old)
                  Ultimate 2020 - First start after boot up 15.5 seconds - subsequent 4.48 seconds
                  Ultimate 2022 - First start after boot up 18.5 seconds - subsequent 4.72 seconds

                  Comment


                  • #10
                    Originally posted by Greyfox View Post

                    3 minutes is a very long time, and the cause is most likely a local issue or a combination of things. For example Ultimate 2022 here takes only around 4 seconds from clicking on desktop icon to fully open in Manage mode (first opening after booting computer). Intel i7-10700 with 32GB RAM, database and home folder on local SSD drives, 50Mps internet, Ethernet connection to router.

                    Start up delays can be due to network or internet access problems, the location, size and content of the startup folder, location and condition of the database, the use of 3rd party antivirus software, etc.

                    Perhaps to narrow down possible causes you could individually try each of the following

                    (a) Create a new folder on your C: drive. Place a single JPG image in that folder, and in Tools/Options/Manage Mode set the Home folder to that folder

                    (b) Temporarily disable network/internet access. If your PC is Ethernet connected disable the Network adaptor, if it is wireless connected disable the wireless adapter. Note that you can't do this if your startup folder or your database are on a network drive.

                    (c). If you are using 3rd party antivirus software, either try with it disabled, or whitelist ACDSee (see https://forum.acdsee.com/forum/main-...virus-software )
                    I have a new Dell 8950, with lots of speed and memory and only the Windows Defender virus program - ie. no third party virus program. Face recognition was always unchecked. So I unchecked indexing. My startup speed dropped from 150 seconds to 80 seconds. Then when I disconnected my Ethernet cable from the machine the startup time dropped to 10 seconds, which I consider acceptable. Do you know if there is something I can do in the preferences, or program to disable that will keep the program from accessing the web before it starts up? Thanks, Doug

                    Comment


                    • #11
                      Originally posted by DougLock View Post
                      Do you know if there is something I can do in the preferences, or program to disable that will keep the program from accessing the web before it starts up?
                      I assume that when the application is started the first time for a given period, there is an on line licencing check, also a check for messages for the message center and the download of any new messages.

                      ACDSee Ultimate will work with the network adaptor disabled (alternative to unplugging the Ethernet cable), but I don't know for how long. It may require periodic confirmation of the licence. I've also seen suggestions of renaming ACDIntouch2.exe and ACDSee CommanderUltimate16.exe to stop them working, but I suspect there would be some loss of functionality doing that.

                      A 70 second penalty (80-10) seems way excessive for the start up on line time, given the total startup times of less than 5 seconds (including the online time) being experienced by myself and others.

                      What sort of internet service do you have?.
                      Have you tried disconnecting all devices except for your PC from your router to check whether some other network activity or device is causing a problem?

                      Comment


                      • #12
                        Originally posted by Greyfox View Post

                        I assume that when the application is started the first time for a given period, there is an on line licencing check, also a check for messages for the message center and the download of any new messages.

                        ACDSee Ultimate will work with the network adaptor disabled (alternative to unplugging the Ethernet cable), but I don't know for how long. It may require periodic confirmation of the licence. I've also seen suggestions of renaming ACDIntouch2.exe and ACDSee CommanderUltimate16.exe to stop them working, but I suspect there would be some loss of functionality doing that.

                        A 70 second penalty (80-10) seems way excessive for the start up on line time, given the total startup times of less than 5 seconds (including the online time) being experienced by myself and others.

                        What sort of internet service do you have?.
                        Have you tried disconnecting all devices except for your PC from your router to check whether some other network activity or device is causing a problem?
                        My service is Frontier fiber. I just checked the speed and it is 58 Mbps down and 61 up. Time for ACDSee to load was 82 seconds.
                        When I set my AT&T cell phone up as a hotspot I get 7.8 down and 8 up. Time for ACDSee to load was 148 seconds.
                        Disconnecting everything from my router except the computer then the load time is still about 80 seconds.
                        There just has to be something in ACDSee that is causing this. I have many programs on my computer and none of them have this issue.
                        Frustrating!

                        Comment


                        • #13
                          Originally posted by DougLock View Post
                          ..My service is Frontier fiber. I just checked the speed and it is 58 Mbps down and 61 up
                          .

                          Your interned service is comparable on download speed with my 50 Mbps HFC service here in South Australia, and better on upload (mine is only 20Mbps upload). However those figures are only the up/down speeds between you and the local server. Connection to a particular remote server in another country usually takes many hops, and it is the overall time that matters. You have indicated that start up takes only 10 seconds if you disconnect the Ethernet cable, but 80 seconds with it connected. The 70 seconds (on line via your router) difference is what is in question, particularly given the comparison overall start up times I and others have posted here in this thread.

                          I would suggest you raise the issue with Customer Support at https://www.acdsee.com/en/support/form/

                          They may be able to give you the details to conduct something like a TraceRoute from your PC to the particular server of theirs that the application connects to, and/or otherwise maybe organize a remote session with you to investigate this further.

                          Comment


                          • #14
                            I've determined that in my case slow start is directly related to the large amount of the pictures in the database catalog. When I created new catalog with no pictures in it program started in 2 seconds. After I added 50 000 pic (average picture size 1MB, jpegs) ACDSee catalog folder size grew to 300MB and start time was around 13 seconds. with 350 000 pictures , catalog folder size was 1.7GB and start time 47 sec.
                            With full database of my pictures 495000 it takes 120 seconds for the program to start. It is "so fast" only because I excluded cataloging thumbnails, turned off face detection etc. I think that with thumbnails it would've taken probably 4 minuets to start. Database is on C disk pictures are on the same disk C and no files needs access via networking.
                            Based on my tests above, in my opinion ACDSee has a serious design flaw and can not handle properly larger amount of image files. Instead of starting the program first and then loading the database in the background we need to wait for everything to load first and meantime I can take my dog for a walk to the park because the way unfortunately ACDSee starts.

                            Comment


                            • #15
                              Originally posted by Greyfox View Post
                              .

                              Your interned service is comparable on download speed with my 50 Mbps HFC service here in South Australia, and better on upload (mine is only 20Mbps upload). However those figures are only the up/down speeds between you and the local server. Connection to a particular remote server in another country usually takes many hops, and it is the overall time that matters. You have indicated that start up takes only 10 seconds if you disconnect the Ethernet cable, but 80 seconds with it connected. The 70 seconds (on line via your router) difference is what is in question, particularly given the comparison overall start up times I and others have posted here in this thread.

                              I would suggest you raise the issue with Customer Support at https://www.acdsee.com/en/support/form/

                              They may be able to give you the details to conduct something like a TraceRoute from your PC to the particular server of theirs that the application connects to, and/or otherwise maybe organize a remote session with you to investigate this further.
                              Slow startup for many (but not all) users has been a problem with ACDSee for a long time. I am sure that their programmers are well aware of it and what causes it. It must be a problem that is too complex or expensive for them to try and solve. I do not think that calling the support folks, spending hours on the phone and trying things that I have already tried will result in any solution. I have just resigned myself to live with my slow startup, though I am not very happy about it. But you are an angel for being so active on this forum and providing help and ideas to the users. Thanks for your help.

                              Comment

                              Working...
                              X
                              😀
                              🥰
                              🤢
                              😎
                              😡
                              👍
                              👎