Same trouble it seems: https://pixls-discuss.s3.dualstack.us-east-1.amazonaws.com/original/3X/7/3/7366e8e2e49d9c8e286b1db87b7f309758a40012.mp4
Is this an iMac with 4K or 5K display?
I’ve got the following specs:
Screen: Retina 4K, 21.5-inch
Processor: 3,6 GHz Intel Core i7
Memory: 16 GB 2400 MHz DDR4
An (I guess) 4 core/8 HT Intel is not the best solution for RT on a 4K display. Preview processing time in RT increases with number of pixels in preview.
Though it would be interesting to see how an RT mac build optimized for newer cpus performs. Maybe @HIRAM can make an I7 build to check or at least a build which supports FMA and AVX (that would also include SSE4 automatically).
In my tests a native windows build for my AMD FX8350 performes much better than a generic build which is restricted to SSE2 features.
no problem except I’m overseas until March 21, and I unplugged my build machine, but I can definitely take a look when I get home. Looking at the screencast… what is acting sluggish? Is it being sluggish relative to another system’s performance?
No need to hurry. I also don’t see a really sluggish behaviour in the video.
4k in your case probably means 4096x2304 according to some Apple website. Based on your video, RawTherapee in your case is working with a 2440x1628 preview size, or almost 4 megapixels.
I have a 1920x1080 screen, my preview size is 1215x815 or 1 megapixel.
As @heckflosse already pointed out, the preview size is roughly proportional to the preview processing time. Your system has to crunch 4 times as many numbers as mine does.
You have an i7 3.6GHz CPU and 4 megapixels to process, while I have a 0.9GHz CPU and 1 megapixel, so comparing the two is not straightforward, but it seems the lag between an event and the preview updating in your video is more or less what would be expected.
Lightroom uses the GPU for some operations, and RT does not (yet).
Side-note: number-crunching aside, using KDE feels much faster on this slow CPU than it did on my previous i7 CPU, I’m guessing that’s to do with the newer instruction set extensions supported by this CPU and by the SSD disk.
2 Likes
I guess you also use a native build of RT
Really? There is at least half a second of delay every time I press a button or pull on a slider. Perhaps it is really not so bad, or it may not transfer well to video. It may also perhaps be unreasonable to expect more responsive behavior, but it feels awkward and sluggish to work with.
This sounds sensible to me. I don’t notice much difference, however, when I reduce the preview window (se video).https://pixls-discuss.s3.dualstack.us-east-1.amazonaws.com/original/3X/a/9/a90e15f774a7292b711e10a61b3a5c2fbf4582e9.mp4
It’s hard to tell what you’re seeing because your video is very jerky, maybe your system is incapable of recording a smooth video at 4k.
Try setting both AdjusterMinDelay and AdjusterMaxDelay to 0 (while RT is closed).
Hi I have the same issue. Brand new iMac retina 5K, 27inch 2017, 4,2 GHz Intel Core i7, 40 GB 2400 MHz DDR4, Radeon Pro 575 4096 MB
Opening pictures takes about 1,5 seconds, scrolling through the folders is quite slow also. I could live with that but when I use the sliders there is a serious delay between the movement of the mouse and the actual slider. Up to a point that it’s very difficult to work and almost impossible to be precise. This is a real bummer because I really wanted to use RT. I haven’t found any solutions anywhere. Nothing worked for me.
I recently downloaded Capture1, the free trial, and that works much smoother. Is the problem due to the 5K 27 inch screen? Is there no way RT will work smooth on a 27 inch 5K iMac?
I have an SSD and was convinced this iMac would have no issues with any photography software. I had Lightroom on my previous iMac 21 inch and that worked very smooth, no delay whatsoever.
I’m quite disappointed having spent almost 3000€ on a computer that’s now slower then my old one…
1 Like
Have you tried the dev branch build? Also which macos version?
I dont know if it’s related, but I experience similar problems with darktable and other gtk software on Mac OS. I tried 10.13,10.14 my hackintosh and an original MacBook, and the Ui is always very slow and unresponsive.
Running dark table the same specs on my hackintosh under windows or Ubuntu 18.04 it is much faster. On Ubuntu it really flies.
To isolate the problem a bit:
- As @HIRAM wrote, use the latest development build when testing,
- Change your screen resolution to 1920x1080 and test. (i.e. do not just resize the RT window to 1920x1080 because then you’re still running at 4k or whatever)
- If you can reproduce the problem at a screen resolution of 1920x1080, record a 30fps video and upload it here.
I have the a slightly lower end model of iMac (27in 5K, 3.4Ghz core i5, 16GB ram, Radeon Pro 570) and RT is super slow on it. I just timed it with a stop watch. RT takes 14.45 seconds to open. When I grab the exposure slider and move it to the right it takes a second or more for the slider to catch up to where the mouse pointer has moved.
On my other computer, an old windows 10 machine with an AMD FX 8350, 32GB of ram, and a 1920x1080 monitor, RT is much faster. The sliders move in conjunction with the mouse pointer. The program opens in just a few seconds. It’s like a totally different program.
I’ve tried most of the suggestions in this thread to make it faster on the iMac. Lowering the screen resolution helps a little but RT is still far too slow. This is with both 5.5 and 5.6.
Output quality from RT seems to be at an all time high though. It’s excellent.
Have you tried the dev branch build? Also which macos version?
It’s been this way in both macOS 10.14.4 and 10.14.5 and with both RT 5.5 and 5.6. The dev branch is not noticeably faster.
I assumed that RT was slow on my old iMac, a 2013 model, because everything was slow on it. But, RT feels about the same on the new machine as it did on the old machine while the other programs I use are significantly faster.
The video is not jerky on this side. I think what you are interpreting as a jerky video is the sluggish rawtherapee behavior that I am trying to demonstrate.