So, since Corona works internally with WideRGB, and shows to you by sRGB, is this workflow accurate?:
OPTION A, MAKING TONEMAPPING OUT OF VBF
1- Save the image of VFB in EXR 32bits float without any tonemapping.
2- Open the EXR in Photoshop asignin wideRGB color space and using proof colors in sRGB to visualize it while we are editing the image. (we asign wideRGb because is the raw of corona understandign that corona works with wideRGB, and because photoshop have more colors to prevent banding or clamping while editing). Convert to 16bit compressing highlight and making tone mapping.
3- Convert to sRGB (in perceptual or colorimetric mode, te same choosen at proofcolors ) and if we are not happy with the conversion, go back and edit saturation in the areas that gamut warning of proof colors are pointing, to prevent unwanted changes with the conversion. (That is difficult to happen because we have been watching proofcolors in sRGB during the edition and we were already liking how it looked)
4- Save the image in a JPG file with embed sRGB profile.
5-Send it to client.
OPTION B MAKING TONEMAPPING IN VFB
1- Save the image of VFB in PNG 16bits with tonemapping.
2- Open PNG16 on Photoshop to Matte painting. Assign wideRGB profile but seeing with proofcolors in sRGB. (is corona saving wideRGB when select PNG16?)
3- Convert to sRGB (in perceptual or colorimetric mode, the same choosen at proofcolors)
4- Save it to JPG with embed sRGB profile.
5- Send to client
Thanks!
