Hi Jo !
Thanks for your answer.
So this doesn't explain why the global colorpicker readings change
depending on the display ICC profile, nor why using a log encoding
between -2.5 and 2.5 EV, the grey gets remapped to L = 77 instead of 50.
I believe there is a gamma correction where it doesn't
It does appear that cmake requires rawspeed. I can only presume that
darktable requires it. cmake lets u know that it wants rawspeed/ anyway
someone created the cmake scripts. Anyway someone created the error
messages. It was not cmake that created them.
On 11/2/18 8:41 AM, Sturm Flut wrote:
Hi Andreas,
Am 02.11.18 um 13:23 schrieb Andreas Schneider:
> On Friday, 2 November 2018 12:58:52 CET Sturm Flut wrote:
>> Dear list,
>>
>> I guess this can also depend a lot on the hardware and the specific
>> X.Org/Mesa/GTK/driver version combinations. I've been using darktable on
>> a 4K
Hi,
Am 31.10.18 um 16:50 schrieb Postmaster:
> Its not so easy to make this work. cmake seems to be an issue.
>From what I've been seeing in a couple of mails now, it feels like you
might be running into issues which seem to be more specific to RHEL and
Fedora than to darktable and the general
On Friday, 2 November 2018 12:58:52 CET Sturm Flut wrote:
> Dear list,
>
> I guess this can also depend a lot on the hardware and the specific
> X.Org/Mesa/GTK/driver version combinations. I've been using darktable on
> a 4K display with Arch Linux running on a Ryzen 1600X for one and a half
>
Dear list,
I guess this can also depend a lot on the hardware and the specific
X.Org/Mesa/GTK/driver version combinations. I've been using darktable on
a 4K display with Arch Linux running on a Ryzen 1600X for one and a half
years and there haven't been any noticeable lags, neither with the old
heya,
it used to do the gamma in the olden days. now it just does what you
observed: convert to uint8 for display and any marshalling of data at
the end of the pipeline in gui mode can take place here. it's
certainly not applying gamma. i suppose we could delete these old
gamma lut table lines of
Hi August,
Right, I have a "workaround" for this:
https://github.com/TurboGit/darktable/commit/8506770fef89e8750320efec9e8c633fe3097dc1
Not sure if it still apply or not. But the idea was to skip as much as
possible Gtk event when moving over the lighttable. This is not a real
solution, just a
On Friday, 2 November 2018 05:05:51 CET August Schwerdfeger wrote:
> Darktable 2.4.3 and .4, MacOS and Fedora.
>
> When using Darktable on a 4K monitor, I am experiencing a UI lag that seems
> dependent on the size of the application window.
>
> For example, when I size the window with
