Re: Fwd: [darktable-dev] preparing 3.2

[Matthias Elsdörfer]

You guys rock!!

Matthias Elsdörfer · Weitererzähler.

Web Design · Fotografie
Copywriting · Kommunikation

Brand Artery  · M.E. Fotografie

Telefon: (+49) 170 - 7 555 701


On 7/15/20 8:47 AM, Bruce Williams wrote:

Hear hear! :)

Cheers,
Bruce Williams
--
Mobile:  +61 41 250 6349

brucewilliamsphotography.com 
shuttersincpodcast.com 

e-mail  | Twitter
 | LinkedIn
 | Facebook
 | Soundcloud
 | Quora

--




-- Forwarded message -
From: *Andreas Schneider* mailto:a...@cryptomilk.org>>
Date: Wed, Jul 15, 2020 at 4:04 PM
Subject: Re: [darktable-dev] preparing 3.2
To: darktable mailto:darktable-dev@lists.darktable.org>>
Cc: Pascal Obry mailto:pas...@obry.net>>


On Tuesday, 14 July 2020 16:21:12 CEST Pascal Obry wrote:
> @All devs !

Pascal,

thank you very much for maintaining darktable. You are doing an
absolutely
fantastic job!


T H A N K S !


--
Andreas Schneider a...@cryptomilk.org 
GPG-ID:     8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D


___
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


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

Aw: [darktable-dev] preparing 3.2

[Alexander Rabtchevich]

Thanks for the great work. Darktable becomes better day after day.

One personal note on the default scene-referred process: filmic RGB v4 is very 
time-consuming module compared to v3 or base curve. On my PC the difference is 
over ten times (40 seconds vs 3.6 seconds). The 40 seconds on my old AMD 1075T 
seem to transfer into about 15 seconds on AMD 2700x comparing their multi-core 
performance, but 15 seconds for one image is too much. The module itself is 
great and it produces very nice controllable results, but is it wise to make it 
default without speed optimizations or OpenCL implementation?

With respect,
Alexander Rabtchevich

> Gesendet: Dienstag, 14. Juli 2020 um 16:21 Uhr
> Von: "Pascal Obry" 
> An: "darktable" 
> Betreff: [darktable-dev] preparing 3.2
>
>
> @All devs !
>
> If you have had some PR merged for 3.2 please can you review the latest
> RELEASE_NOTES.md that I have just pushed to ensure I don't have missed
> any important entry.
>
> Also, I think for 3.4 we should concentrate on the documentation which
> is now lacking many entries. So if you could write some description for
> the manual of the new feature you have added it would be nice. Either
> directly into the docbook on the repository with a PR or sending a
> plain text + screenshot if needed to me that I will volunteer to commit
> at the right place.
>
> Thanks all for the contributions!
>
> --
>   Pascal Obry /  Magny Les Hameaux (78)
>
>   The best way to travel is by means of imagination
>
>   http://www.obry.net
>
>   gpg --keyserver keys.gnupg.net --recv-key F949BD3B
>
> ___
> 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] preparing 3.2

[Peter Harde]

Hi,

my hardware is relatively new and has relatively high performance 
(i7-8700, 6 core, 12 threads, Nvidia RTX 2060). But also with this 
hardware, filmic 4 slows down the processing markedly. And combining 
filmic 4 with tone equalizer increases the problem. It is obvious that 
both modules are "heavy" due to the algorithms behind them. All the more 
it seems very reasonable to me, to get OpenCL support for filmic 4.


Best regards

Peter Harde

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