![]() And you would know if this would be required / desired for your use case. And you don’t select it as output profile unless you want your output file to be in adobergb. Of this is the case, comparing in other apps would go wrong anyway since they don’t know the input is adobergb and would interpret it wrong. You don’t use it as an input profile, unless you know the input file is adobergb but it has NO adobergb profile embedded. You also don’t select it as working profile, be a use Darktable usually uses linear rec2020 as working profile which is fine. The moment you profile/calibrate your monitor, you select that monitor profile, not Adobe RGB or something. The only use case would be if your monitor has an adobergb mode you are using, and you have NO monitor profile selected on system settings. Otherwise I will go far into some wilderness.Īlso note that i can’t imagine you have to select adobergb anywhere in monitor profiles or soft proof profiles. ![]() I don’t focus on everyone always, but in this case I need to be clear about the situation and analyze anything and everything. it wasn’t raised, which means everything is fine here. the topic would have been raised by the community. NOT soft proof profile, not input profile, not output profile, not working profile. I guess this would mean you would have to select the monitor profile somewhere in Darktable. Now, if a program advertises itself to macos as being color managed, it gets more choices and can draw in bigger gamuts than sRGB for instance, but it has to do a lot by itself suddenly. What i learned from using a 2017 Macbook pro, is that of a program is not pretending to be color managed, macos interprets it as being sRGB, so macos will take whatever the program is drawing, and interprets it as sRGB and makes sure it looks ok on the profile in the OS display settings. Darktable’s color management is done with a library internal to Darktable (lcms2, not using macos libraries AFAIK) so it should work the same as any other build using lcms2. Of that input - output check is being done correctly and is NOT ok, it looks like therenis a bug with the build you are using. If you google the question, it has been poorly raised, and the program (mac os port) is many years old. Otherwise the topic would have been raised not only by me. Most likely, darktable is friendly with cms mac os. If you have a monitor calibration profile and have it set in macos settings, you should not set it anywhere in Darktable is my guess (but I’m not 100%) on this. Note that i completely ignore how the file looks inside of Darktable. They should be similar (gamut limits and such not accounted for right now ). Export it, compare it to the input tiff in a color managed program (like Photoshop ). In the export, save it as a jpg, set it to sRGB output and relative mode. Make sure all Darktable modules are disabled that can be disabled. Open a tiff file, that has an ICC profile embedded in it (and for giggles, make sure it is not a CMYK profile ). So just to get started, you should not touch any setting (and for sure not set anything to adobergb, because that has no place except for an output profile ). What i know from macos, is that the os is doing the color management for apps, unless an app really requests 'i know what i am doing, let me draw my own pixels '. The output is only used if you want your files to be in a certain profile, but generally this should be sRGB.Īll the soft proof settings should also be left at default to get started. Make sure you do NOT touch input profile module (leave the working profile to linear rec2020). Src.tiff+darktable.app != output.tiff+preview.app Src.tiff+preview.app != src.tiff+darktable.app Src.tiff+preview.app = output.tiff+preview.app And so yes - if I open the source in preview.app and the exported file from darktable, which used to be the source, I also open in preview.app, then the source and the resulting file will not be different. I will see the difference already at this step. What will the original image look like in darktable and in another program that supports cms. If you have issues with your monitor profile, the preview would look different / weird / wrong.īut loading a tiff file and not doing anything to it and saving it again in sRGB should look (almost) like the input.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |