Hello. I also had a problem with the startup taking a long time. I couldn’t find a solution for a long time. Installing the latest version of Microsoft Visual C++ Redistributable AIO helped
Hope it works for you
Following a fresh boot up, PL 7.6 Elite (with FP and VP) takes 2min 37s to start on my Windows laptop (Dell, with Intel i7 12700H, 16Gb memory, 512Gb SSD, Nvidia GeForce RTX 3050 (Studio driver), Windows Defender anti-virus).
On my Mac Mini M1 with 8Gb memory the same version of PL takes a few seconds.
Images are loaded off an external SSD. Both systems use the same SSD.
Honestly, PL takes so long to load on my Windows laptop that I have to often remind myself that it takes this long and that the app hasn’t crashed.
That’s unfortunate, but its not normal performance. I have an old i7 6700 desktop PC and from the time I click on the icon until it is ready for editing PhotoLab start up is around 12-15 seconds. Something on your machine is causing a roadblock.
Mark
I understand that you’re frustrated, Erwin - but, by not directly answering user-forum members’ questions, you’re not helping others in their attempts to help you.
- Are you saying, that when PL starts up, it is addressing RAW files on an SD card ? (!)
If so, try moving your RAW files into a folder on permanent storage, and start PL from there.
3 Likes
I would agree that you should open a support ticket. I also think that Photolab takes a long time to load on my windows machine, but nowhere near 7 minutes.
OpenCL is a form of GPU acceleration. If you look in your preferences of Photolab, there should be a setting to activate or deactivate it. What happens if you deactivate it, does it improve the startup time?
1 Like
It is really strange I have a very similar configuration (besides RTX4060Ti) and the start up of DxO 7 is just a few seconds. To be honest in my old and much, much slower machine the start was not so very long either…
FWIW
My PC has an i5 CPU with 16GB of ram and the RTX 3060 graphics card. So, on paper less powerful than yours.
I too have SSD’s installed for both the operating system & my programs but all my image files are on HDDs
I never start PL with the SD card in the reader…I always copy the image files into the dated and named folder structure that have on my data HDDs. And then open PL to edit as needed.
Can you please clarify which nVidia driver are you using, is it the Gamer or Studio version and which version number are you using? FWIW mine is version 551.86 Studio not Gamer.
You, I surmise are aware that the recommendation is to ensure that you install the most up to date driver version.
I timed my launch to user interface opening and it takes approximately 8 seconds.
PS I hope that PL support can throw more light on your apparently unique issue.
It takes 12 to 15 seconds for PhotoLab on my Windows 10 i7 6700 from 2016 to completely load. This hasn’t changed much going back all the way to PhotoLab 1 in 2017. Loading is slightly slower than it was for PL 1 which took no more than 10 seconds. Many regulars here have startup times consistent with mine. I suspect those who are seeing very significantly longer startup times for PhotoLab are running into a roadblock exacerbated by something interacting with PhotoLab’s loading process. What that may be I cannot say.
Matk
If raw files are on a SD card, there is no need for further investigation: it is obviously the problem as PL doesn’t import anything and uses the media containing the raw files.
2 Likes
Might this be because you are using a Windows computer, with an Intel CPU?
My Mac mini (intel chip) was pathetically slow about so many things. But my MacBook Pro with M2 chip blazed right through them.
Processing one image on the Mac mini took up to two minutes.
On the MacBook Pro, it is almost instant.
Exporting images feels instantaneous.
Just a thought.
Does your computer have a graphics processor?
It highly unlikely that is the cause of @erwind’s slow start up. My Windows PC is ancient, it only has a 3rd generation Intel Core i5 CPU and a very old Nvidia GTX 1050i graphics card yet it loads PL in less than 30 seconds.
Mike,
I have been using The Windows version of PhotoLab on my Windows 10 i7-6700 desktop for the past six and a half years. Over the years, using the various versions of PhotoLab, loading has always taken between 10 and 15 seconds. Since I generally start-up PhotoLab at least a few times a day, almost everyday, that adds up to several thousand starts and the timing is always consistent.
By the way, while asking about the graphics card would seem to be a reasonable question, please bear in mind the graphic card’s GPU is not used during start-up so the installed card will have no affect on the timing. The GPU is only used for DeepPRIME and DeepPRIME XD in PhotoLab. It is also used for DeepPRIME XD2 in PureRAW 4.
Mark
1 Like
Plus 1 on the timings on older builds!
Prior to my current build I used my 1st Gen i5 Quad Core with 16GB RAM and like you the GTX1050Ti and no SSDs all HDDs
PL launch took around 45 seconds
A good and valid point re the GPU, however if there is any interoperability involving the GPU when PL starts up something might still be going on there.
I note that @Erwind says in the log Open CL says it has taken 4 minutes to start but on my PC whether Open CL Is “on” in the preferences or not mine launches within approx 8 seconds.
Over the years, with ‘Open CL’ selected or deselected, it never seemed to have any noticeable impact on startup or general performance.
Mark
As I already advised you, just update Microsoft Visual C++ Redistributable AIO. This should work
No, you didn’t advise me (@stuck) as I don’t have a slow start up problem. I presume your post advising updating the MS Visual C++ Distributable was for the original poster. However, his last post indicates he left the forum before you made your post.
You are right, I was hasty with my answer and missed. I apologize if I disturbed you.
Mmmmm - - No further engagement by @Erwind … I’m guessing he was embarrassed to find that one of the simple suggestions made to him turned out to be correct !
Sadly none of the suggestions in this thread have solved this problem for me.
I’m currently engaging with DxO Support, so fingers crossed we can find a cause and solution.