RawTherapee Windows Gtk3 builds

Software RawTherapee
21

@Edward_Kiefer do you have any network drive or firewire drive set up?
In fact it would be better if you opened an issue on GitHub for that and we can continue discussions there, not to hijack this thread.

22

only got 1 HD , C: (internal WD black 500G )
Got a link to GitHub bugtracker/issue ?

I think I wait for next one just to be sure.

Edit: no need for link I see now.

23

lo

The prog is a bit faster than the old version
I’m running PA from a Ext 2.5 disk “USB 2.0” on a 7 year old Acer M5910 “64bit/8gig/GeForce405”
6 sec to start, old one needed 9 sec
“the time for PA to place the folders, it cleans them up after exit”
after closing a restart is all-most instant possible [the time you need to
], the old one needed 2 min delay
CPU usage both is 13%

editing a photo, in the new RT its all-most instant, no delay of sec. anymore

24

Hi everybody,
I installed the 4.2642 yesterday and everything looks very nice but I think I have noticed a small bug. When I expand the left side of the editor menu (navigator, curver) or the right side (processing tools) the photo “flick” because the program is “processing image/ready” constantly (every one or two seconds). When contract the left/right side menus this behaviour stop and RT works perfectly.
My OS is a Win7 64.
Kind regards,
Antonio

25

@Antonio_Lopez

This is a known bug.
see: Problem with constantly refreshing preview occuring randomly [Gtk3] · Issue #3071 · Beep6581/RawTherapee · GitHub

It happens only, when the image area is to small.

cu TooWaBoo

26

Already fixed by Hombre.

27

I confirm Hombre’s fix is working.

28

That’s great news!
Looking forward for the fixed versiĂłn.
Thanks!!
Antonio

29

I updated my Google drive with latest Gtk3 Release and Debug builds for Windows 64 bits (with Hombre’s fix) → here as always.

Branch: gtk3
Version: 4.2.670
Changeset: 1a9121714a3a8e04d09ca0cf0f237345a732d962
Compiler: gcc 5.3.0
Processor: generic x86
System: Windows
Bit depth: 64 bits
Gtkmm: V3.18.0
Build type: debug
Build flags: -m64 -mwin32 -mthreads -std=gnu++11 -mtune=generic -Werror=unused-label -fopenmp -Werror=unknown-pragmas -fopenmp -O0 -g2
Link flags: -m64 -mwin32 -mthreads -static-libgcc -mtune=generic -O0
OpenMP support: ON
MMAP support: ON
1 Like
30

Thanks, runs fine under Win 10.:+1:
Looks like the bug is fixed.

cu TooWaBoo

31

I have performed a couple of test and everything looks nice (win 7 64bits).
It seems that the bug has been fixed. :clap::clap:
Thank you for the fast solution!!
BR
Antonio

32

I tried the new version 4.2.642 and on my W7/64/ I-5 /8GB machine it was very slow to open. It would take about 60 seconds to open. Once it opened it seemed to work OK. I didn’t like waiting, so I ended up going back to the prior version 4.2.539, which on my computer opens in 3 seconds.

I also did not see in the preference menu the option to change the select theme, I miss that option, I like to use the #63 Gray-Cyan option, is it gone?

33

@rd52
Checkout this:
Github

Maybe it’s the same reason of your slow startup.

34

thanks TooWaBoo (oops it was Beep6581’s suggestion), renaming the options (as recommended in your Github suggestion) really helped. It now opens in 3 seconds, much the same as the older version.

35

New Gtk3 builds for 64-bit Windows are up there.

Branch: gtk3
Type: Release and Debug (gdb.exe within the bundle)
Changeset: 676a4441a12b30b401b9df49b976e32cba7c9b36

1 Like
36

@sguyader

Thanks, runs fine on Win 10 x64. :+1:

1 Like
37

Have downloaded WinVista_64_4.2.699 from the main site downloads page.
Runs fine on Win7.
But the bottom of the editor pane is a bit funny:

38

@mikesan,

Did you try sguyader’s (RawTherapee_WinVista_64_4.2.699-g3c016c4_gtk3.zip on Win7):

https://drive.google.com/folderview?id=0B_AvPFlUj8t5SUdodURGOFdOems&usp=drive_web#list

I am running sguyader’s and I don’t have that problem. I do get crashes from time to time.

39

Actually I think the version on the official site is my build. I don’t know what’s the problem, @mikesan what is the resolution of your display?

40

Then is gotta be display resolution or something else.