-start rawtherapee-cli.exe goes so fast, I can’t time it. So instantly.
-when I freshly reboot my system, rawtherapee takes indeed about 8 seconds to start and when I click for the ‘preferences’ button, it takes another 2 seconds for it to respond.
-closing and starting rawtherapee again, after initial start, takes about 6 seconds. (everything from cache)
BUT when my system is up & running for a few hours, a initial start of rawtherapee (yes, I do also other stuff on my computer ) takes the long run again. waiting, waiting, system idling, waiting, and then after approx. 50 seconds, there is rawtherapee’s GUI again. Starting rawtherapee-cli.exe is not delayed… So it seems to me, it’s something in the full blown GUI version that is waiting for something, but what?
Maybe I can try to use some sysinternal tools in order to figure if rawtherapee is delayed/hold up/waiting for something that’s not there.
to be continued…
After 15 years with MAC OS at home and as much as work, If i could have avoid all the time spent watching my computer “doing things”, I would have save years of my life ! Especially windows that is “sandglass oriented”. I still use windows at work, no choice. But at home I got read of my mac for a linux Mint : Rawtherapee 5.3 requests 7sec to launch (core i7) and combined with ArgyLL CMS and Xnview, I don’t feel like my pictures are worse than the winadobe fellows…
Many thanks for this major release that brings lens baby among improvments. I can now now definitely get read of Darktable, another excellent product by the way…
I have the same behaviour- after clicking on the Rawtherapee icon, it takes about a minute for the GUI to turn up… I use Win 10 64 bit. I did not report it because I hardly process more than couple of photos at a time and I can wait.
Probably joking, right?
I can’t reboot my system just every time I want to use RT. Nevertheless, it’s still taking much too long to start, because 7-8 seconds just to launch a program is far too long imho.
And BTW, clicking on ‘preferences’ and then still waiting for a few seconds is not normal when using your system. Especially when for all other tasks my system is very fast.
I thought RT 5.3 is getting mature and a serious piece software; so just trying to get it to work seriously should be the goal. Or am I expecting too much?
In the mean time, I have fired up Process Monitor from Sysinternals to see what RT is doing, when started. Although I filtered on just “rawtherapee” to exclude other stuff, it’s an enormous load of logging data. Where I can start searching/looking?
Certainly not. You are not a victim, period. You received something for free and you are having an issue. You have the agency to diagnose the problem and provide the information that leads to a fix.
Certainly try this, as detailed on RawPedia, gdb rawtherapee-debug.exe and r and so on, to, hopefully, see, what is going on in the background.
Consider also disabling the smartscreen evil thingy. (Hidden deeper after every Win update.)
On the Search bar, type Windows Defender Security Center.
Open Windows Defender Security Center settings and go to App & browser control.
From there, you will see the options available for Windows Defender SmartScreen.
On my system I have these options set to ‘Warn’. But even if I switch them to “Off”; it doesn’t effect RT startup time.
I’ve also tried disabling AV s/w, disabling F/W; but all to no avail.
And why should only RT behave so ‘specific’ (and slow), while all other software performs just smooth and quick. E.g. when I stitch a panorama file with PTGui Pro, stitching 20 x 60Mb TIFF files, creating several thousand temp files, sucking up 20GB of RAM, all in a few seconds. So I have no issues with the performance of my specific machine.
I’ve also read the story about debug reports for RT. But that all refers to crashes of RT. And in this case, RT doesn’t crash, it’s just slow to start…
I’m really eager to use RT as a substitute for my current RAW converter (ViewNX-i), but I’m not a programmer, just an experienced Windows photographic post processing user.
I’m not happy with the RAW conversions from the Adobe products with my NEF RAW files, because ViewNX-i does a better job. But I’m looking for more control, more finetuning, etc. and was hoping to find this with RT.
When googling the web about the slow startup issues with RT; it is clear to me, I’m not the only one. But didn’t find the holy grail (yet) as to solve this issue, before really diving deep into a new RAW converter. So I was hoping to get some assistance over here.
Are the developers/programmers reading along? (I have no idea if they do)
At least in the past, SmartScreen did “warn” me for some dev versions of RT installers, and after clicking “Allow”, the installation was still broken. PTGui is a commercial program, and even with 2.0k of clicks on the link for development build of RT for Windows, this is almost nothing, RawTherapee is an exotic outsider, suspicious, when checked against MS database. This might become worse in the future.
Even if nothing crashes, running dbg with the debug version (perhaps also setting verbose to true in options, I’m not sure about this) may show something.
The program start seems to be still slower than gtk2 version was, but on your computer, it should take about 5 seconds, at most.
Can you try to point these to an empty folder (create an emtpy folder somewhere in your file system and set the paths for flatfield and darkframe in preferences to this folder)? For reference
I don’t know whether it will be substantially faster. It’s just about excluding a possible culprit
changed C:\Program Files\RawTherapee\5.3 to D:\testing for both instances.
Where D:\testing is an empty, freshly created directory.
No changes. Same startup time.
But did you read this (previously posted)?
Changing those two dirs doesn’t change anything in RT’s startup time.
I can use RT several times with a reasonable (but still slow for a small program on a fast machine) startup time of about 8 seconds, and then suddenly it falls back to 50 seconds startup time…
Yes, I read this. I’m mainly on Win7 and the startup time of RT is between 3 and 7 seconds. 3 seconds when using METM (less gui at startup) and 7 seconds when using SETM (gui creating empty editor at startup). I agree that this could be faster!
I keep on digging into my system, to figure out why/with what RT is so busy.
Another thing I noticed, when RT is finally started, when browsing to a directory with a number of large (500MB or bigger) TIFF files, it takes a very long time before all the TIFFs are being processed/displayed, even after the ‘loading thumbnails’ message has disappeared and not all the TIFFs are already displayed.
RT is very busy with ‘Hard Faults/s’ aka paging memory. Numbers vary between 70-120 Hard Faults/sec, while at the same time Disk I/O is very low, CPU Usage is only 1-2% and committed memory usage of RT is even <2GB of RAM.
I have the option “serialize read of TIFF files” checked; but it doesn’t seem to make much difference (?)
Is there maybe a memory option for RT to use the available memory in my system (24GB RAM) instead of paging so (too?) much?
Normally I only get this kind of paging (large amounts of Hard Faults/s values) activity when I load >2GB of graphic files into PS CC 2017 with lots of layers and all the internal memory has already been used by PS CC 2017 and there is no ‘Free memory’ left anymore.
But in this case; where RT is keeping the paging memory counter busy, there is more then 20GB of RAM free!
I thought of starting the Task Manager before starting RawTherapee and checking the CPU usage and or processes. I noticed that during the time it takes to show GUI, the RawTherapee process does not show up in the Task Manager and the CPU usage does not cahnge. Does that mean that, as far as Windows is concerned, this task has not even started for the first 50 seconds or so ?
Correction: I was wrong, it does show up on the Task Manager immediately after starting it.