Change Details

**System Information** Operating system: Windows-10-10.0.17134 64 Bits Graphics card: Intel(R) HD Graphics 4000 Intel 4.0.0 - Build 10.18.10.5069 **Blender Version** Broken: version: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: `rBf6cb5f54494e` (also tried on the latest 2.81 Beta) Worked: (optional) **Short description of error** I don't think it's a bug, but rather something that hasn't been thought of. Currently when you use Cryptomatte and export an OpenEXR Multilayer file, if you then import it into the compositor and change its color space to something other than linear, the cryptomatte passes will also be affected by the color space change and will no longer work properly. Cryptomatte color picking with linear color space : {F7649100} Cryptomatte color picking with linearACES color space : {F7649101} Here is an example .blend with an EXR Multilayer file packed into it : {F7652089} **Exact steps for others to reproduce the error** Use any blender scene, enable cryptomatte, and render a 1 frame animation in OpenEXR Multilayer. Import the file in the compositor, connect it to a cryptomatte node. Change the color space of the file to linearACES for example. Then try color picking the cryptomatte passe. It will behave very weirdly, sometimes you will not be able to select an object, or the edges of the matte will not be antialiased etc. Sorry for being so vague about the exact steps to follow to reproduce the bug but it is quite simple to recreate.

**System Information** Operating system: Windows-10-10.0.17134 64 Bits Graphics card: Intel(R) HD Graphics 4000 Intel 4.0.0 - Build 10.18.10.5069 **Blender Version** Broken: version: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: `rBf6cb5f54494e` (also tried on the latest 2.81 Beta) Worked: (optional) **Short description of error** I don't think it's a bug, but rather something that hasn't been thought of. Currently when you use Cryptomatte and export an OpenEXR Multilayer file, if you then import it into the compositor and change its color space to something other than linear, the cryptomatte passes will also be affected by the color space change and will no longer work properly. Cryptomatte color picking with linear color space : {F7649100} Cryptomatte color picking with linearACES color space : {F7649101} Here is an example .blend with an EXR Multilayer file packed into it : {F7652089} **Exact steps for others to reproduce the error** Download the example file. First set the image in linear color space. With the cryptomatte node, pick the color of the chair for example as in this image : {F7656425} Then show the generated mask of the cryptomatte node : {F7656427} In linear color space, everything works as expected, the cryptomatte node masks only the chairs. Then, set the image color space in linearACES for example. (you'll notice that the color picking output of the cryptomatte node isn't displayed the same way as in linear color space) Delete the values in the cryptomatte node. Pick the color of the chairs like the first time. {F7656432} Then show the generated mask of the cryptomatte node : {F7656435} The mask does not only include the chairs as expected but also other objects, and the edges of the mask are too sharp compared to the same mask in linear color space.

**System Information** Operating system: Windows-10-10.0.17134 64 Bits Graphics card: Intel(R) HD Graphics 4000 Intel 4.0.0 - Build 10.18.10.5069 **Blender Version** Broken: version: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: `rBf6cb5f54494e` (also tried on the latest 2.81 Beta) Worked: (optional) **Short description of error** I don't think it's a bug, but rather something that hasn't been thought of. Currently when you use Cryptomatte and export an OpenEXR Multilayer file, if you then import it into the compositor and change its color space to something other than linear, the cryptomatte passes will also be affected by the color space change and will no longer work properly. Cryptomatte color picking with linear color space : {F7649100} Cryptomatte color picking with linearACES color space : {F7649101} Here is an example .blend with an EXR Multilayer file packed into it : {F7652089} **Exact steps for others to reproduce the error** Use any blender scene, enable cryptomatte, and render a 1 frame animation in OpenEXR MultilayerDownload the example file. Import the file inFirst set the compositor, connect it to a cryptomatte nodeimage in linear color space. Change the color space of the file toWith the cryptomatte node, pick the color of the chair for example as in this image : {F7656425} Then show the generated mask of the cryptomatte node : {F7656427} In linear color space, everything works as expected, the cryptomatte node masks only the chairs. Then, set the image color space in linearACES for example. Then try(you'll notice that the color picking output of the cryptomatte passe.e node isn't displayed the same way as in linear color space) It will behave very weirdly, sometimes you will not be able to select an object, or the edges of the matte will not be antialiased etc.Delete the values in the cryptomatte node. Pick the color of the chairs like the first time. {F7656432} Then show the generated mask of the cryptomatte node : {F7656435} Sorry for being so vague about the exact steps to follow to reproduce the bug but it is quite simple to recreatThe mask does not only include the chairs as expected but also other objects, and the edges of the mask are too sharp compared to the same mask in linear color space.