It seems clear that on some HW/SW configurations, RT GTK3 suffers from slowness (when starting, switching) whereas on other configuration there is no problem.
On my PC tower (I7 6700K, motherboard Z170A, 16GB DDR4, SSD) which is not blazing fast, Starting time is about 2s, and I cannot reproduce the above lag with 10 edit windows opened.
Why such different behaviour?
1 Like
I agree! But: rt 5.0 gtk2 unfortunately cannot handle compressed RAF from an X-Pro2. 
Is there – or will there be an rt 5.4/gtk2 from Windows 
?
Have fun!
Claes in Lund, Sweden
Yes that what I did. To be sure, I repeated the test with 4 images in METM.
For each image the 2 tools are expanded with a correction for each image, manual or auto.
I minimize the RT window, go in other apps , expand the RT window.
There is surely a lag, but unnoticable in normal use. All adjustments react normally.
Thank you very much for the options file. Now I know why you can’t reproduce the lag.
It’s the theme. You use ‘TooWaGrey - Average Surround’, which is fast. I used the default ‘Rawtherapee’ theme, which is slow. Now we need to find out, why ‘TooWaGrey - Average Surround’ is so much faster.
ping @TooWaBoo
2 Likes
GTK3 UI rendering performance should be significantly improved in commit UI rendering performance improved · Beep6581/RawTherapee@b626b4e · GitHub available now in the dev branch.
2 Likes
1000 kudos for this :)))
In the TooWaBlue theme text-shadow has always been off. I never noticed a speed difference between the TooWaBlue and RawTherapee theme.
1 Like
That may be a reason your themes have been faster…
Would removing unneeded dcps and icc profiles also help, or is there something special about lensfun?
If you want to test
RawTherapee_dev_5.4-412-gb626b4e98_WinVista_64.zip
uploaded at
https://keybase.pub/gaaned92/RTW64NightlyBuilds/
1 Like
I changed skin to TooWaBlue also. Seems to help indeed.
I was having issues with running the program and tried changing the editor mode in the preferences/general tab to Single Editor Tab Mode and Multi Editor tabs mode and it sped things up a lot for me. It is usable for me now. Not sure if I missed someone trying this above. I am new here and the program.
Hi Chris and welcome!
What kind of RAW files are you working with? Could it, for instance, be compressed RAFs from a Fuji?
Operating system, computer, CPU, RAM, &c?
Have fun!
Claes in Lund, Sweden
Thanks Claes,
I am working with DNG’s from Pentax.
I am using an older HP dv7 notebook with the following specs.
Windows 10
i7-2630QM @ 2.00 GHz (8 cpus)
16gb ram
intel HD 3000 and AMD 6770m switchable graphics (I have the program set to run with the 6770m)
SSD + HHD hard drives
Spontaneously, the CPU sounds being on the slow side.
Ping @Morgan_Hardwood: who might be our resident
Windows tuning expert?
Have fun!
Claes in Lund, Sweden
Also: what version of RawTherapee, please?
/Claes
The decoding of compressed Fuji RAF should be very fast because it’s one of the few raw decoders which is multithreaded (Sony ARW and floating point dng decoders are also multithreaded). Of course that’s only the case if the compressed raf is loaded from a fast storage medium like SSD. If the compressed raf is loaded from a slow hard disk or from a network drive, the multithreading of compressed raf decoding will have no positive influence on decoding speed.
From this statement it is not clear to me whether you changed from single to multi editor tabs mode or vice versa. Single Editor Tab Mode should be faster though.