Re: [darktable-dev] "basecurve" is automatically applied when "auto_apply" is off
* philippe.weyl...@laposte.net [01-13-20 13:02]: > > Also, make sure you don't have any forgotten auto-applied presets in that > > module, of course. > > You are right. But if I'm not mistaken they are locked ... How to remove > auto-applied ? > > - Mail original - > > De: "jys" > À: darktable-dev@lists.darktable.org > Envoyé: Dimanche 12 Janvier 2020 21:41:07 > Objet: Re: [darktable-dev] "basecurve" is automatically applied when > "auto_apply" is off > > On Sun, Jan 12, 2020, at 00:20, Mike Romanov wrote: > > > The plugin "basecurve" is automatically applied when both "auto_apply..." > > checkboxes is off. > > I've heard of this fixing itself after a restart of darktable, I haven't > experienced it myself. Also, make sure you don't have any forgotten > auto-applied presets in that module, of course. :-) > > -- > jys > ___ > 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 > edit the module preset and remove the information necessary to determine where to apply the preset (automagically). The same way you made the preset apply automatically. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] camera icc profile in colorin
Hi all Please help me in solving a small problem. I created an icc-profile for my camera and am trying to use it in “input color profile”. I can select it in the "input profile" list. And i created a new automatically applied preset “MyPreset”. This works fine until i transfer the working directory to a computer with different OS (Windows or Linux). All changes are transferred correctly except for “MyPreset”: the program cannot find icc-profile of the camera, although it is present in “input profile” list. And i have to choose it manually for each shot. I think this happens because database file full path to the icc-profile files, different in different operating systems. But for placing such profiles only two path options are provided: datadir and confdir. I think that the solution may be to save "datadir" or "confdir" and replace them with real path when reading the profile from db. Problem is that i have not yet found where this parameter is formed for saving in db. I ask to prompt the search direction. -- Mike Romanov ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.or
[darktable-dev] Re[2]: [darktable-dev] "basecurve" is automatically applied when "auto_apply" is off
Thanks, you're right. I forgot about the test preset. :-/ >Понедельник, 13 января 2020, 3:52 +07:00 от jys : > >On Sun, Jan 12, 2020, at 00:20, Mike Romanov wrote: > >> The plugin "basecurve" is automatically applied when both "auto_apply..." >> checkboxes is off. >I've heard of this fixing itself after a restart of darktable, I haven't >experienced it myself. Also, make sure you don't have any forgotten >auto-applied presets in that module, of course. :-) > >-- >jys >___ >darktable developer mailing list >to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org > -- Mike Romanov ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.or
Re: [darktable-dev] 3D LUT
Hi Phillipe, nice to hear that the 3dl support made some progress. Sadly it is not possible for me at this time to compile from source because i am tight in time. But if you, or anyone else, can send me a compiled version (Win64) i will be happy to test it against all 3dl files i have. Regards Jan On 13-Jan-20 14:49, philippe.weyl...@laposte.net wrote: Hi Jan, I've made a try to implement 3dl files. see PR #4096. Your references and your code helped me a lot. That works for me (your 3dl file plus those from the link given by Guido), but I haven't a lot of them to test. If you have the possibility to build that PR and give me a feedback that would be great. Thanks Philippe - Mail original - De: "Jan Ingwer Baer" À: "philippe weyland" Envoyé: Samedi 11 Janvier 2020 10:22:22 Objet: Re: [darktable-dev] 3D LUT Hi Philippe, some more info about 3dl files : https://github.com/AcademySoftwareFoundation/OpenColorIO/blob/RB-1.1/src/core/FileFormat3DL.cpp Regards Jan On 10-Jan-20 10:54, philippe.weyl...@laposte.net wrote: Hi Jan, I haven't found the specification of 3dl file but I understand the coordinates of the cube can be non linear. That's the role of the first line of data (0 64 128 192 256 320 384 448 512 576 640 704 768 832 896 960 1023 for 17 vertices in your sample file). I've read that we could even have 3 lines like this, one per axe. If I've understood properly, the lut3d transfer function is not able to do that today. Regards Philippe - Mail original - De: "Jan Ingwer Baer" À: "Philippe Weyland" Envoyé: Mercredi 8 Janvier 2020 20:36:04 Objet: Re: [darktable-dev] 3D LUT Attached an example 3DL-file and the source of LUT-Import from my Irfanview-Plugin. Regards Jan On 08-Jan-20 16:43, Philippe Weyland wrote: Any plans to extend it to the compressed 3D-LUTs? Just merged (3.0.1) Is it possible to integrate the compression of HALDCLUT- and CUBE-files? Possible a button 'Compress-3D-LUT"? Compression is a really long process and so far it has been kept outside dt. See GMIC commands for that. Please add additional formats for the 3D-LUT files: tif and 3dl Could you share the sites providing such lut formats ? ___ 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 ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] 3D LUT
Hi Jan, I've made a try to implement 3dl files. see PR #4096. Your references and your code helped me a lot. That works for me (your 3dl file plus those from the link given by Guido), but I haven't a lot of them to test. If you have the possibility to build that PR and give me a feedback that would be great. Thanks Philippe - Mail original - De: "Jan Ingwer Baer" À: "philippe weyland" Envoyé: Samedi 11 Janvier 2020 10:22:22 Objet: Re: [darktable-dev] 3D LUT Hi Philippe, some more info about 3dl files : > https://github.com/AcademySoftwareFoundation/OpenColorIO/blob/RB-1.1/src/core/FileFormat3DL.cpp > Regards Jan On 10-Jan-20 10:54, philippe.weyl...@laposte.net wrote: > Hi Jan, > I haven't found the specification of 3dl file but I understand the > coordinates of the cube can be non linear. > That's the role of the first line of data (0 64 128 192 256 320 384 448 512 > 576 640 704 768 832 896 960 1023 for 17 vertices in your sample file). > I've read that we could even have 3 lines like this, one per axe. > If I've understood properly, the lut3d transfer function is not able to do > that today. > Regards > Philippe > > - Mail original - > > De: "Jan Ingwer Baer" > À: "Philippe Weyland" > Envoyé: Mercredi 8 Janvier 2020 20:36:04 > Objet: Re: [darktable-dev] 3D LUT > > Attached an example 3DL-file and the source of LUT-Import from my > Irfanview-Plugin. > > Regards > Jan > On 08-Jan-20 16:43, Philippe Weyland wrote: >>> Any plans to extend it to the compressed 3D-LUTs? >> >> Just merged (3.0.1) >> >>> Is it possible to integrate the compression of HALDCLUT- and >> CUBE-files? Possible a button 'Compress-3D-LUT"? >> >> Compression is a really long process and so far it has been kept >> outside dt. See GMIC commands for that. >> >>> Please add additional formats for the 3D-LUT files: tif and 3dl >> >> >> Could you share the sites providing such lut formats ? >> >> >> ___ >> 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
Re: [darktable-dev] Change of behviaour reg. (implicit) discard of history – intentional?
On 13/01/2020 12:28, Patrick Shanahan wrote: * Jørn Villesen Christensen [01-13-20 05:14]: Hi there, I have been using Darktable 3.0 for a while – and thank you for your great work. Darktable has some nice new features that I really enjoy. However, there is one feature that I find a bit annoying, it has to do with (implicit) discard of history. Example: 1. I have a photo with say 20 edits in the history. 2. The last thing I have done was to play with a module, lets say Tone Curve, but decided against it. I therefore click on entry 19 in the history, and I get the photo before me playing around. 3. I leave the photo for a while and then come back to it. (Actually not necessary for anything else than demonstrating my poor memory :-D ). 4. When I come back to it, I decide to add a bit of noise filtering (a step I often add in the end because it is heavy on the processing). When I enable the de-noise filter, the whole image change lighting – and it takes me a second or two to realise that it is because the entry no. 20 (the reverted Tone curve edit) has not been discarded, but instead the history has been fast-forwarded and the de-noise has been added as entry 21. In this scenario, I am used to edit no. 20 being discarded, and the de-noise filter just applied on the image "as is". *Unless* you "compress" the history stack, the focus location on the stack is only pertinent if you make a new edit, then that "net edit" will replace everything above your location on the stack. Hm... now I cannot reproduce the thing either. It did happen to me a couple of times the last couple of days (and this morning) but it looks like I should have taken my time to make a "proof of concept" of it before mailing here. Sorry for the noise and thank you for your replies. I will take up the issue again if I can nail it better. ~Jørn ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Change of behviaour reg. (implicit) discard of history – intentional?
* Jørn Villesen Christensen [01-13-20 05:14]: > Hi there, > > I have been using Darktable 3.0 for a while – and thank you for your great > work. Darktable has some nice new features that I really enjoy. > > However, there is one feature that I find a bit annoying, it has to do with > (implicit) discard of history. > > Example: > > 1. I have a photo with say 20 edits in the history. > 2. The last thing I have done was to play with a module, lets say Tone >Curve, but decided against it. I therefore click on entry 19 in the >history, and I get the photo before me playing around. > 3. I leave the photo for a while and then come back to it. (Actually >not necessary for anything else than demonstrating my poor memory :-D ). > 4. When I come back to it, I decide to add a bit of noise filtering (a >step I often add in the end because it is heavy on the processing). >When I enable the de-noise filter, the whole image change lighting – >and it takes me a second or two to realise that it is because the >entry no. 20 (the reverted Tone curve edit) has not been discarded, >but instead the history has been fast-forwarded and the de-noise has >been added as entry 21. > > In this scenario, I am used to edit no. 20 being discarded, and the de-noise > filter just applied on the image "as is". *Unless* you "compress" the history stack, the focus location on the stack is only pertinent if you make a new edit, then that "net edit" will replace everything above your location on the stack. ie: the stack has 21 entries and you have focused on 18 and leave that image, when you return you will still have 21 entries. If you focuse on 18 and compress the stack, you will then have 18 or less depending on whether you have utilized a particular module more than one time without initiating a multiple/new instance. clear as mud? placing the focus on an entry in the history stack and leaving the image does not change the history stack. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Change of behviaour reg. (implicit) discard of history – intentional?
Am 13.01.20 um 11:12 schrieb Jørn Villesen Christensen: Hi there, I have been using Darktable 3.0 for a while – and thank you for your great work. Darktable has some nice new features that I really enjoy. However, there is one feature that I find a bit annoying, it has to do with (implicit) discard of history. Example: 1. I have a photo with say 20 edits in the history. 2. The last thing I have done was to play with a module, lets say Tone Curve, but decided against it. I therefore click on entry 19 in the history, and I get the photo before me playing around. 3. I leave the photo for a while and then come back to it. (Actually not necessary for anything else than demonstrating my poor memory :-D ). 4. When I come back to it, I decide to add a bit of noise filtering (a step I often add in the end because it is heavy on the processing). When I enable the de-noise filter, the whole image change lighting – and it takes me a second or two to realise that it is because the entry no. 20 (the reverted Tone curve edit) has not been discarded, but instead the history has been fast-forwarded and the de-noise has been added as entry 21. Can't confirm this behavior with current git master. If there is a bug in 3.0, it's gone in the next release. In this scenario, I am used to edit no. 20 being discarded, and the de-noise filter just applied on the image "as is". I see there has been some changes in the history section (in the visual appearance, at least), the questions are: * Is this intentional? * If no, can we revert to the original behaviour? * If yes, can we have an option to revert it? (Sorry). Thank you, once again, for your amazing work. BR Jørn ___ 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] 3D LUT
Hi Guido, Thanks for the link. This site provides luts to be applied on raw data for fuji camera. Have you already tried these luts (the png ones) on dt moving lut3d before colorin ? Are you happy with the results ? I'm wondering how colorin must be set up in that case (not to apply color matrix that the lut is supposed to equivalent). Input profile = working profile ? Making progress on 3dl stuff. Philippe - Mail original - De: "Guido Scholz" À: darktable-dev@lists.darktable.org Envoyé: Mercredi 8 Janvier 2020 20:53:50 Objet: Re: [darktable-dev] 3D LUT Am Wed, 08. Jan 2020 um 16:43:25 +0100 schrieb Philippe Weyland: Hi Philippe, > > Please add additional formats for the 3D-LUT files: tif and 3dl > Could you share the sites providing such lut formats ? Here you can find some 3dl files: https://blog.sowerby.me/fuji-film-simulation-profiles/ Guido -- http://wie-im-flug.net/ http://www.lug-burghausen.org/ ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] Change of behviaour reg. (implicit) discard of history – intentional?
Hi there, I have been using Darktable 3.0 for a while – and thank you for your great work. Darktable has some nice new features that I really enjoy. However, there is one feature that I find a bit annoying, it has to do with (implicit) discard of history. Example: 1. I have a photo with say 20 edits in the history. 2. The last thing I have done was to play with a module, lets say Tone Curve, but decided against it. I therefore click on entry 19 in the history, and I get the photo before me playing around. 3. I leave the photo for a while and then come back to it. (Actually not necessary for anything else than demonstrating my poor memory :-D ). 4. When I come back to it, I decide to add a bit of noise filtering (a step I often add in the end because it is heavy on the processing). When I enable the de-noise filter, the whole image change lighting – and it takes me a second or two to realise that it is because the entry no. 20 (the reverted Tone curve edit) has not been discarded, but instead the history has been fast-forwarded and the de-noise has been added as entry 21. In this scenario, I am used to edit no. 20 being discarded, and the de-noise filter just applied on the image "as is". I see there has been some changes in the history section (in the visual appearance, at least), the questions are: * Is this intentional? * If no, can we revert to the original behaviour? * If yes, can we have an option to revert it? (Sorry). Thank you, once again, for your amazing work. BR Jørn ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] Camera's base curve preset produces different results in DT 3.0
Hi. In DT 2.6.2 color grading of my D7200 RAW files produced more natural results and was quite close to that what Nikon's native Capture NX-D does. Have no idea how to restore my image processing workflow on Darktable 3.0 to get identical result as they were DT 2.6.2. I did try all chroma preservation options in the base curve module, none of them was as close to the camera's JPEG as the DT 2.6.2 did by default. The image still looks less saturated than the JPEG. I have turned off all automatic JPEG processing enhacements at my camera to make my results more predictable, no extra saturation is added, usually I slightly add saturation in post. When I try to increase the saturation then the skin tones get weird - everything what is red on the face (lips, spots e.t.c.) are being accentuated and the skin still looks more pale and grey that it was in DT 2.6.2 when i did increase saturation. The point is that I can't get to the state when the colors at starting point were OK for me as it was in DT 2.6.2. I did a lot of experiments and still can't find a way to match the skin tones. The base curve presets for my D7200 in both DT versions look identical. The problem is that they produce now different results no matter how I change the base curve module options. If I try to fix skin tones in DT 3.0 the color adjustments are shifting colors on other image parts and e.g. clothes and background get wrong colors. I did not have such notable issues with DT 2.6.2. Regards, Victor ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
