I think I’ve seen somewhere someone importing cr2 canon files in nuke, with nuke using dcraw as a background to interpret the files that are read in. Hello, I’ve currently scratching my head about what would be the best approach to bring camera raw files into ACEScg workflow without losing to much of it’s quality or doing to much conversion from one software to another. It’s annoying that Nuke still doesn’t include the same DNG integer to float transform. I think as long as the metadata tags are as written when the image was saved to disk, then the result is consistent with Resolve, OIIOTool or rawToACES in DNG mode. The output matches the Resolve DNG ACES IDT, which does the same conversion from integer to linear floating point. When using OIIOTool for raw development, it has a flag that automatically adjusts to scene linear - though based on an assumption, so check that it’s working okay for you. ![]() Which doesn’t surprise me since they’re all using LibRaw on the back end. I would like to start using rawToACES again, but the way it generated an IDT from DNG metadata (before the bug that makes them all really blue) is the same result as I get from OIIOTool and Resolve. Then apply that to all the images saved out of DCRaw. Then adjust the exposure in Nuke so the grey card is. I’m of the opinion that DCRaw to ACES can work well if you shoot a grey card and set the flag to output the image with ACES primaries. I could use dcraw to get to linear tiff but then what ? We primarily use stills for hdri on set ref and for textures and reference, internally I have us using ocio and ACES 1.2 config for all projects. Saying that having done more research going to 16bit linear tiff seems to have disadvantages and is not ideal for hdri either? so my options are very limited How do I find this 3x3 IDT you all mention, how and where should I apply it?Īs already I explained raw2aces is out as it needs building and we don’t have resources my team tried but having issues with dependencies on our distro.ĭcraw is also pretty old on our distro so can’t go straight to ACES. I do understand that going to display referred is not best but having tried dcraw to linear it didn’t look great and this way got us overall better results for our texture use. Thanks for the inputs but a lot of this is over my head that your on about with spectral sensitivities. An “IDT Matrix” is included automatically with your raw file.From that known gamut you can get to any target gamut you want. An IDT is simply a 3x3 matrix which converts raw colors to some known target gamut. ![]() You might look at rawtoaces and get scared you need to have spectral sensitivity data for your camera sensor in order to convert your image into AP0. You might get scared of all this talk of IDTs. Regardless of what your desired target gamut is, this is pretty straightforward. you mentioned ACES but I am not sure if you are referring to ACES the “color encoding system” or ACES the gamut (AP0). Secondly you must decide what gamut you wish to debayer your image into. ![]() DNG or CR2 or NEF, the result will be the same black-box display-referred result. Otherwise all bets are off.Īs far as I am aware, it is 2022 and Adobe products still do not support debayering camera raw to a scene-linear output image. Linearįirst and most importantly, you must debayer your raw image to a linear encoding, so that you preserve a proportional relationship between pixel data intensity and scene light intensity. It seems like there is some confusion in this thread around what is necessary to convert camera raw images into scene-linear aces exr images.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |