![]() I hope that split is appreciated and could be implemented? I would like to open a new topic on for casual talk, awareness and share experiences, while keeping this issue here for the developers and solution oriented topics. darktable 2.7.0+1087~g7fe35d67d (found it time ago already).Platform (please complete the following information): It might be, we find either something totally different (anything else might influence the UI) or a hardware related issue. ?), that just now stated in #2064, for him, the 2.7 is way more responsive than 2.6.2 I don't want to misapply (correct word acc. (see section Expected behavior)īeing not slower, "laggier" than 2.6.2, ideally even faster, more responsive than 2.6.2 The lag I "feel" (until screen gets updated), seems actually even harder than the values I found here. in the WB-Chart I have marked some obvious findings, where in the other sheets, for "efficiency" reasons, merely marked the most obvious oneįrom there you can see, that dt-2.7 (at least here) responds way slower in total, than 2.6.2, while the single actions, they seem to be faster.In coloumn "B" I placed a formular like =B12-B11 in order to have the used time per step.In coloumn "A" I put a formular like =D11-$D$11 in order to eliminate the offset and have a relative time.All those I have done and concluded in attached.repeat 1-5 with tonecurve Gamma 0.5 and Zoom from 200% to fit2screen.Change WB from 2000 to 25000 (copy the relevant lines from log).(pixelpipe merely has sharpen, rotation and basecurve).(play raw, red tulips by pphoto CC-BY-NC 4.0) double preview triggered when zooming in #2064.High CPU load even opencl is working #2404.This bug report, from my point of view (and I might be wrong), tries to comprehend: I think it is a bit complex and even I tried to be narrow, the report got a bit longer (also there is always a risk, I do make mistakes in English) Please read this entirely, before you draw your conclusion. official 2.6.2, which makes it feel very sticky on my side. However the implementation of them would not be a trivial change, I fear.According to my observation, we do have a more than noticeable performance issue for darkroom in git-master vs. I, too, think that the various floating windows of GIMP which would allow for the tools in the sidebars to be positioned at will and the photo-edit to take up the whole of one monitor would be a very helpful option for some, but not according to the taste of everyone. I know that, even when set to the same temperature my monitors (both by the same manufacturer) appear to have subtle differences. Since I haven’t taken the time or expense to colour-manage that wouldn’t trouble me. One of the issues raised was that even with colour-managed hardware and two identical model monitors, you may get inconsistent results. Others may remember exactly where and when. Then I collapse the left-hand side-panel where possible - this gives me almost the whole left monitor for the image. ![]() One thing I have done is to stretch the darktable window so that it is mostly on the left monitor, and the right-hand side panel is on the right hand monitor. I have two nearly identical monitors - one 27" and one 28" - that have identical physical screen height, so they work very well alongside one another. ![]() Hey there is something I have also wanted off and on. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |