Re: [darktable-dev] Re: sRGB internal color profile
Am Sonntag, 8. Mai 2016, 17:40:51 schrieb jmsarat: > Ok, it was just a wild guess. If DT is using its own color management > for export when lcms2 is not selected, what are the differences or > benefits of using lcms2? It is faster, but somewhat limited, most obvious limitation is the lack of configurable rendering intent. And it doesn't work for all color profiles. For those not supported by our code we fall back to using lcms2. So the results _should_ be the same. If they aren't in your case that's probably a bug. > Jean-Marc > > Le 08/05/2016 à 16:08, Tobias Ellinghaus a écrit : > > Am Sonntag, 8. Mai 2016, 15:54:28 schrieb jmsarat: > >> Hi Matthias, > >> > >> With a clean $HOME/.config/darktable, the option lcms2 is deactivated by > >> default therefore the export function use lcms1-1.19. > > > > That is a misunderstanding. darktable might use some internal functions > > instead of lcms2, but it will never use lcms1. > > > > [...] > > > > Tobias > > ___ > darktable developer mailing list > to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org signature.asc Description: This is a digitally signed message part.
Re: [darktable-dev] Re: sRGB internal color profile
Ok, it was just a wild guess. If DT is using its own color management for export when lcms2 is not selected, what are the differences or benefits of using lcms2? Jean-Marc Le 08/05/2016 à 16:08, Tobias Ellinghaus a écrit : Am Sonntag, 8. Mai 2016, 15:54:28 schrieb jmsarat: Hi Matthias, With a clean $HOME/.config/darktable, the option lcms2 is deactivated by default therefore the export function use lcms1-1.19. That is a misunderstanding. darktable might use some internal functions instead of lcms2, but it will never use lcms1. [...] Tobias ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] Re: sRGB internal color profile
Am 08.05.2016 um 15:54 schrieb jmsarat: > Hi Matthias, > > With a clean $HOME/.config/darktable, the option lcms2 is deactivated by > default therefore the export function use lcms1-1.19. The resulting image > does not have defect in the blue shade but if the lcms2 option is activated > then the problem appears. I do not see a difference with lcms2 activated or deactivated with either sRGB or Adobe RGB. Matthias ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Re: sRGB internal color profile
Am Sonntag, 8. Mai 2016, 15:54:28 schrieb jmsarat: > Hi Matthias, > > With a clean $HOME/.config/darktable, the option lcms2 is deactivated by > default therefore the export function use lcms1-1.19. That is a misunderstanding. darktable might use some internal functions instead of lcms2, but it will never use lcms1. [...] Tobias signature.asc Description: This is a digitally signed message part.
Re: [darktable-dev] Re: sRGB internal color profile
On Sun, May 8, 2016 at 4:54 PM, jmsarat wrote: > Hi Matthias, > > With a clean $HOME/.config/darktable, the option lcms2 is deactivated by > default >therefore the export function use lcms1-1.19. Where from are you getting this? I do not think dt ever used lcms1. > The resulting image > does not have defect in the blue shade but if the lcms2 option is activated > then the problem appears. > > I tried with a fresh DT 2.0.4 compiled on Mageia 5 with lcms2-2.7 and with > the latest dev version 2.1.0+1082~g6e50d7a. The problem is there with both > versions. > > Jean-Marc Roman. > > > > Le 08/05/2016 à 13:09, Matthias Bodenbinder a écrit : >> >> Hi Jean-Marc, >> >> I can not reproduce your JPG output. Not even with your xmp file. I am >> using DT 2.0.4, self compiled. >> >> Have you tried with a different user resp. with a clean >> $HOME/.config/darktable ? >> >> Matthias >> >> >> Am 08.05.2016 um 12:35 schrieb jmsarat: >>> >>> Hi Jo, >>> >>> With this clean xmp : https://1fichier.com/?rd1q8touto >>> >>> I obtain this image : https://1fichier.com/?3uqu4ijx0g >>> >>> No style on export and using the image parameters for color profile >>> (sRGB(web)) and rendering intent (perceptual). >>> >>> The raw image is there : https://1fichier.com/?5n9xbgf9ej >>> >>> The problem is visible in the blue shade but could be present in other >>> colors. >>> >>> Jean-Marc >>> >>> Le 08/05/2016 à 08:26, johannes hanika a écrit : heya, this is what it looks like for me: https://jo.dreggn.org/img_0001.jpg much like your not broken reference image? do you apply any styles on export maybe? if you have an exported jpg i could check the history stack in the xmp stored in that one.. cheers, jo On Sat, May 7, 2016 at 4:42 AM, jmsarat wrote: > > Bonjour Johannes, > > The problem occurs when exporting an image and using the internal sRGB > color > profile. The problem disappear if I select another sRGB color profile > (Sony > sRGB or RT sRGB). > As the source is a sony arw raw image, I do not specify a particular > icc > profile and use the standard matrix. I tried sony dcp profiles for > A6000 > converted to icc but if the result is different the problem has been > moved > to other places in the blue shades. > Attached the xmp corresponding to the image. This is a simplified xmp > with > the minimal options that create the problem in blue shades. > The arw file is there : https://1fichier.com/?8khnco34cy > > darktable version 2.1.0+1080~gfedb40 > > Jean-marc > > > > > Le 27/04/2016 à 15:06, johannes hanika a écrit : >> >> heya, >> >> i can't reproduce. is there anything else? can you share an .xmp >> sidecar file so we can precisely reproduce your steps? and just to >> double check: you are talking export, not display, right? so it can't >> be a display profile issue. are you using any particular icc profile >> as input colour space? >> >> -jo >> >> On Wed, Apr 27, 2016 at 2:06 PM, Moritz Moeller >> >> wrote: >>> >>> On 25/04/16 12:43, jmsarat wrote: [...] lower image result with an external profile (Sony Corp sRGB). [...] >>> >>> >>> Can you share the source of the Sony profile? >>> >>> I have some images that have always shown exactly the artifacts you >>> documented and which I could never develop through DT therefore. I >>> thought >>> it was some module inside DT causing this. If it is as simple as >>> changing >>> the profile, that would be really awesome. >>> >>> .mm >>> >>> >>> >>> >>> ___ >>> 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 >> >> > > ___ > 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-
Re: [darktable-dev] Re: sRGB internal color profile
Hi Matthias, With a clean $HOME/.config/darktable, the option lcms2 is deactivated by default therefore the export function use lcms1-1.19. The resulting image does not have defect in the blue shade but if the lcms2 option is activated then the problem appears. I tried with a fresh DT 2.0.4 compiled on Mageia 5 with lcms2-2.7 and with the latest dev version 2.1.0+1082~g6e50d7a. The problem is there with both versions. Jean-Marc Le 08/05/2016 à 13:09, Matthias Bodenbinder a écrit : Hi Jean-Marc, I can not reproduce your JPG output. Not even with your xmp file. I am using DT 2.0.4, self compiled. Have you tried with a different user resp. with a clean $HOME/.config/darktable ? Matthias Am 08.05.2016 um 12:35 schrieb jmsarat: Hi Jo, With this clean xmp : https://1fichier.com/?rd1q8touto I obtain this image : https://1fichier.com/?3uqu4ijx0g No style on export and using the image parameters for color profile (sRGB(web)) and rendering intent (perceptual). The raw image is there : https://1fichier.com/?5n9xbgf9ej The problem is visible in the blue shade but could be present in other colors. Jean-Marc Le 08/05/2016 à 08:26, johannes hanika a écrit : heya, this is what it looks like for me: https://jo.dreggn.org/img_0001.jpg much like your not broken reference image? do you apply any styles on export maybe? if you have an exported jpg i could check the history stack in the xmp stored in that one.. cheers, jo On Sat, May 7, 2016 at 4:42 AM, jmsarat wrote: Bonjour Johannes, The problem occurs when exporting an image and using the internal sRGB color profile. The problem disappear if I select another sRGB color profile (Sony sRGB or RT sRGB). As the source is a sony arw raw image, I do not specify a particular icc profile and use the standard matrix. I tried sony dcp profiles for A6000 converted to icc but if the result is different the problem has been moved to other places in the blue shades. Attached the xmp corresponding to the image. This is a simplified xmp with the minimal options that create the problem in blue shades. The arw file is there : https://1fichier.com/?8khnco34cy darktable version 2.1.0+1080~gfedb40 Jean-marc Le 27/04/2016 à 15:06, johannes hanika a écrit : heya, i can't reproduce. is there anything else? can you share an .xmp sidecar file so we can precisely reproduce your steps? and just to double check: you are talking export, not display, right? so it can't be a display profile issue. are you using any particular icc profile as input colour space? -jo On Wed, Apr 27, 2016 at 2:06 PM, Moritz Moeller wrote: On 25/04/16 12:43, jmsarat wrote: [...] lower image result with an external profile (Sony Corp sRGB). [...] Can you share the source of the Sony profile? I have some images that have always shown exactly the artifacts you documented and which I could never develop through DT therefore. I thought it was some module inside DT causing this. If it is as simple as changing the profile, that would be really awesome. .mm ___ 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 ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] Re: sRGB internal color profile
Hi Jean-Marc, I can not reproduce your JPG output. Not even with your xmp file. I am using DT 2.0.4, self compiled. Have you tried with a different user resp. with a clean $HOME/.config/darktable ? Matthias Am 08.05.2016 um 12:35 schrieb jmsarat: > Hi Jo, > > With this clean xmp : https://1fichier.com/?rd1q8touto > > I obtain this image : https://1fichier.com/?3uqu4ijx0g > > No style on export and using the image parameters for color profile > (sRGB(web)) and rendering intent (perceptual). > > The raw image is there : https://1fichier.com/?5n9xbgf9ej > > The problem is visible in the blue shade but could be present in other colors. > > Jean-Marc > > Le 08/05/2016 à 08:26, johannes hanika a écrit : >> heya, >> >> this is what it looks like for me: >> >> https://jo.dreggn.org/img_0001.jpg >> >> much like your not broken reference image? >> >> do you apply any styles on export maybe? if you have an exported jpg i >> could check the history stack in the xmp stored in that one.. >> >> cheers, >> jo >> >> >> >> On Sat, May 7, 2016 at 4:42 AM, jmsarat wrote: >>> Bonjour Johannes, >>> >>> The problem occurs when exporting an image and using the internal sRGB color >>> profile. The problem disappear if I select another sRGB color profile (Sony >>> sRGB or RT sRGB). >>> As the source is a sony arw raw image, I do not specify a particular icc >>> profile and use the standard matrix. I tried sony dcp profiles for A6000 >>> converted to icc but if the result is different the problem has been moved >>> to other places in the blue shades. >>> Attached the xmp corresponding to the image. This is a simplified xmp with >>> the minimal options that create the problem in blue shades. >>> The arw file is there : https://1fichier.com/?8khnco34cy >>> >>> darktable version 2.1.0+1080~gfedb40 >>> >>> Jean-marc >>> >>> >>> >>> >>> Le 27/04/2016 à 15:06, johannes hanika a écrit : heya, i can't reproduce. is there anything else? can you share an .xmp sidecar file so we can precisely reproduce your steps? and just to double check: you are talking export, not display, right? so it can't be a display profile issue. are you using any particular icc profile as input colour space? -jo On Wed, Apr 27, 2016 at 2:06 PM, Moritz Moeller wrote: > On 25/04/16 12:43, jmsarat wrote: >> >> [...] lower image >> result with an external profile (Sony Corp sRGB). [...] > > > Can you share the source of the Sony profile? > > I have some images that have always shown exactly the artifacts you > documented and which I could never develop through DT therefore. I > thought > it was some module inside DT causing this. If it is as simple as changing > the profile, that would be really awesome. > > .mm > > > > ___ > 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
