Re: [darktable-dev] Re: Improving built-in color profiles
Hi, I would like to follow your approach and compare the Darktable profiles for my Nikon D750 with the ones I did on my own and your method. I found the camera raw plug-in downloader from adobe in version 10.3 and downloaded it for both, mac and windows. Now Im stuck: Neither using wine and the nullsoft installer nor using xar to extract the macOSX package gave me the dcp files. Am I missing something? Could you please give some more details on how to get your color matrices? Cheers, Dave 2018-05-04 21:10 GMT+02:00 Sarge Borsch : > So, I tried to edit an ICC file in a hex editor to put the values from > that website, and, just as expected, got nonsensical results. > > After that I tried another idea to snatch better color profiles — I > searched the web for Adobe Camera Raw package, extracted the profiles from > it (they are in .dcp format), and figured that it's possible to convert > them to ICC by dcamprof. > They seem to work very well — better than the currently built-in input > profiles for sony a5100 in darktable. > Now what do you think about the copyright status of these converted ICC > profiles? Can they legally be distributed with darktable, or should I keep > them only for myself? > They are a lot smaller than the source .dcc files, probably because they > don't keep nothing valuable except the color matrices. So are 3x3 numeric > matrices copyrightable? > > If you think these profiles can be officially added to darktable, I may > fix the name tags and submit a pull request. > > > On 4 May 2018, at 17:14, Sarge Borsch wrote: > > > > Hi. > > I see that there are measured color responses at > https://www.dxomark.com/Cameras/Sony/A5100---Measurements > > Hence the question: is it a good idea to try to take the built-in > profile and replace the primaries with these measured values, in order to > get closer to the in-camera JPEG color rendering? (or are they already > used?) > > > > I'm asking that because I've noticed that none of the built-in input > color profiles for sony a5100 allows me to get close to the in-camera JPEG > colors. > > The 2 of them which are the closest to the correct rendering (that is, > matching camera JPEG, which is quite good when judging by eye) are the > "standard color matrix" and "linear Rec2020 RGB". > > Both of them wildly differ from the in-camera JPEG in deep blue colors: > "standard color matrix" causes them to be clipped and to look really > unnatural, and "linear Rec2020 RGB" looks more or less natural, but the hue > is obviously different (blue gets moved to cyan). Hence I started to wonder > how easy is it to get a better color profile. > > > > I know that ideally this should be done with a color chart, but I don't > have one and don't have spare money for it at the moment. > > > > Also I can share a shot of the example object (Raw + JPEG) which has > such problematic color if anyone wants to test it, too. > > > ___ > darktable developer mailing list > to unsubscribe send a mail to darktable-dev+unsubscribe@ > lists.darktable.org > > ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Re: Improving built-in color profiles
Mac packages are easier to extract without even installing (and installing proprietary software is not very good for security, that's why I went straight to trying to extract only the files I wanted) It's several layers of different but relatively common archive formats: dmg, xar, gzip, cpio. You'll need to go into them roughly like this: CameraRaw_10_3.pkg -> CameraRawProfiles.pkg -> CameraProfiles At all steps ignore the file extensions and use `file` utility to test the actual file type. When unsure what file to try, aim for bigger files. Perhaps some steps are harder to do on systems other than macOS, I didn't try to extract it on other systems. After than I used `dcamprof`, it's 2 steps: convert to JSON and then use make-icc command (I had to also explicitly tell it the profile name). > On 5 May 2018, at 00:31, Coding Dave wrote: > > Hi, I would like to follow your approach and compare the Darktable profiles > for my Nikon D750 with the ones I did on my own and your method. I found the > camera raw plug-in downloader from adobe in version 10.3 and downloaded it > for both, mac and windows. Now Im stuck: Neither using wine and the nullsoft > installer nor using xar to extract the macOSX package gave me the dcp files. > Am I missing something? Could you please give some more details on how to get > your color matrices? > > Cheers, > Dave > > 2018-05-04 21:10 GMT+02:00 Sarge Borsch : > So, I tried to edit an ICC file in a hex editor to put the values from that > website, and, just as expected, got nonsensical results. > > After that I tried another idea to snatch better color profiles — I searched > the web for Adobe Camera Raw package, extracted the profiles from it (they > are in .dcp format), and figured that it's possible to convert them to ICC by > dcamprof. > They seem to work very well — better than the currently built-in input > profiles for sony a5100 in darktable. > Now what do you think about the copyright status of these converted ICC > profiles? Can they legally be distributed with darktable, or should I keep > them only for myself? > They are a lot smaller than the source .dcc files, probably because they > don't keep nothing valuable except the color matrices. So are 3x3 numeric > matrices copyrightable? > > If you think these profiles can be officially added to darktable, I may fix > the name tags and submit a pull request. > > > On 4 May 2018, at 17:14, Sarge Borsch wrote: > > > > Hi. > > I see that there are measured color responses at > > https://www.dxomark.com/Cameras/Sony/A5100---Measurements > > Hence the question: is it a good idea to try to take the built-in profile > > and replace the primaries with these measured values, in order to get > > closer to the in-camera JPEG color rendering? (or are they already used?) > > > > I'm asking that because I've noticed that none of the built-in input color > > profiles for sony a5100 allows me to get close to the in-camera JPEG colors. > > The 2 of them which are the closest to the correct rendering (that is, > > matching camera JPEG, which is quite good when judging by eye) are the > > "standard color matrix" and "linear Rec2020 RGB". > > Both of them wildly differ from the in-camera JPEG in deep blue colors: > > "standard color matrix" causes them to be clipped and to look really > > unnatural, and "linear Rec2020 RGB" looks more or less natural, but the hue > > is obviously different (blue gets moved to cyan). Hence I started to wonder > > how easy is it to get a better color profile. > > > > I know that ideally this should be done with a color chart, but I don't > > have one and don't have spare money for it at the moment. > > > > Also I can share a shot of the example object (Raw + JPEG) which has such > > problematic color if anyone wants to test it, too. > > ___ > 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] Re: Improving built-in color profiles
I'm not very surprised to see that you can get better results than the default color profiles. The out of the box colors for those Sony cameras are not very natural. Blue colors are often looking bad on a lot of Sony cameras (Nex, A6000, A6300, A7...). I'm almost never using the Sony Alpha curve. Best solutions to me are either to go for Neutral base curve, or a bit like your idea, Linear 709 as the input profile, with a lot of added saturation. So I'm quite interested by your work : ) To extract manually the profiles seems to be a bit complicated... So I will keep reading this thread ! François On Fri, May 4, 2018 at 9:11 PM Sarge Borsch wrote: > So, I tried to edit an ICC file in a hex editor to put the values from > that website, and, just as expected, got nonsensical results. > > After that I tried another idea to snatch better color profiles — I > searched the web for Adobe Camera Raw package, extracted the profiles from > it (they are in .dcp format), and figured that it's possible to convert > them to ICC by dcamprof. > They seem to work very well — better than the currently built-in input > profiles for sony a5100 in darktable. > Now what do you think about the copyright status of these converted ICC > profiles? Can they legally be distributed with darktable, or should I keep > them only for myself? > They are a lot smaller than the source .dcc files, probably because they > don't keep nothing valuable except the color matrices. So are 3x3 numeric > matrices copyrightable? > > If you think these profiles can be officially added to darktable, I may > fix the name tags and submit a pull request. > > > On 4 May 2018, at 17:14, Sarge Borsch wrote: > > > > Hi. > > I see that there are measured color responses at > https://www.dxomark.com/Cameras/Sony/A5100---Measurements > > Hence the question: is it a good idea to try to take the built-in > profile and replace the primaries with these measured values, in order to > get closer to the in-camera JPEG color rendering? (or are they already > used?) > > > > I'm asking that because I've noticed that none of the built-in input > color profiles for sony a5100 allows me to get close to the in-camera JPEG > colors. > > The 2 of them which are the closest to the correct rendering (that is, > matching camera JPEG, which is quite good when judging by eye) are the > "standard color matrix" and "linear Rec2020 RGB". > > Both of them wildly differ from the in-camera JPEG in deep blue colors: > "standard color matrix" causes them to be clipped and to look really > unnatural, and "linear Rec2020 RGB" looks more or less natural, but the hue > is obviously different (blue gets moved to cyan). Hence I started to wonder > how easy is it to get a better color profile. > > > > I know that ideally this should be done with a color chart, but I don't > have one and don't have spare money for it at the moment. > > > > Also I can share a shot of the example object (Raw + JPEG) which has > such problematic color if anyone wants to test it, too. > > ___ > 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] Re: Improving built-in color profiles
In regards to the copyright question, I looked at the output of dcamprof dcp2json and the json file has the line "ProfileCopyright": "Copyright 2009 Adobe Systems, Inc." To extract the profiles and convert them, on Linux and MacOS: Download the MacOS Adobe Camera Raw package Compile and install dcamprof and xar if they aren't on your system unzip CameraRaw_10_3_mac.zip xar -x -f CameraRaw_10_3.pkg cd CameraRawProfiles.pkg/ mv Payload Payload.gz gunzip Payload.gz cpio -i < Payload cd CameraProfiles At this point there are 2 directories, Adobe Standard and Camera. Adobe Standard has the standard Adobe profile. Camera contains subdirectories for each camera with multiple profiles. cd Adobe\ Standard dcamprof dcp2json Canon\ EOS\ 7D\ Standard.dcp 7DStandard.json dcamprof make-icc -n "Canon EOS 7D Standard" 7DStandard.json 7DStandard.icc mv 7DStandard.icc ~/.config/darktable/color/in Substitute your camera for Canon EOS 7D. I converted a couple of the profiles and tried them. They didn't make a huge difference, but then my camera is old and it's performance fairly well known. Hope this helps, Bill On Thu, May 31, 2018 at 11:15 AM, François Tissandier < francois.tissand...@gmail.com> wrote: > I'm not very surprised to see that you can get better results than the > default color profiles. The out of the box colors for those Sony cameras > are not very natural. Blue colors are often looking bad on a lot of Sony > cameras (Nex, A6000, A6300, A7...). I'm almost never using the Sony Alpha > curve. Best solutions to me are either to go for Neutral base curve, or a > bit like your idea, Linear 709 as the input profile, with a lot of added > saturation. So I'm quite interested by your work : ) To extract manually > the profiles seems to be a bit complicated... So I will keep reading this > thread ! > >François > > On Fri, May 4, 2018 at 9:11 PM Sarge Borsch > wrote: > >> So, I tried to edit an ICC file in a hex editor to put the values from >> that website, and, just as expected, got nonsensical results. >> >> After that I tried another idea to snatch better color profiles — I >> searched the web for Adobe Camera Raw package, extracted the profiles from >> it (they are in .dcp format), and figured that it's possible to convert >> them to ICC by dcamprof. >> They seem to work very well — better than the currently built-in input >> profiles for sony a5100 in darktable. >> Now what do you think about the copyright status of these converted ICC >> profiles? Can they legally be distributed with darktable, or should I keep >> them only for myself? >> They are a lot smaller than the source .dcc files, probably because they >> don't keep nothing valuable except the color matrices. So are 3x3 numeric >> matrices copyrightable? >> >> If you think these profiles can be officially added to darktable, I may >> fix the name tags and submit a pull request. >> >> > On 4 May 2018, at 17:14, Sarge Borsch >> wrote: >> > >> > Hi. >> > I see that there are measured color responses at >> https://www.dxomark.com/Cameras/Sony/A5100---Measurements >> > Hence the question: is it a good idea to try to take the built-in >> profile and replace the primaries with these measured values, in order to >> get closer to the in-camera JPEG color rendering? (or are they already >> used?) >> > >> > I'm asking that because I've noticed that none of the built-in input >> color profiles for sony a5100 allows me to get close to the in-camera JPEG >> colors. >> > The 2 of them which are the closest to the correct rendering (that is, >> matching camera JPEG, which is quite good when judging by eye) are the >> "standard color matrix" and "linear Rec2020 RGB". >> > Both of them wildly differ from the in-camera JPEG in deep blue colors: >> "standard color matrix" causes them to be clipped and to look really >> unnatural, and "linear Rec2020 RGB" looks more or less natural, but the hue >> is obviously different (blue gets moved to cyan). Hence I started to wonder >> how easy is it to get a better color profile. >> > >> > I know that ideally this should be done with a color chart, but I don't >> have one and don't have spare money for it at the moment. >> > >> > Also I can share a shot of the example object (Raw + JPEG) which has >> such problematic color if anyone wants to test it, too. >> >> >> ___ >> darktable developer mailing list >> to unsubscribe send a mail to darktable-dev+unsubscribe@ >> 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] Re: Improving built-in color profiles
Ah, I also get weird initial color profiles with a5100. I usually try to match the jpeg. I might try to generate a custom ICC then. I have a color checker card. I forget what is the best software to do that. > On May 5, 2018, at 2:55 AM, Sarge Borsch wrote: > > Regarding the copyrights question: > The ICC profile that I got as the result of the conversion is 536 bytes, at > least 29 of which are the ASCII name string that is equal to "Sony ILCE-5100 > Adobe Standard". > It contains only the following tags: > desc, > cprt (= "Copyright, the creator of this profile (generated by DCamProf > v1.0.5)"), > wtpt (1 XYZ tuple), > rXYZ, rXYZ, rXYZ, (the most important and probably the only part we actually > need — the color matrix), > and tone response curves which are just straight lines. > > As I see, the only thing in the final ICC profile that could possibly be > non-trivial enough to raise copyright questions is the 3x3 color matrix. > > >> On 4 May 2018, at 22:10, Sarge Borsch wrote: >> >> So, I tried to edit an ICC file in a hex editor to put the values from that >> website, and, just as expected, got nonsensical results. >> >> After that I tried another idea to snatch better color profiles — I searched >> the web for Adobe Camera Raw package, extracted the profiles from it (they >> are in .dcp format), and figured that it's possible to convert them to ICC >> by dcamprof. >> They seem to work very well — better than the currently built-in input >> profiles for sony a5100 in darktable. >> Now what do you think about the copyright status of these converted ICC >> profiles? Can they legally be distributed with darktable, or should I keep >> them only for myself? >> They are a lot smaller than the source .dcc files, probably because they >> don't keep nothing valuable except the color matrices. So are 3x3 numeric >> matrices copyrightable? >> >> If you think these profiles can be officially added to darktable, I may fix >> the name tags and submit a pull request. >> >>> On 4 May 2018, at 17:14, Sarge Borsch wrote: >>> >>> Hi. >>> I see that there are measured color responses at >>> https://www.dxomark.com/Cameras/Sony/A5100---Measurements >>> Hence the question: is it a good idea to try to take the built-in profile >>> and replace the primaries with these measured values, in order to get >>> closer to the in-camera JPEG color rendering? (or are they already used?) >>> >>> I'm asking that because I've noticed that none of the built-in input color >>> profiles for sony a5100 allows me to get close to the in-camera JPEG colors. >>> The 2 of them which are the closest to the correct rendering (that is, >>> matching camera JPEG, which is quite good when judging by eye) are the >>> "standard color matrix" and "linear Rec2020 RGB". >>> Both of them wildly differ from the in-camera JPEG in deep blue colors: >>> "standard color matrix" causes them to be clipped and to look really >>> unnatural, and "linear Rec2020 RGB" looks more or less natural, but the hue >>> is obviously different (blue gets moved to cyan). Hence I started to wonder >>> how easy is it to get a better color profile. >>> >>> I know that ideally this should be done with a color chart, but I don't >>> have one and don't have spare money for it at the moment. >>> >>> Also I can share a shot of the example object (Raw + JPEG) which has such >>> problematic color if anyone wants to test it, too. > > ___ > 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] Re: Improving built-in color profiles
Harry Durgin did a couple videos on that https://www.youtube.com/redirect?v=11nInNWJHWk&event=video_description&q=http%3A%2F%2Fweeklyedit.com%2Fcamera-profiling-darktable-chart%2F&redir_token=u1328WDSXNhekRzZLid7MbFMgGh8MTUyNzkwMDE0NkAxNTI3ODEzNzQ2 and https://www.youtube.com/redirect?redir_token=x1pQe5b4RXUCYmFePOfoRGWv5Fh8MTUyNzkwMDE4NkAxNTI3ODEzNzg2&v=LufwQZx01gk&q=http%3A%2F%2Fweeklyedit.com%2Fbasecurves%2F&event=video_description On Thu, May 31, 2018 at 6:51 PM, Robin Kramer wrote: > Ah, I also get weird initial color profiles with a5100. I usually try to > match the jpeg. I might try to generate a custom ICC then. I have a color > checker card. I forget what is the best software to do that. > > > On May 5, 2018, at 2:55 AM, Sarge Borsch > wrote: > > > > Regarding the copyrights question: > > The ICC profile that I got as the result of the conversion is 536 bytes, > at least 29 of which are the ASCII name string that is equal to "Sony > ILCE-5100 Adobe Standard". > > It contains only the following tags: > > desc, > > cprt (= "Copyright, the creator of this profile (generated by DCamProf > v1.0.5)"), > > wtpt (1 XYZ tuple), > > rXYZ, rXYZ, rXYZ, (the most important and probably the only part we > actually need — the color matrix), > > and tone response curves which are just straight lines. > > > > As I see, the only thing in the final ICC profile that could possibly be > non-trivial enough to raise copyright questions is the 3x3 color matrix. > > > > > >> On 4 May 2018, at 22:10, Sarge Borsch > wrote: > >> > >> So, I tried to edit an ICC file in a hex editor to put the values from > that website, and, just as expected, got nonsensical results. > >> > >> After that I tried another idea to snatch better color profiles — I > searched the web for Adobe Camera Raw package, extracted the profiles from > it (they are in .dcp format), and figured that it's possible to convert > them to ICC by dcamprof. > >> They seem to work very well — better than the currently built-in input > profiles for sony a5100 in darktable. > >> Now what do you think about the copyright status of these converted ICC > profiles? Can they legally be distributed with darktable, or should I keep > them only for myself? > >> They are a lot smaller than the source .dcc files, probably because > they don't keep nothing valuable except the color matrices. So are 3x3 > numeric matrices copyrightable? > >> > >> If you think these profiles can be officially added to darktable, I may > fix the name tags and submit a pull request. > >> > >>> On 4 May 2018, at 17:14, Sarge Borsch > wrote: > >>> > >>> Hi. > >>> I see that there are measured color responses at > https://www.dxomark.com/Cameras/Sony/A5100---Measurements > >>> Hence the question: is it a good idea to try to take the built-in > profile and replace the primaries with these measured values, in order to > get closer to the in-camera JPEG color rendering? (or are they already > used?) > >>> > >>> I'm asking that because I've noticed that none of the built-in input > color profiles for sony a5100 allows me to get close to the in-camera JPEG > colors. > >>> The 2 of them which are the closest to the correct rendering (that is, > matching camera JPEG, which is quite good when judging by eye) are the > "standard color matrix" and "linear Rec2020 RGB". > >>> Both of them wildly differ from the in-camera JPEG in deep blue > colors: "standard color matrix" causes them to be clipped and to look > really unnatural, and "linear Rec2020 RGB" looks more or less natural, but > the hue is obviously different (blue gets moved to cyan). Hence I started > to wonder how easy is it to get a better color profile. > >>> > >>> I know that ideally this should be done with a color chart, but I > don't have one and don't have spare money for it at the moment. > >>> > >>> Also I can share a shot of the example object (Raw + JPEG) which has > such problematic color if anyone wants to test it, too. > > > > > ___ > > darktable developer mailing list > > to unsubscribe send a mail to darktable-dev+unsubscribe@ > lists.darktable.org > > > > ___ > darktable developer mailing list > to unsubscribe send a mail to darktable-dev+unsubscribe@ > lists.darktable.org > > ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Re: Improving built-in color profiles
Sorry, the links I pasted don't appear to be good. Go to youtube and search for harry durgin. He did videos on generating icc profiles and generating basecurves to match jpegs. On Thu, May 31, 2018 at 8:43 PM, William Ferguson wrote: > Harry Durgin did a couple videos on that > > https://www.youtube.com/redirect?v=11nInNWJHWk&event= > video_description&q=http%3A%2F%2Fweeklyedit.com%2Fcamera- > profiling-darktable-chart%2F&redir_token=u1328WDSXNhekRzZLid7MbFMgGh8MT > UyNzkwMDE0NkAxNTI3ODEzNzQ2 > > and > > https://www.youtube.com/redirect?redir_token= > x1pQe5b4RXUCYmFePOfoRGWv5Fh8MTUyNzkwMDE4NkAxNTI3ODEzNzg2&v= > LufwQZx01gk&q=http%3A%2F%2Fweeklyedit.com%2Fbasecurves% > 2F&event=video_description > > > > On Thu, May 31, 2018 at 6:51 PM, Robin Kramer wrote: > >> Ah, I also get weird initial color profiles with a5100. I usually try to >> match the jpeg. I might try to generate a custom ICC then. I have a color >> checker card. I forget what is the best software to do that. >> >> > On May 5, 2018, at 2:55 AM, Sarge Borsch >> wrote: >> > >> > Regarding the copyrights question: >> > The ICC profile that I got as the result of the conversion is 536 >> bytes, at least 29 of which are the ASCII name string that is equal to >> "Sony ILCE-5100 Adobe Standard". >> > It contains only the following tags: >> > desc, >> > cprt (= "Copyright, the creator of this profile (generated by DCamProf >> v1.0.5)"), >> > wtpt (1 XYZ tuple), >> > rXYZ, rXYZ, rXYZ, (the most important and probably the only part we >> actually need — the color matrix), >> > and tone response curves which are just straight lines. >> > >> > As I see, the only thing in the final ICC profile that could possibly >> be non-trivial enough to raise copyright questions is the 3x3 color matrix. >> > >> > >> >> On 4 May 2018, at 22:10, Sarge Borsch >> wrote: >> >> >> >> So, I tried to edit an ICC file in a hex editor to put the values from >> that website, and, just as expected, got nonsensical results. >> >> >> >> After that I tried another idea to snatch better color profiles — I >> searched the web for Adobe Camera Raw package, extracted the profiles from >> it (they are in .dcp format), and figured that it's possible to convert >> them to ICC by dcamprof. >> >> They seem to work very well — better than the currently built-in input >> profiles for sony a5100 in darktable. >> >> Now what do you think about the copyright status of these converted >> ICC profiles? Can they legally be distributed with darktable, or should I >> keep them only for myself? >> >> They are a lot smaller than the source .dcc files, probably because >> they don't keep nothing valuable except the color matrices. So are 3x3 >> numeric matrices copyrightable? >> >> >> >> If you think these profiles can be officially added to darktable, I >> may fix the name tags and submit a pull request. >> >> >> >>> On 4 May 2018, at 17:14, Sarge Borsch >> wrote: >> >>> >> >>> Hi. >> >>> I see that there are measured color responses at >> https://www.dxomark.com/Cameras/Sony/A5100---Measurements >> >>> Hence the question: is it a good idea to try to take the built-in >> profile and replace the primaries with these measured values, in order to >> get closer to the in-camera JPEG color rendering? (or are they already >> used?) >> >>> >> >>> I'm asking that because I've noticed that none of the built-in input >> color profiles for sony a5100 allows me to get close to the in-camera JPEG >> colors. >> >>> The 2 of them which are the closest to the correct rendering (that >> is, matching camera JPEG, which is quite good when judging by eye) are the >> "standard color matrix" and "linear Rec2020 RGB". >> >>> Both of them wildly differ from the in-camera JPEG in deep blue >> colors: "standard color matrix" causes them to be clipped and to look >> really unnatural, and "linear Rec2020 RGB" looks more or less natural, but >> the hue is obviously different (blue gets moved to cyan). Hence I started >> to wonder how easy is it to get a better color profile. >> >>> >> >>> I know that ideally this should be done with a color chart, but I >> don't have one and don't have spare money for it at the moment. >> >>> >> >>> Also I can share a shot of the example object (Raw + JPEG) which has >> such problematic color if anyone wants to test it, too. >> > >> > >> ___ >> > darktable developer mailing list >> > to unsubscribe send a mail to darktable-dev+unsubscribe@list >> s.darktable.org >> > >> >> ___ >> darktable developer mailing list >> to unsubscribe send a mail to darktable-dev+unsubscribe@list >> s.darktable.org >> >> > ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Re: Improving built-in color profiles
On Friday, 1 June 2018 02:43:40 CEST William Ferguson wrote: > Harry Durgin did a couple videos on that > > https://www.youtube.com/redirect?v=11nInNWJHWk&event=video_description&q=htt > p%3A%2F%2Fweeklyedit.com%2Fcamera-profiling-darktable-chart%2F&redir_token=u > 1328WDSXNhekRzZLid7MbFMgGh8MTUyNzkwMDE0NkAxNTI3ODEzNzQ2 I'm sorry, but Harry his video has several mistakes :-( Better take a look at: https://pixls.us/articles/profiling-a-camera-with-darktable-chart/ -- Andreas Schneider GPG-ID: CC014E3D www.cryptomilk.orga...@cryptomilk.org ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Re: Improving built-in color profiles
Hi Andreas, Wow. Great article. Thanks, Bill On Fri, Jun 1, 2018 at 4:11 AM, Andreas Schneider wrote: > On Friday, 1 June 2018 02:43:40 CEST William Ferguson wrote: > > Harry Durgin did a couple videos on that > > > > https://www.youtube.com/redirect?v=11nInNWJHWk&event= > video_description&q=htt > > p%3A%2F%2Fweeklyedit.com%2Fcamera-profiling-darktable- > chart%2F&redir_token=u > > 1328WDSXNhekRzZLid7MbFMgGh8MTUyNzkwMDE0NkAxNTI3ODEzNzQ2 > > I'm sorry, but Harry his video has several mistakes :-( > > Better take a look at: > > https://pixls.us/articles/profiling-a-camera-with-darktable-chart/ > > > -- > Andreas Schneider GPG-ID: CC014E3D > www.cryptomilk.orga...@cryptomilk.org > > > ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Re: Improving built-in color profiles
On Thu, 2018-05-31 at 13:25 -0400, William Ferguson wrote: > In regards to the copyright question, I looked at the output of > dcamprof dcp2json and the json file has the line > > "ProfileCopyright": "Copyright 2009 Adobe Systems, Inc." > > To extract the profiles and convert them, on Linux and MacOS: > > Download the MacOS Adobe Camera Raw package > > Compile and install dcamprof and xar if they aren't on your system > > unzip CameraRaw_10_3_mac.zip > xar -x -f CameraRaw_10_3.pkg > cd CameraRawProfiles.pkg/ > mv Payload Payload.gz > gunzip Payload.gz > cpio -i < Payload > cd CameraProfiles > > At this point there are 2 directories, Adobe Standard and Camera. > Adobe Standard has the standard Adobe profile. Camera contains > subdirectories for each camera with multiple profiles. > > cd Adobe\ Standard > > dcamprof dcp2json Canon\ EOS\ 7D\ Standard.dcp 7DStandard.json > dcamprof make-icc -n "Canon EOS 7D Standard" 7DStandard.json > 7DStandard.icc > mv 7DStandard.icc ~/.config/darktable/color/in > > Substitute your camera for Canon EOS 7D. > > I converted a couple of the profiles and tried them. They didn't > make a huge difference, but then my camera is old and it's > performance fairly well known. > > Hope this helps, > > Bill > So I tested those ICCs in Rawtherapee and compared them with DCP (Rawtherapee provides this support) and result it following: my problem with color cast was in temperature. Using correct temperature in dcp2icc solved my issue. Timur. ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Re: Improving built-in color profiles
Hi, Am 31.05.2018 um 17:15 schrieb François Tissandier: The out of the box colors for those Sony cameras are not very natural. Blue colors are often looking bad on a lot of Sony cameras (Nex, A6000, A6300, A7...). I'm almost never using the Sony Alpha curve. Best solutions to me are either to go for Neutral base curve, or a bit like your idea, Linear 709 as the input profile, with a lot of added saturation. I also used the Neutral base curve in the past, which gave me much better results than the Sony alpha like base curve when developing pictures from my Alpha 6300. Quite some time ago, however, I created a custom base curve, which gives me even more pleasing results. See https://github.com/rabauke/darktable-styles https://www.darktable.org/2013/10/about-basecurves/ Heiko -- -- Number Crunch Blog @ https://www.numbercrunch.de -- Cluster Computing @ https://www.clustercomputing.de -- Social Networking @ https://www.researchgate.net/profile/Heiko_Bauke ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
