Re: [darktable-dev] Planning of the upcoming 2.4.0 release

2017-07-17 Thread Tobias Ellinghaus
Am Mittwoch, 21. Juni 2017, 11:39:30 CEST schrieb Dan Torop: > Hi Tobias, Hi Dan, > I've been working on downscaling mosaiced images without (or with fewer) > artifacts (https://redmine.darktable.org/issues/11167). Right now there's > workable code for Bayer and X-Trans in git master. The main

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

2017-06-22 Thread Ulrich Pegelow
Am 20.06.2017 um 11:43 schrieb Tobias Ellinghaus: Hello there, we are currently thinking about having the next feature release (2.4.0) earlier than Christmas. In order to plan for that we need to know if anyone is currently working on something that should go into the release. We would also

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

2017-06-22 Thread Ulrich Pegelow
Am 22.06.2017 um 20:23 schrieb Ulrich Pegelow: OK, that sounds good. There should not be any OpenCL code dealing with non-floating point values at that place. But let me double-check that. Reply to myself. This is what I get for the preview of an xtrans image: [pixelpipe_process] [preview]

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

2017-06-22 Thread Ulrich Pegelow
Am 22.06.2017 um 19:31 schrieb Dan Torop: Ulrich Pegelow writes: Oh no! I was thinking of the dt_iop_clip_and_zoom_demosaic_{half,third}_*() functions in imageop_math.c. Those don't have OpenCL implementations, though? Certainly getting into revising OpenCL code

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

2017-06-22 Thread Dan Torop
Ulrich Pegelow writes: >>> Please consider that changes in that place also will require changes to >>> the equivalent OpenCL code which might be anything but trivial. >> >> Oh no! I was thinking of the dt_iop_clip_and_zoom_demosaic_{half,third}_*() >> functions in

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

2017-06-22 Thread Ulrich Pegelow
Am 22.06.2017 um 15:58 schrieb Dan Torop: Ulrich Pegelow writes: Am 21.06.2017 um 18:03 schrieb Dan Torop: I'd say that is well withing the time frame – provided it's not too invasive. That is great. Should be a tweak to the Bayer downscale code (making

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

2017-06-22 Thread Dan Torop
Ulrich Pegelow writes: > Am 21.06.2017 um 18:03 schrieb Dan Torop: >>> >>> I'd say that is well withing the time frame – provided it's not too >>> invasive. >>> >> >> That is great. Should be a tweak to the Bayer downscale code (making >> start/endpoints of sample

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

2017-06-21 Thread Ulrich Pegelow
Am 21.06.2017 um 18:03 schrieb Dan Torop: I'd say that is well withing the time frame – provided it's not too invasive. That is great. Should be a tweak to the Bayer downscale code (making start/endpoints of sample right), bringing that work to X-Trans, and then SSE variants. Please

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

2017-06-21 Thread Dan Torop
Germano Massullo writes: > Il 21/06/2017 17:43, Tobias Ellinghaus ha scritto >>> I've also been working on Wayland support >>> (https://redmine.darktable.org/issues/11535). This is mostly done, but >>> isn't worth enabling until GTK+ >= 3.22.16 makes its way into >>>

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

2017-06-21 Thread Tobias Ellinghaus
Am Mittwoch, 21. Juni 2017, 21:44:30 CEST schrieb Germano Massullo: > Il 21/06/2017 17:43, Tobias Ellinghaus ha scritto > > >> I've also been working on Wayland support > >> (https://redmine.darktable.org/issues/11535). This is mostly done, but > >> isn't worth enabling until GTK+ >= 3.22.16

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

2017-06-21 Thread Tobias Ellinghaus
Am Mittwoch, 21. Juni 2017, 13:06:48 CEST schrieb David Vincent-Jones: > I am running gtk3 3.20.10-5.3.1 ... but there are a number of That's the broken version. It seems a recent 3.22 is only in Tumbleweed. I am sorry but there is nothing we can do, besides encouraging to upgrade or to look

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

2017-06-21 Thread David Vincent-Jones
I am running gtk3 3.20.10-5.3.1 ... but there are a number of 'secondary' packages that are carrying entirely different version numbers. PackageKit-gtk3-module 1.1.3-3.2 gtk3-branding-openSUSE 42.1-3.1 . (I am running openSUSE 42.2) No modules show any available updates. Is there any

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

2017-06-21 Thread Germano Massullo
Il 21/06/2017 17:43, Tobias Ellinghaus ha scritto >> I've also been working on Wayland support >> (https://redmine.darktable.org/issues/11535). This is mostly done, but >> isn't worth enabling until GTK+ >= 3.22.16 makes its way into >> distributions. Wayland support doesn't seem to me to be

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

2017-06-21 Thread Tobias Ellinghaus
Am Mittwoch, 21. Juni 2017, 19:01:10 CEST schrieb David Vincent-Jones: > The image import problem still exists on my system requiring this > strange work-around (multiple tabbing and then a Ctrl a). This is a > nuisance apart from anything else. Is there any light at the end of this > tunnel and a

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

2017-06-21 Thread johannes hanika
heya, On Thu, Jun 22, 2017 at 4:35 AM, Moritz Mœller (The Ritz) wrote: > On June 20, 2017 18:34:27 Roman Lebedev wrote: >> >> On Tue, Jun 20, 2017 at 5:55 PM, Moritz Moeller >> wrote: >>> >>> On 20.6.17 11:43 , Tobias

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

2017-06-21 Thread Roman Lebedev
On Wed, Jun 21, 2017 at 7:35 PM, Moritz Mœller (The Ritz) wrote: > On June 20, 2017 18:34:27 Roman Lebedev wrote: >> >> On Tue, Jun 20, 2017 at 5:55 PM, Moritz Moeller >> wrote: >>> >>> On 20.6.17 11:43 , Tobias Ellinghaus

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

2017-06-21 Thread David Vincent-Jones
The image import problem still exists on my system requiring this strange work-around (multiple tabbing and then a Ctrl a). This is a nuisance apart from anything else. Is there any light at the end of this tunnel and a fix in sight? I am running the latest git on OpenSUSE with XFCE desktop.

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

2017-06-21 Thread The Ritz
On June 20, 2017 18:34:27 Roman Lebedev wrote: On Tue, Jun 20, 2017 at 5:55 PM, Moritz Moeller wrote: On 20.6.17 11:43 , Tobias Ellinghaus wrote: I'm using a local build with [...] Wolfgang Mader's modern monochrome modules since about 4 months and

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

2017-06-21 Thread Colin Adams
I don't use Wayland for that very reason. On Wed, 21 Jun 2017 at 17:04 Dan Torop wrote: > > Tobias Ellinghaus writes: > > > Am Mittwoch, 21. Juni 2017, 11:39:30 CEST schrieb Dan Torop: > > [...] > > >> I will be able to get to this again in early July. Is that

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

2017-06-21 Thread Dan Torop
Tobias Ellinghaus writes: > Am Mittwoch, 21. Juni 2017, 11:39:30 CEST schrieb Dan Torop: [...] >> I will be able to get to this again in early July. Is that soon enough to >> make its way into 2.4.0? Additional improvement would be slightly better >> quality zoomed-in rendering

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

2017-06-21 Thread Tobias Ellinghaus
Am Mittwoch, 21. Juni 2017, 11:39:30 CEST schrieb Dan Torop: > Hi Tobias, > > I've been working on downscaling mosaiced images without (or with fewer) > artifacts (https://redmine.darktable.org/issues/11167). Right now there's > workable code for Bayer and X-Trans in git master. The main flaw is

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

2017-06-21 Thread Roman Lebedev
On Wed, Jun 21, 2017 at 12:17 PM, Tobias Ellinghaus wrote: > Am Mittwoch, 21. Juni 2017, 09:33:13 CEST schrieb Robert William Hutton: >> On 21/06/17 04:47, Germano Massullo wrote: >> > It would be also interesting to know if there will be changes in >> > darktable dependencies, so

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

2017-06-21 Thread Tobias Ellinghaus
Am Mittwoch, 21. Juni 2017, 09:33:13 CEST schrieb Robert William Hutton: > On 21/06/17 04:47, Germano Massullo wrote: > > It would be also interesting to know if there will be changes in > > darktable dependencies, so that package maintainers can early start > > working on them > > I'll do some

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

2017-06-20 Thread Robert William Hutton
On 21/06/17 04:47, Germano Massullo wrote: It would be also interesting to know if there will be changes in darktable dependencies, so that package maintainers can early start working on them I'll do some testing and create a new page on the wiki for 2.4 based on the one for 2.2:

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

2017-06-20 Thread Germano Massullo
It would be also interesting to know if there will be changes in darktable dependencies, so that package maintainers can early start working on them ___ darktable developer mailing list to unsubscribe send a mail to

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

2017-06-20 Thread Roman Lebedev
On Tue, Jun 20, 2017 at 5:55 PM, Moritz Moeller wrote: > On 20.6.17 11:43 , Tobias Ellinghaus wrote: >> >> In order to plan for that we need to know if anyone is currently working >> on >> something that should go into the release. We would also need some hands >> on >>

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

2017-06-20 Thread Pascal Obry
Le mardi 20 juin 2017 à 16:55 +0200, Moritz Moeller a écrit : > https://github.com/rabauke/darktable/tree/haze_removal This one is already committed on master. --   Pascal Obry /  Magny Les Hameaux (78)   The best way to travel is by means of imagination   http://www.obry.net   gpg

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

2017-06-20 Thread Pascal Obry
Hi Tobias, we are currently thinking about having the next feature release (2.4.0) > earlier than Christmas. > Good news! > In order to plan for that we need to know if anyone is currently working on > something that should go into the release. I do have a merge-request for the mask undo