* I. Ivanov [01-31-19 22:34]:
>
> > It doesn't work over network (on different computers) because DT code
> > checks for existence of PID:
> > https://github.com/darktable-org/darktable/blob/master/src/common/database.c
> > So I guess currently there's no guard against 2 darktables running on
>
It doesn't work over network (on different computers) because DT code
checks for existence of PID:
https://github.com/darktable-org/darktable/blob/master/src/common/database.c
So I guess currently there's no guard against 2 darktables running on
different PCs accessing the same database on
Thanks ... that answers my question
On 2019-01-31 12:32 a.m., Archie Macintosh wrote:
On Thu, 31 Jan 2019 at 07:59, Archie Macintosh wrote:
On Wed, 30 Jan 2019 at 23:30, David Vincent-Jones wrote:
Can somebody explain why (on some occasions only) the 'black relative
exposure' slider, sets
On Thu, 31 Jan 2019 at 07:59, Archie Macintosh wrote:
>
> On Wed, 30 Jan 2019 at 23:30, David Vincent-Jones wrote:
>>
>> Can somebody explain why (on some occasions only) the 'black relative
>> exposure' slider, sets itself to a maximum value when using the 'auto
>> tune levels'. The value
On Thu, 31 Jan 2019 08:13:09 +0100
Bernhard wrote:
> Patrick Shanahan schrieb am 31.01.19 um 05:09:
> >> I am trying to avoid check XMP each time DT starts as it takes quite some
> >> time for my collection.
> > if you NEVER have but one instance of dt running, should not be a problem.
> > if
