> > * 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 not very often and then they can be found in the color group because they have to do with color (at least, not coming from an image processing background, it makes sense for them to be there). > * signal-processing modules are mixed with creative ones Do you mean highpass and lowpass? If so, I don't think it's really strange. The highpass and lowpass modules create a sort of more advanced mask that could be used for sharpening, but they could also be used for more creative effects by using different blend modes. Regular sharpening and equalizer seem like more basic corrective modules (sharpening is typically because of anti-aliasing filters or softer lenses, equalizer for microconstrast-to-macroconstrast adjustments. The creative group consists of modules that provide a little more unusual effects that you might not really need for most shots but can often radically alter the look of them, or else things like framing and watermark. > * you get sharpen in enhancements and high-pass in effects, but they > do exactly the same thing Sharpening and highpass don't do exactly the same thing. In order for the highpass module to actually do something like sharpening, you have to combine its output with the image using a blend mode. If you use a different blend mode, the result wouldn't just be what you might call sharpening. Just try 'difference' blend mode for instance. You can create funny effects with it that might actually have an occasional use. > * same for local-contrast and wavelet equalizer I agree that this could be confusing, but here is some logic to it as well. The local constrast module in 'local laplacian filter' mode has sliders for how it operates on shadows, highlights, and midtones. It is supposed to enhance by operating on these three brightness areas of an image, whereas the equalizer more emphasizes the whole image all at once. > * same for the crop/flip and the perspective correction. Perspective correction is supposed to correct converging lines caused by the placement of the sensor plane away from the plane of converging lines. Crop isn't supposed to correct for anything. It's just taking part of the image. > > I mean, even with my own workflow set apart, I just think it would make > sense to separate technical and creative modules completely. And by > technical, I mean everything related to image reconstruction and > normalization (things you would do in Matlab). Especially since the > technical modules mostly come early in the pipe, it would make sense to > have them grouped explicitely so that you set them first. Look, I don't think the arrangement of modules is 100% perfect, and certainly people will have different preferences. But I am also not sure why modules should be separated based on where they are in the pixelpipe. The pixelpipe is just the order of how the modules are applied and there are technical reasons for the pipe to be in a fixed order. For example, in an image I processed today, 'defringe' comes before 'equalizer' in the pixelpipe. But fringing is one of the last things I think about when editing because I care a lot more about general composition and look and feel. Jason ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
