Re: [darktable-dev] Darkroom UI refactoring

2018-10-09 Thread Aurélien Pierre
But even if we keep the actual disposition, don't you think it's weird that : * in/out color profiles are stored in the color tabs, whereas they are "basic" in the sense they are needed from technical requirements and always on, * signal-processing modules are mixed with creative ones

Re: [darktable-dev] Darkroom UI refactoring

2018-10-09 Thread Timothy Spear
I have been using Lightroom for six years. Before that Aperature for three years. Over the past year, ACDPro, Capture One, Luminar, CyberShot and a few others (looking to replace Lightroom, selected dt). It just hit me based on Aurélien's email. Every commercial product has the interface organiz

Re: [darktable-dev] Re: Colour Matrix for Canon EOS M3

2018-10-09 Thread Patrick Shanahan
* Andreas Schneider [10-09-18 02:16]: > On Monday, 8 October 2018 17:02:11 CEST openhab.doc wrote: > > Hello Andreas, > > Hi Pierre, > > > While working into the topic and the resulting intensive reading of the > > article, I noticed a few things that can be described more closely. Here I > > wi

Re: [darktable-dev] Darkroom UI refactoring

2018-10-09 Thread Mark Feit
On 10/9/18 3:02 AM, Aurélien Pierre wrote: But even if we keep the actual disposition, don't you think it's weird that : * in/out color profiles are stored in the color tabs, whereas they are "basic" in the sense they are needed from technical requirements and always on, I don't th

Re: [darktable-dev] Darkroom UI refactoring

2018-10-09 Thread Jason Polak
> > * in/out color profiles are stored in the color tabs, whereas they are > "basic" in the sense they are needed from technical requirements and > always on, Yes they are needed, but I wouldn't want them cluttering up the 'basic' group. If they have to be modified, it's likely to be no

Re: [darktable-dev] Colour Matrix for Canon EOS M3

2018-10-09 Thread openhab.doc
Hi all, the links are online again! https://c.web.de/@615570179773960144/nzTRoUvERdKwexyPn7dv1w https://c.web.de/@615570179773960144/fNAZ_GfRSuufUTyy4XQ--g Thanks Pierre Am Montag, 8. Oktober 2018, 21:43:45 CEST schrieb Matej Martinovic: > Hello Pierre, > > I can't really help you with your

Re: [darktable-dev] Darkroom UI refactoring

2018-10-09 Thread Aurélien Pierre
What I call "signal-processing" here are all the module intended to clean the data and turn an (always) damaged picture into what it is supposed to look like in theory. That is : 1. reconstructing missing parts (clipped highlights) 2. recovering the dynamic range (tonemapping) 3. reconstructing

Re: [darktable-dev] Darkroom UI refactoring

2018-10-09 Thread William Ferguson
On Tue, Oct 9, 2018 at 7:18 PM Aurélien Pierre wrote: > What I call "signal-processing" here are all the module intended to clean > the data and turn an (always) damaged picture into what it is supposed to > look like in theory. That is : > >1. reconstructing missing parts (clipped highlights

Re: [darktable-dev] Darkroom UI refactoring

2018-10-09 Thread Aurélien Pierre
Le 10/10/2018 à 00:14, William Ferguson a écrit : > On Tue, Oct 9, 2018 at 7:18 PM Aurélien Pierre > mailto:rese...@aurelienpierre.com>> wrote: > > What I call "signal-processing" here are all the module intended > to clean the data and turn an (always) damaged picture into what > it is

Re: [darktable-dev] Darkroom UI refactoring

2018-10-09 Thread William Ferguson
On Wed, Oct 10, 2018 at 12:53 AM Aurélien Pierre wrote: > Le 10/10/2018 à 00:14, William Ferguson a écrit : > > On Tue, Oct 9, 2018 at 7:18 PM Aurélien Pierre > wrote: > >> What I call "signal-processing" here are all the module intended to clean >> the data and turn an (always) damaged picture