Re: [darktable-dev] book on color

Dear Jason, Am 11.01.24 um 12:08 schrieb Jason Polak: Dear Devs/Users, Does anyone know of a good introductory book on color space theory from a mathematical perspective? I'm looking for an introductory text to learn more about color. I have a PhD in pure math so any amount of math is good.

Re: Fwd: [darktable-dev] Delete files on memory card

Hi, Am 18.07.23 um 22:18 schrieb Bruce Williams: First up, this is a question more for the darktable-user list, not the dev list. But now that we're here... No, dt does not offer the ability to remove files from the memory card. And conventional wisdom says you really shouldn't wipe your

Re: [darktable-dev] Documentation

Hi, Am 19.06.23 um 23:13 schrieb Mica Semrick: Hi, we are having some issues with the punishing automation. I've been working on it but haven't found the solution yet. I already suspected that it might be an automation issue. Good to know that you are aware of this and already working on it.

[darktable-dev] Documentation

Hi, I am wondering what happened to the dt manuals. The manuals for dt 3.8, 4.0, 4.2 on https://www.darktable.org/resources/ are empty. Regards, Heiko -- -- Number Crunch Blog @ https://www.numbercrunch.de -- Cluster Computing @ https://www.clustercomputing.de -- Social Networking @

Re: [darktable-dev] Code reformatting...

Hi, Am 23.01.23 um 22:12 schrieb Matthias Andree: Am 23.01.23 um 08:40 schrieb Pascal Obry: While the idea is sound, 80 character wide lines seem so... 1980's. Do people still need to read and edit darktable source code on 640x480 displays? today's developers have not only wider screens than

Re: [darktable-dev] Code reformatting...

Dear Pascal, Am 23.01.23 um 08:40 schrieb Pascal Obry: Hello devs, As we are not ready to have an automatic reformatting of the code I have started at least making the function headers a bit more readable. From: void dt_gui_presets_show_edit_dialog(const char *name_in, const char

Re: [darktable-dev] Why is the next version 4.0

Hi, Am 17.02.22 um 21:44 schrieb Mica Semrick: I don't think there is a policy. In the chat room, the question was posed, "is the next release 3.10 or 4.0" and 4.0 sounded cool. There are a bunch of 4.0 worhty features too. many software projects follow "semantic versioning" today. In

Re: [darktable-dev] New module development process

Hi, Am 08.06.21 um 19:05 schrieb Bret Whissel: I have copied the `rgblevels` module into a new module that I'm calling 'agecorrect', and I have made modifications to the new module that do the initial corrections automatically when enabled on a photo. if I understand you correctly than the

Re: [darktable-dev] Support Coding

Dear Jan, Am 01.05.21 um 12:13 schrieb Solarer: I read the section on developing on the website and have 2 questions: 1) Do you prefer patches or pull requests? I think, creating a pull request on GitHub is the preferred way. 2) Can somebody tell me (or at least point me to a good source)

Re: [darktable-dev] Translation tips

Hi, Am 21.04.21 um 19:22 schrieb Bernhard: you can also compile and use| cmake -DCMAKE_INSTALL_PREFIX=/opt/darktable/ ..| || || |for installing into a different custom directory and use ||--configdir| and|--cachedir parameters when starting those installations to generate a specific profile

Re: [darktable-dev] Translation tips

Am 21.04.21 um 17:26 schrieb i...@kevinvermassen.be: Hi I'm looking for some translation tips. Until now, I just used Poedit to translate one line at a time. But I find it more clear to have darktable opened to see which string in English translate to which string in Dutch (I'm new to

Re: [darktable-dev] different meanings of "feather" in darktable

Dear Jeronimo, Am 05.01.21 um 14:22 schrieb Jeronimo Pellegrini: There is "feathering", used in mask refinement, which adapts a mask's edge to edges detected in image. And recently, when updating the translation, I saw "feather size" referring to the radius of the outer circle (or ellipsis)

[darktable-dev] raw spot removal?

Hi, the "spot removal" module is labeled as working in RAW space (see spots.c): const char *description(struct dt_iop_module_t *self) { return dt_iop_set_description(self, _("remove sensor dust spots"), _("corrective"),

Re: [darktable-dev] Assign Actions to MIDI Events

Hi Jaume, Am 04.11.20 um 21:56 schrieb Jaume Aragay Badia: I'm new here. I come from using LightRoom and I use a MIDI controller to adjust levels with it's sliders and trigger actions with it's buttons... I wanted to do the same with DT. basically you need to translate MIDI into key strokes.

Re: [darktable-dev] idea to consider

Hi, Am 30.08.20 um 14:22 schrieb Chris Shelton: Some photographers work in jpg only and sometimes I would not question their creative ability while maybe questioning the technical choice although I suppose they do avoid the mistake of overworking and gilding the lily jpeg is usually

Re: [darktable-dev] darktable 3.2- string freeze - let's start translations

Hi Pierre, I contributed several small updates for the German translation during the last few months. I planed to continue my work on the German translation, depending on my time budget. I do not plan to fix all missing translations in a single large pull request. I would rather

Re: [darktable-dev] Re: darktable 3.2- string freeze - let's start translations

Hi, Am 07.07.20 um 23:47 schrieb Pascal Obry: A quick fix... A string was found to not be marked for translation by Timur Davletshin. This is now fixed and so a new POT file is proposed (see attached file). Thanks Timur! I think "lus script installer dont show again" in the preferences

[darktable-dev] negadoctor & haze removal

Hi, I performed some basic experiments with the new nagadoctor module. I observed one possible issue: When the negadoctor module is used in combination with the haze removal module then the haze removal must be applied after RGB inversion via negadoctor. This means the haze removal module

Re: [darktable-dev] Translators: what tools are you using to translate?

Hi, I have not that much practical experience with translation. Though, when I contributed to darktable's translation I mainly used poedit, which I found quite convinient. I also tried emacs pod-mode and GetText extension for Clion, which give, however, not much more than some syntax

Re: [darktable-dev] Error messages when calling settings dialog

Hi, this might be an issue introduced by my recent updates for the German translations. Thanks for pointing out. I can reproduce this and will have a look at this trying to fix this. Heiko Am 20.05.20 um 15:55 schrieb Peter Harde: Dear developers 3.1.0+1707~g1bd0d448b, Ubuntu 18.04,

Re: [darktable-dev] translations

Dear Jeronimo, Am 30.04.20 um 23:13 schrieb Jeronimo Pellegrini: On Thu, Apr 30, 2020 at 09:31:44PM +0200, Heiko Bauke wrote: For example, I am working on the pt_BR translation. After pulling from git, I go to the po/ directory and run intltool-update pt_BR thanks, this is exactly what I

[darktable-dev] translations

Hi, a lot of new features and enhancements have been brought to darktable recently. As a consequence there are also some new untranslated UI strings, which are not yet accounted for in the *.po files, not even as untranslated strings. Therefore I wonder, what is the best way to update the

Re: [darktable-dev] Submit darktable 3.01 for Ubuntu 20.04 (ASAP)

Hi, Am 04.04.20 um 16:00 schrieb layingback: Ubuntu 20.04 (Focal Fossa) LTS ships April 23, but it still only has Darktable 2.6.3 in the official repositories. As an LTS (Long Term Support) it will be supported for 5 years (10 years for paid support).  Doubt you want to be supporting new

Re: [darktable-dev] unused feature "blend only lightness"

Hi, Am 01.02.20 um 16:28 schrieb rawfiner: Hi Only a guess, but maybe it is used when we display some channels of the parametric masks, or when we display the masks? this was also my first guess. But then I found if(request_mask_display & DT_DEV_PIXELPIPE_DISPLAY_ANY)

[darktable-dev] unused feature "blend only lightness"

Hi, all blend modes that operate in Lab space have some special treatment for the case that a module sets the flag IOP_FLAGS_BLEND_ONLY_LIGHTNESS. However, I cannot find any module that actually sets this flag. Furthermore, it seams to me not reasonable why the behavior of a blend mode

Re: [darktable-dev] Error at compile from current git master - libavif

Am 31.12.19 um 12:49 schrieb Heiko Bauke: Hi, Am 30.12.19 um 11:09 schrieb Richard Hobday: As far as I can see the package "libavif" or "libavif-dev" does not exist in Ubumtu 18.04. FYI: Ubuntu 19.10 comes with libavifile-0.7-bin - toolkit for libavifile libavifile-

Re: [darktable-dev] Error at compile from current git master - libavif

Hi, Am 30.12.19 um 11:09 schrieb Richard Hobday: As far as I can see the package "libavif" or "libavif-dev" does not exist in Ubumtu 18.04. FYI: Ubuntu 19.10 comes with libavifile-0.7-bin - toolkit for libavifile libavifile-0.7-common - toolkit for libavifile libavifile-0.7-dev - development

Re: [darktable-dev] [note] in darktable everything is written in lower case -- update translation

Hi, Am 11.12.19 um 11:05 schrieb openhab@web.de: Few days ago I learned that a rule exists among the darktable developers that says that in darktablel everything is written in lower case (see comments in pull request #3694). The rule has been taken into account for most translations, but

Re: [darktable-dev] darktable 3.0.0rc0 released

Hi, Am 04.11.19 um 18:44 schrieb Pascal Obry: The darktable 3.0.0rc0 release is out. just observed some odd behavior: Resetting all parameters of the local contrast module via the module's reset button yields: * detail 125% * highlights 50% * shadows 50% * midtone range 0.5 resetting the

Re: [darktable-dev] darktable 3.0.0rc0 released

Hi, Am 05.11.19 um 23:59 schrieb jys: I think that would cause *endless* confusion... probably better to call the new one 'filmic2' or something. agree, "filmic2" is not bad. Heiko -- -- Number Crunch Blog @ https://www.numbercrunch.de -- Cluster Computing @

Re: [darktable-dev] Drag-and-drop to change module order

Hi, Am 02.11.19 um 01:36 schrieb Patrick Shanahan: * Pascal Obry [11-01-19 16:30]: Le vendredi 01 novembre 2019 à 14:56 -0400, Patrick Shanahan a écrit : fwiw, I believe the pp order should remain static and *only* the visual list should be changable. Amusing! You are probably saying that

Re: [darktable-dev] haze removal default values

Hi, Am 15.09.19 um 18:03 schrieb Pascal Obry: Hi Andreas, the haze removal default values are in 99% of the cases too strong. Is there a reason that they are this strong? My suggestions for default values would be: strength: 0.15 distance: 0.200 I tend to agree and see the same issue on

Re: [darktable-dev] DT bad on skin tones?

Hi, Am 29.05.19 um 22:14 schrieb jys: Since the basecurve module must be retained, I'm wondering if, now that its default position has been moved to after colorin, is there anything preventing it from being moved even further along the pipe, to the most harmless possible location (whatever that

Re: [darktable-dev] meaning of RGB values

Hi, Am 23.05.19 um 00:32 schrieb Moritz Mœller: each module that relies on a certain color space must take into consideration everything in the pipe before (and possible undo it, which is not always really possible) to push stuff back into linear, if necessary. I completely agree. My

[darktable-dev] meaning of RGB values

Hi, quick question: what do RBG color values actually represent in darktable just after basecurve module? For simplicity, let us assume "input color profile" is standard color matrix with Rect2020-RGB as working profile (In case that this is of any relevance.). Backgroud of my question:

Re: [darktable-dev] Compiling lut3d.cl / openCL / Font issues with Master

Hi, Am 13.05.19 um 10:08 schrieb Sébastien Chaurin: Should I fill an issue on GitHub related to the compilation of lut3d.cl ? I can't believe I'm the only one facing this issue and not being able to use openCL with the current master. just got current git master. No

Re: [darktable-dev] Options shouldn't be tied to Filmstrip

Hi, Am 27.04.19 um 23:06 schrieb Stefan Klinger: Yeah, I'll do that: Stop nitpicking, Patrick. The user suggested that the UI could be designed better, and rightly so. And he made constructive suggestions, so let's discuss them, constructively. I also find the current behavior not

Re: [darktable-dev] sharpen module

Dear Aurélien Am 18.04.19 um 21:59 schrieb Aurélien Pierre: please don't do a deconvolution in the Lab color model. Natural blur is a phenomenon happening to photons and described by a convolution product. If you want to revert it, you need to use a physically meaningful color space, e.g. a

Re: [darktable-dev] sharpen module

Dear Pascal, Am 17.04.19 um 23:46 schrieb Pascal Obry: Let's go with that if we are sure the algo are equivalent. Code duplication is not good in the long run. the two implementations of the Gaussian filter work rather differently. Both are certainly not equivalent to each other in a

[darktable-dev] sharpen module

Hi, I just started to implement a simple (non-blind) deconvolution filter as an addition sharpening method. I plan to add this as an additional mode for the sharpening module. Looking at the code of the current unsharp mask method I realized that the module uses its own implementation of a

Re: [darktable-dev] where to discuss big changes

Hi, Am 16.04.19 um 19:51 schrieb rawfiner: Currently, the place where big changes should be discussed is IRC (according to houz, as I have not seen this information anywhere, which is problematic as new contributors may make big changes, so they have at least to be able to know where is the

Re: [darktable-dev] Suggestion: No Limit on Mask Blur Radius

Hi, Am 04.04.19 um 15:05 schrieb P. Altenburg: As it is, I've noticed the radius of the blur on (parametric) masks is 200 at max. I would love it if this radius could be really big, like a quarter of the image width or something. I agree that a maximal blur radius of 200 can be too small

Re: [darktable-dev] darktable from current git doesn't response after database conversion

Hi, Am 13.03.19 um 11:01 schrieb johannes hanika: i had a very similar problem with hangs during startup. in my case deleting the old /usr/local/lib/darktable directory did the trick (old plugins were installed there which happened to be renamed/not compiled any more, so they were neither

Re: [darktable-dev] darktable from current git doesn't response after database conversion

Hi, Am 12.03.19 um 01:28 schrieb Patrick Shanahan: * Heiko Bauke [03-11-19 20:21]: [...] Regarding the custom module, I am on my own of course. However, I wonder: does the database conversion require that users migrate from 2.6.1 when 2.8 will be released? aiui: the database is updated

Re: [darktable-dev] darktable from current git doesn't response after database conversion

Hi, Am 12.03.19 um 01:32 schrieb Edgardo Hoszowski: Should work with any version, at least if it works with 2.6 Do you know the database version you are migrating from? peeking around in library.db (and the respective backup of library.db from before the upgrade) with sqlitebrowser I found

Re: [darktable-dev] darktable from current git doesn't response after database conversion

Hi, Am 10.03.19 um 12:28 schrieb Alexander Rabtchevich: Darktable doesn't run (doesn't show lightroom). After saying "yes" to database conversion, the library.db time canges for sometime and after showing GUI frame nothing happens. gdb shows no errors. The state in the system monitor is

Re: [darktable-dev] ATTENTION: darktable master may go unstable.

Hi Patrick, Am 12.03.19 um 00:19 schrieb Patrick Shanahan: aiui, the order in the pipe has not changed, is hard coded. only the displayed order is changeable. in fact, there exists scripts to save different orders (for displaying) or to reset to display the pipe order. I think

Re: [darktable-dev] ATTENTION: darktable master may go unstable.

Hi, Am 07.03.19 um 21:47 schrieb Pascal Obry: - the possibility to have custom module order (with drag & drop) what great news! As I see, the custom ordering rendered the "priority" field in dt_iop_module_t obsolete. Therefore, I wonder what determines the modules' default position in the

Re: Fwd: [darktable-dev] Crop tool is awkward for my use case

Am 18.02.19 um 15:48 schrieb Moritz Mœller: +1 .mm On February 18, 2019 03:01:22 Bruce Williams wrote: Why not leave the current situation as it is, but add a CTRL key modifier to allow the alternate behaviour? like this approach, too. I think it would improve dt's ease of use.

[darktable-dev] static code analysis

Hi, I think darktable has made a huge step forwards regarding new features in the recent 2.6 release. For this reason I would like to focus on code quality, performance and user experience in my future contributions. Currently, there is an offer for open source developers to get a free

[darktable-dev] possible error in clipping.c

Hi, currently I am testing some static code analysis tools to search systematically for bugs and code smells in the darktable code base. So far, I found a lot of minor issues, which can be easily fixed, and even more false positives. In clipping.c, there is an issue that I am not able to

Re: [darktable-dev] minor issues in git master (and probably in rc0 too)

Dear Pascal, Am Mittwoch, 5. Dezember 2018 schrieb Pascal Obry: > I see, this is the "expected" layout. I have no better idea to > introduce a collapsible section. Have you a better idea? no, not really. At the moment I would prefer not to allow to collapse the section in the filmic module.

Re: [darktable-dev] minor issues in git master (and probably in rc0 too)

Dear Pascal, Am 04.12.18 um 23:23 schrieb Pascal Obry: I have done that recently maybe I misunderstand what the UI looks like on your side. Can you share a screen shot. see attachment. Heiko -- -- Number Crunch Blog @ https://www.numbercrunch.de -- Cluster Computing @

[darktable-dev] minor issues in git master (and probably in rc0 too)

Hi, the next dt release is already at the horizon. Thus I had a look at current git master. I just observed just two minor issues: * I have no clue how the new feature to rename module instances works. Clicking on "rename" nothing happens. I expected that some kind of dialogue appears to

Re: [darktable-dev] Feature request (Cropping module GUI)

Hi, Am Freitag, 16. November 2018 schrieb Jan Ingwer Baer: > If DT shows the aspect ratio it should try to find the nearest integral > fraction (of course with values below 30) like 3:2, 16:9, ... > > > For your exampel it should show 8.2:5, or it should use one of the > common denominators

Re: Fwd: [darktable-dev] feature freeze

* I will try to provide a tool to fix this issue (as far as possible). This, however, will take some time and I can not guarantee that this conversion will be possible. But I will try my best. see also https://github.com/darktable-org/darktable/pull/1827#issuecomment-439224708

Re: Fwd: [darktable-dev] feature freeze

Dear Andreas, Am 15.11.18 um 21:40 schrieb Andreas Schneider: On Thursday, 15 November 2018 21:33:00 CET Pascal Obry wrote: Le jeudi 15 novembre 2018 à 21:25 +0100, Andreas Schneider a écrit : The issue is probably a migration which didn't work:

Re: [darktable-dev] Using darktable with Go to convert raw to jpeg

Hi, Am Montag, 12. November 2018 schrieb Michael Mayer: > On Mon, Nov 12, 2018 at 8:54 AM, Heiko Bauke wrote: > > although I never investigated these compatibility issues I suspect one > > cannot expect much compatibility here. Different raw converters may work > > very d

Re: [darktable-dev] Using darktable with Go to convert raw to jpeg

Moin Moin, Am Montag, 12. November 2018 schrieb Michael Mayer: > Moin Moin, > We are grateful for every little piece of advice concerning XMP > sidecar files and you are welcome to write in our wiki. I still don't > understand how compatible Darktable is with Adobe Lightroom and other >

Re: [darktable-dev] advanced mask adjustments

Hi Björn, Am 10.11.18 um 11:22 schrieb Björn Sozumschein: So, aside from the better conformity with the user's intuitive understanding, maybe inverting the mask at the end of the pipeline would benefit usability. for better user experience I revised the code that constructs the mask

Re: Fwd: [darktable-dev] advanced mask adjustments

Hi Björn, many thanks for your feedback. Am 10.11.18 um 11:24 schrieb Björn Sozumschein: I also believe that a proper explanation would prevent confusion regarding the inversion behavior. However, I have concerns with respect to the usability, based on my initial experience: In most cases, I

[darktable-dev] advanced mask adjustments

Hi, currently I have an open pull request, see https://github.com/darktable-org/darktable/pull/1809 This pull request has some aspect which may lead to confusion by some users in some situations. I would like to draw your attention to this issue and would be thankful for feedback. The pull

Re: [darktable-dev] Plugin-SDK

Hi Jan, Am Montag, 5. November 2018 schrieb Jan Ingwer Baer: > It would be nice to have a thing like a 'Plugin-SDK' to enable more > users to create their own IOP-Modules. To make the development of > IOP-modules much more easy it should contain : > - all the needed headers and libraries > -

Mask feathering (was Re: [darktable-dev] OpenCL issues)

Hi, Am 29.10.18 um 22:55 schrieb Aurélien Pierre: Very pleased to hear that (not the bug part, though). [...] In particular, I need to enable blending on GPU.  Currently I am working on automatic mask refinement based on a guided filter, see

Re: [darktable-dev] OpenCL issues

Dear Ulrich, Am 30.10.18 um 07:07 schrieb Ulrich Pegelow: The empty string is not the default for opencl_device_priority, default is "*/!0,*/*/*". Please note that manual device selection by this parameter is only effective if opencl_scheduling_profile=default. I checked what is written to

Re: [darktable-dev] OpenCL issues

Am 29.10.18 um 22:55 schrieb Aurélien Pierre: You can try : 1. the command *nvidia-smi* to see how the GPU RAM is used (if there is not enough vRAM available, you will see an OpenCL error code -4). 2. setting opencl_async_pixelpipe=true in darktablerc 3. setting opencl_mandatory_timeout

[darktable-dev] OpenCL issues

Hi, I own a laptop with a low-end OpenCL capable graphics card. Usually I explicitly turn OpenCL support off for darktable. Today I enabled OpenCL support in darktable for some testing purposes. Starting darktable (current git master with some extensions not related to OpenCL) with the

Re: [darktable-dev] How does the Gaussian filter work?

Dear Johannes, Am 15.10.18 um 10:08 schrieb johannes hanika: this is an IIR filter (infinite impulse response, as opposed to the straight forward FIR, finite impulse response, which would be for instance a 5-tap b-spline filter) which approximates a gaussian. it's especially well suited for

[darktable-dev] How does the Gaussian filter work?

Hi, today I had look at the code in gaussian.c, which (to my surprise) is not just a straight-forward implementation of a Gaussian filter. After some google search I realized that several approximate algorithms exist that are able to approximate a Gaussian filter within a computing time

Re: [darktable-dev] GMIC module

Hi Johannes, Am 05.09.2018 um 12:08 schrieb johannes hanika: as to your question, integrate gmic or reimplement. does it make much of a difference? main differences: * using libgmic introduces an additional dependency. * libgimic is written in C++, GMIC module needs to be implemented in

Re: [darktable-dev] GMIC module

Hi Andreas, Am 05.09.2018 um 08:48 schrieb Andreas Schneider: However, something else, I'm still looking forward to get the guided filter for parametric and drawn masks, any news on that front? :-) still lacking time and sufficient knowledge in OpenCL programming to implement this feature

Re: [darktable-dev] Base curve

Hi, Am 30.08.2018 um 07:27 schrieb Andreas Schneider: On Thursday, 30 August 2018 00:36:49 CEST Heiko Bauke wrote: However, houz and hanatos tell everyone to use darktable-chart instead :-) darktable-chart might be the better way to calibrate your camera. If you do not own a color checker

Re: [darktable-dev] Base curve

Hi, Am 26.08.2018 um 18:58 schrieb Holger Klemm: Hello, I would like to create a custom base curve for my Canon EOS 5D Mark IV. I followed the instructions, but in Darktable only get a base curve with a horizontal line and the image is black. which instructions have you followed? Which

[darktable-dev] G'MIC module

Hi, G'MIC is an open-source framework for image processing, which can be also used via a popular gimp plugin. I have written a darktable module, which allows to apply G'MIC filters in darktable. I have written this module mainly for academic reasons to be able to test which G'MIC filters

Re: [darktable-dev] Apple will be deprecating and removing OpenCL

Hi, Am 05.06.2018 um 09:56 schrieb johannes hanika: On Tue, Jun 5, 2018 at 9:35 AM, Sarge Borsch wrote: https://developer.apple.com/macos/whats-new/ Apps built using OpenGL and OpenCL will continue to run in macOS 10.14, but these legacy technologies are deprecated in macOS 10.14. Games and

Re: [darktable-dev] Showing exposure bias

Hi, Am 18.05.2018 um 19:54 schrieb Šarūnas: I have always missed seeing exposure bias value in darktable. Does anyone else think it would be good to have that shown in 'image information' on the left? Perhaps there is also a nifty way of indicating exp. bias somehow in histogram? knowing the

Re: [darktable-dev] Re: Custom Image Order by Drag and Drop

Hi, Am 15.04.2018 um 22:16 schrieb Mario Lüder: Thanks for your interest. You may find my patch attached. looks interesting and potentially useful. I think the canonical way to contribute code to draktabe is to open a pull request on github, see https://github.com/darktable-org/darktable/

Re: [darktable-dev] Show maximum possible export size in light table?

Am 12.01.2018 um 14:29 schrieb Mark Feit: A really, really good solution to this would be to dump all available image metadata into a full-text indexer and allow the user to filter using queries.  Done right, it gives users immense flexibility and saves having to write and maintain

Re: [darktable-dev] Show maximum possible export size in light table?

Hi, Am 11.01.2018 um 20:05 schrieb Simon Harhues: If it is about selecting images, how about adding export size as filter option for the collection module? Instead of pixels, mm/inch + dpi might be an alternative, although I have no real idea how to put both in one drop down. I totally agree.

Re: [darktable-dev] Show maximum possible export size in light table?

Hi, Am 11.01.2018 um 17:46 schrieb August Schwerdfeger: If I did that, I still could not determine the size until *after* the export, by examining the exported image. What I am asking about is a way to determine the size within Darktable itself, without having to do an export. this is

Re: [darktable-dev] Show maximum possible export size in light table?

Hi, Am 11.01.2018 um 17:10 schrieb August Schwerdfeger: For me, the use case is determining, in a speedy and convenient manner, the maximum size at which I can print a cropped photo. if you want to export at maximal size without upscaling set max size to zero, or set these dimensions to very

Re: [darktable-dev] Manual lens corrections - feature request

Hi, Am 15.11.2017 um 16:59 schrieb Bernhard: Heiko Bauke schrieb am 15.11.2017 um 13:35: How would you understand »in-camera RAW image development«? usually you determine if you shoot RAW, JPEG or both. Some new cameras offer the possibility to shoot RAW and get JPEGs _after_ the shot by e.g

Re: [darktable-dev] Manual lens corrections - feature request

Hi, Am 15.11.2017 um 12:28 schrieb Roman Lebedev: On Wed, Nov 15, 2017 at 2:14 PM, Heiko Bauke <heiko.ba...@mail.de> wrote: [...] Contrary to the common believe that in-camera corrections are applied to JPEGs but not to the RAW file, in-camera lens correction in the EOS-1D X M

Re: [darktable-dev] Manual lens corrections - feature request

Hi, Am 15.11.2017 um 11:25 schrieb Jean-Luc Coulon (f5ibh): Personnaly, I think it is a bad idea [tm] to include anything in the raw file. If you change your mind, you cannot get back... I totally agree with that one should apply corrections to RAW files that are eventually baked into the

Re: [darktable-dev] Manual lens corrections - feature request

Hi, Am 14.11.2017 um 20:39 schrieb bigmack...@mail.com: New user here, so apologies if I'm posting to the wrong list! I've just switched fully from Lightroom 6 to Darktable 2.2.5 under Linux. Kudos to the developers - it's superb. The one and only feature I'm missing in Darktable is the

Re: [darktable-dev] idea: guided filter instead or (or in addition to) bilateral

Hi, Am 07.11.2017 um 18:05 schrieb Sarge Borsch: Looks like there's a superior alternative to bilateral filter which produces less gradient reversal artifacts when used for tone mapping http://kaiminghe.com/publications/eccv10guidedfilter.pdf http://kaiminghe.com/eccv10/index.html I'm no good

Re: [darktable-dev] Export masks

Hi, Am 02.11.2017 um 12:38 schrieb Martin Marmsoler: Another question: is it possible to combine multiple parametric masks (for example to mask multiple colors)? not directly. As a work-around one can apply several instances of a module with different masks. Heiko -- -- Number

Re: [darktable-dev] Deconvolution and Python framework

Hi, Am 11.10.2017 um 19:11 schrieb Martin Marmsoler: Gimp use python as scripting language. It might be easier to port for Gimp? by the way: there is a Richardson Lucy sharpening filter in G'MIC. (As far as I understand this is a non-blind deconvolution algorithm.) Heiko -- --

Re: [darktable-dev] Deconvolution and Python framework

Dear Aurélien, Am 10.10.2017 um 10:25 schrieb Aurélien PIERRE: Following my work from this Summer, I'm glad to propose my first blind deconvolution algorithm, written in Python, based on papers from 2011-2014  : https://github.com/aurelienpierre/Image-Cases-Studies TL;DR : Blind

Re: [darktable-dev] compiler warnings regarding variable length arrays

Hi, Am 22.09.2017 um 15:35 schrieb Tobias Ellinghaus: No, you are missing the point of those pragmas: darktable from git always builds with "-Werror", thus the "-Wvla" switch actually throws an hard error when using VLAs. With the pragma we are relaxing that back to a warning again to be able

Re: [darktable-dev] compiler warnings regarding variable length arrays

Hi, Am 22.09.2017 um 10:15 schrieb Tobias Ellinghaus: IIRC there was some problem with obscure alternate libc implementations that had too little stack size or something like that. yes, something like that:

[darktable-dev] shell scripts

Hi, at the moment I am reviewing the shell scrips in the darktable source, mainly by employing the shellcheck tool. In this way, I found some minor (manly stylistic) issues. So far I found only one more serious issue in the statement if [ -n "`echo -e $NEW_VERSION | grep Format`" ]; then

Re: [darktable-dev] film emulation

Dear Johannes, Am 08.09.2017 um 15:00 schrieb johannes hanika: awesome, thanks! the hope with the clustered fit would be that the lut is generally smooth enough to be represented with lower sampling density. did you look at the max delta E error (distance in Lab colour space)? darktable-chart

Re: [darktable-dev] film emulation

Hi, Am 02.09.2017 um 21:13 schrieb johannes hanika: that means you are dropping the tonecurve information? or is that baked into the clut, too? yes I just dropped the tonecurve information because this gave me the best results in some test cases. Investigating the source code of

Re: [darktable-dev] possible bug in color look up table module

Dear Johannes Am 31.07.2017 um 04:18 schrieb johannes hanika: yeah the solver sucks. I think I was able to fix it. See https://github.com/rabauke/darktable/tree/fix_colorchecker I implemented for darktable the approach to calculate the expansion coefficients which I outlined in an other

Re: [darktable-dev] possible bug in color look up table module

Dear Roman, Am 31.07.2017 um 17:45 schrieb Roman Lebedev: I suspect you (or your editor) have run clang-format/etc on that file. Don't do that. mentioning clang-format I remember I run clang-format on that file indeed. I did to ensure that my changes are compatible with darktable coding

Re: [darktable-dev] possible bug in color look up table module

Dear Johannes, Am 31.07.2017 um 04:18 schrieb johannes hanika: oh, nice, thanks for looking into this! i can't parse your diff, it has so many white space changes. could you maybe fix it or explain what it does? is it just a special case for the zero-patch case? yeah the solver sucks.

Re: [darktable-dev] possible bug in color look up table module

Dear Johannes, Am 12.07.2017 um 10:06 schrieb johannes hanika: sounds weird, will try to reproduce. the fitting of this function is using a spline, which may be prone to ringing, in between the colours you fixed. it has a linear part that fixes this issue for purely b/w, but may lead to issues

Re: [darktable-dev] possible bug in color look up table module

Hi, Am 12.07.2017 um 10:06 schrieb johannes hanika: sounds weird, will try to reproduce. the fitting of this function is using a spline, which may be prone to ringing, in between the colours you fixed. it has a linear part that fixes this issue for purely b/w, but may lead to issues for b/w +

[darktable-dev] possible bug in color look up table module

Hi, recently I became aware of some (to me) unexpected behavior of the color look up table module. To reproduce the (possible) bug: * Activate the color look up module with its standard parameters (which causes no color change to the image). * Remove successively all color patches by a

  1   2   >