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

[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 consider that changes in that place also will require changes to 
the equivalent OpenCL code which might be anything but trivial.


Ulrich

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

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

[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
>>> distributions. Wayland support doesn't seem to me to be critical for 2.4.0.
>> Ack, IMO Wayland is still to be considered experimental and not a top 
>> priority 
>> to fix.
> No intention of being pushy, but for information completeness, on Fedora
> Workstation Wayland is the default graphic server

Interesting... The code in git master should work with Wayland due to PR 1453, 
which requests GDK to use the XWayland compatibility layer as a backend in 
preference to Wayland. The continued work on bug 11535 should allow GTK/GDK to 
use the straight Wayland backend.

Wayland has exposed some quirks in darktable's UI code which X11 is too 
tolerant to notice. One might argue this is circular reasoning, and as these 
are problems only in the eyes of the Wayland display server.

[...]

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

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

[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 makes its way into
> >> distributions. Wayland support doesn't seem to me to be critical for
> >> 2.4.0.
> > 
> > Ack, IMO Wayland is still to be considered experimental and not a top
> > priority to fix.
> 
> No intention of being pushy, but for information completeness, on Fedora
> Workstation Wayland is the default graphic server

Good for them. Fedora has always been special. :-)

signature.asc
Description: This is a digitally signed message part.

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

[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 for another distribution. :-(

> '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 possibility that it could be 'theme' related?

No, OpenSUSE is just shipping buggy software.

> David

Tobias

[]

signature.asc
Description: This is a digitally signed message part.

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

[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 possibility that it could be 'theme' related?

David

On 06/21/2017 12:23 PM, Tobias Ellinghaus wrote:
> 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 fix in sight?
>>
>> I am running the latest git on OpenSUSE with XFCE desktop.
> 
> What version of GTK3 are you having installed? IIRC it was a bug in that 
> library.
> 
>> David
> 
> Tobias
> 



signature.asc
Description: OpenPGP digital signature

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

[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 critical for 2.4.0.
> Ack, IMO Wayland is still to be considered experimental and not a top 
> priority 
> to fix.
No intention of being pushy, but for information completeness, on Fedora
Workstation Wayland is the default graphic server
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

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

[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 fix in sight?
> 
> I am running the latest git on OpenSUSE with XFCE desktop.

What version of GTK3 are you having installed? IIRC it was a bug in that 
library.

> David

Tobias

signature.asc
Description: This is a digitally signed message part.

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

[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 Ellinghaus wrote:
>>> I'm using a local build with [...] Wolfgang Mader's
>>> modern monochrome modules since about 4 months and wouldn't want to miss
>>> either.
>>> https://github.com/wmader/darktable/tree/color2gray
>>
>> That was merged initially, currently resides as a preset in "color
>> look up table" module
>
>
> This module has a parameter. How can this work with a single look up
> table???

but did that parameter really change anything? i was under the
impression that the changes were really cosmetic and ignorantly
removed it..

-jo

> .mm
>
>
>
>
>
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

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

[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 wrote:
>>> I'm using a local build with [...] Wolfgang Mader's
>>> modern monochrome modules since about 4 months and wouldn't want to miss
>>> either.
>>> https://github.com/wmader/darktable/tree/color2gray
>>
>> That was merged initially, currently resides as a preset in "color
>> look up table" module
>
>
> This module has a parameter. How can this work with a single look up
> table???
Dunno, i'm simply stating the current status:

commit cf98370e253590e3a6e5844433a0cfae8e3df126
Author: johannes hanika 
Date:   Sun Nov 20 08:15:20 2016 +1300

   monochrome: remove module. use clut+local contrast

   clut has the hk-mono preset, local contrast (optionally) uses the
   local laplacian filter.

diff --git a/src/iop/mm.c b/src/iop/mm.c
deleted file mode 100644
index 19293c644..0
--- a/src/iop/mm.c
+++ /dev/null


> .mm
Roman.
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

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

[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.

David
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

[darktable-dev] Flash data in "image information" panel?

[Mark Heieis]

  
  
Hi,
Is there a reason
  (beyond UI space) that flash information is not displayed? Or
  is it somewhere else that I'm missing? Either way, it would be
  rather nice if flash data was included in the image
  information panel.
Thanks.
  

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

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

[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 wouldn't want to miss
either.
https://github.com/wmader/darktable/tree/color2gray

That was merged initially, currently resides as a preset in "color
look up table" module


This module has a parameter. How can this work with a single look up table???

.mm




___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

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

[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 soon enough
> to
> >> make its way into 2.4.0? Additional improvement would be slightly better
> >> quality zoomed-in rendering in darkroom view, and faster initial
> rendering
> >> of the preview when loading a new image.
> >
> > 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.
>
> [...]
>
> > Ack, IMO Wayland is still to be considered experimental and not a top
> priority
> > to fix.
>
> Indeed. And it seems that Nvidia proprietary drivers and Wayland don't
> interact well (something about EGLStreams vs. GBM). In which case, Nvidia
> GPU users may not be deep into Wayland...
>
> [...]
>
> ___
> darktable developer mailing list
> to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
>
>

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

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

[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 in darkroom view, and faster initial rendering
>> of the preview when loading a new image.
>
> 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.

[...]

> Ack, IMO Wayland is still to be considered experimental and not a top 
> priority 
> to fix.

Indeed. And it seems that Nvidia proprietary drivers and Wayland don't interact 
well (something about EGLStreams vs. GBM). In which case, Nvidia GPU users may 
not be deep into Wayland...

[...]

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

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

[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 that
> highlights have magenta edges.
> 
> It would be great if before 2.4.0 I could code a slightly improved box
> filter and write SSE variants. (The Bayer SSE code is currently disabled,
> and there never was X-Trans SSE code.) I don't know if this will entirely
> fix https://redmine.darktable.org/issues/11340 (negative values for
> demosaic), and alas don't think it will fix the magenta edges to
> highlights.
> 
> 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 in darkroom view, and faster initial rendering
> of the preview when loading a new image.

I'd say that is well withing the time frame – provided it's not too invasive.

> 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 critical for 2.4.0.

Ack, IMO Wayland is still to be considered experimental and not a top priority 
to fix.

> Dan

Tobias

[...]

signature.asc
Description: This is a digitally signed message part.

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

[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 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:
>>
>> https://redmine.darktable.org/projects/darktable/wiki/Building_darktable_22
>>
>> Does anyone know if there are any new deps?
>
> One thing that comes to mind is the switch from Lua 5.2 to 5.3. IIRC we also
> bumped the required CMake version, but I am not sure about that and would have
> to dig through the git log. I'll help assembling the changed deps eventually.
Lua 5.3
CMake 3.1
Required: GCC 4.8 / clang 3.3   Recommended: GCC 5.0 / clang 3.5
New dependency: zlib

>> Regards,
>>
>> Rob
>
> Tobias
Roman.
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

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

[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 testing and create a new page on the wiki for 2.4 based on
> the one for 2.2:
> 
> https://redmine.darktable.org/projects/darktable/wiki/Building_darktable_22
> 
> Does anyone know if there are any new deps?

One thing that comes to mind is the switch from Lua 5.2 to 5.3. IIRC we also 
bumped the required CMake version, but I am not sure about that and would have 
to dig through the git log. I'll help assembling the changed deps eventually.

> Regards,
> 
> Rob

Tobias

signature.asc
Description: This is a digitally signed message part.