Re: [darktable-dev] OpenCL question

2019-03-07 Thread David Vincent-Jones
Thank you Andreas . yes, it helps to know where to put the commands =;) Unfortunately it does not appear to have solved the problem still very slow and the mouse jerking around, system freezing, not very nice at all without OpenCL my system runs just fine!! On 2019-03-07 12:43 p.

[darktable-dev] Re: [darktable-user] ATTENTION: darktable master may go unstable.

2019-03-07 Thread Edgardo Hoszowski
So everybody is in the same page, a few notes: Modules can now be moved pretty much everywhere (with shift + drag), if not, the system will not allow it (i.e. RAW modules can't be mixed with Lab/RGB modules) The only exception is: Lab modules can't be before input color profile or after output col

Re: [darktable-dev] ATTENTION: darktable master may go unstable.

2019-03-07 Thread Pascal Obry
Le jeudi 07 mars 2019 à 22:16 +0100, Moritz Moeller a écrit : > Fucking amazing!!! So next DT will get a node editor? :] > Let me know when this is merged, I want to try this immediately! It is now merged. Do report all issues on GitHub. Thanks, -- Pascal Obry / Magny Les Hameaux (78) Th

Re: [darktable-dev] ATTENTION: darktable master may go unstable.

2019-03-07 Thread Moritz Moeller
On 7.3.19 21:47, Pascal Obry wrote:> - mask history (that is a mask is now part of the history and when changed will not change the same mask in the same module in the history. - the possibility to have custom module order (with drag & drop) - a working color space Fucking amazing!!! So next DT

[darktable-dev] ATTENTION: darktable master may go unstable.

2019-03-07 Thread Pascal Obry
ATTENTION: darktable master may go unstable. I'm about to merge a commit in master that could make darktable unstable. This is an extensive change from Edgardoh which adds: - mask history (that is a mask is now part of the history and when changed will not change the same mask in the same modul

Re: [darktable-dev] OpenCL question

2019-03-07 Thread Andreas Schneider
On Thursday, March 7, 2019 8:34:39 PM CET David Vincent-Jones wrote: > Thank you Andreas . here are my results > > [W530 ~]# opencl_device_priority=*/!0,*/*/* > -bash: !0: event not found > [W530 ~]# opencl_mandatory_timeout=250 > [W530 ~]# opencl_scheduling_profile=very fast GPU > -bash: fast

Re: [darktable-dev] OpenCL question

2019-03-07 Thread David Vincent-Jones
Thank you Andreas . here are my results [W530 ~]# opencl_device_priority=*/!0,*/*/* -bash: !0: event not found [W530 ~]# opencl_mandatory_timeout=250 [W530 ~]# opencl_scheduling_profile=very fast GPU -bash: fast: command not found I am using dual monitors by the way with dt running on the ex

Re: [darktable-dev] OpenCL question

2019-03-07 Thread Andreas Schneider
On Thursday, March 7, 2019 8:09:48 PM CET David Vincent-Jones wrote: > Sorry for the lack of appropriate material ... I hope this added info is > what you are looking for: > > Card is Nvidia GK107GLM (Quadro K1000M) > > driver=nvidia ver:415.27 > > Operating system x86_64 Manjaro rolling release

Re: [darktable-dev] OpenCL question

2019-03-07 Thread David Vincent-Jones
Sorry for the lack of appropriate material ... I hope this added info is what you are looking for: Card is Nvidia GK107GLM (Quadro K1000M) driver=nvidia ver:415.27 Operating system x86_64 Manjaro rolling release using Arch repos. I am not sure if the intel driver is blacklisted does it

Re: [darktable-dev] OpenCL question

2019-03-07 Thread Andreas Schneider
On Wednesday, 6 March 2019 22:06:37 CET David Vincent-Jones wrote: > dt version: 2.7.0+594~g03d44f57e Manjaro from Arch-repos. > > I have recently initiated OpenCL on my system. When I start from the > terminal (-d opencl) all indications are that all the elements are > successfully in place ... n