Change Details

**System Information** elementaryOS 0.4.1, GTX1080 **Blender Version** Broken: 2.79.6, 7ff1750 **Short description of error** When generating proxies from Blender's Clip Editor while using a different Color Management View profile other than Default, that color profile is not taken into account, making the proxies look different than the actual movie in the Clip Editor. **Exact steps for others to reproduce the error** The whole issue came up when trying to work with footage shot with the Arri Alexa. The footage is a ProRes file, encode with Arri Wide Gamut in LogC. I am currently working with @sobotka on making that work inside Blender. The way we do that currently is as follows: By using Blackmagic Fusion I convert the ProRes to a Linear EXR, but not rec709, instead it's Linear Arri Wide Gamut, in order to keep the data of that colorspace intact. Loading this in Blender looks wrong of course, since Blender assumes an EXR file to be Linear Rec709. In order to work around that, @sobotka thankfully created a new OpenColorIO config file, that uses the AWG colorspace when setting the view to Filmic. Using that new config.ocio the Footage looks correct in the Clip Editor. Obviously I need the Background Images in the 3D Viewport to look the same, since I want to integrate 3D elements into the footage. However, when I generate the Proxies, they seem to use the Default Rec709 View Transform. See this screenshot: {F4594896} The colors in MCE at the bottom are correct, but wrong in the 3d View above. I can understand that the 3D View cannot do realtime color conversions in order to maintain a decent playback. However, that's why I think the proxies need to take CM into account, including gamma and exposure. For anyone who wants to try it, I have attached a folder with one frame from that footage, the proxy, the blendfile, as well as a the adjusted colormanagement folder with the new config.ocio from @sobotka. (I left out the film responce curves). {F4595165}

**System Information** elementaryOS 0.4.1, GTX1080 **Blender Version** Broken: 2.79.6, 7ff1750 **Short description of error** When generating proxies from Blender's Clip Editor while using a different Color Management View profile other than Default, that color profile is not taken into account, making the proxies look different than the actual movie in the Clip Editor. **Exact steps for others to reproduce the error** The whole issue came up when trying to work with footage shot with the Arri Alexa. The footage is a ProRes file, encode with Arri Wide Gamut in LogC. I am currently working with @sobotka on making that work inside Blender. The way we do that currently is as follows: By using Blackmagic Fusion I convert the ProRes to a Linear EXR, but not rec709, instead it's Linear Arri Wide Gamut, in order to keep the data of that colorspace intact. Loading this in Blender looks wrong of course, since Blender assumes an EXR file to be Linear Rec709. In order to work around that, @sobotka thankfully created a new OpenColorIO config file, that uses the AWG colorspace when setting the view to Filmic. Using that new config.ocio the Footage looks correct in the Clip Editor. Obviously I need the Background Images in the 3D Viewport to look the same, since I want to integrate 3D elements into the footage. However, when I generate the Proxies, they seem to use the Default Rec709 View Transform. See this screenshot: {F4594896} The colors in MCE at the bottom are correct, but wrong in the 3d View above. I can understand that the 3D View cannot do realtime color conversions in order to maintain a decent playback. However, that's why I think the proxies need to take CM into account, including gamma and exposure. For anyone who wants to try it, I have attached a folder with one frame from that footage, the proxy, the blendfile, as well as a the adjusted colormanagement folder with the new config.ocio. (I left out the film responce curves). {F4595165}

**System Information** elementaryOS 0.4.1, GTX1080 **Blender Version** Broken: 2.79.6, 7ff1750 **Short description of error** When generating proxies from Blender's Clip Editor while using a different Color Management View profile other than Default, that color profile is not taken into account, making the proxies look different than the actual movie in the Clip Editor. **Exact steps for others to reproduce the error** The whole issue came up when trying to work with footage shot with the Arri Alexa. The footage is a ProRes file, encode with Arri Wide Gamut in LogC. I am currently working with @sobotka on making that work inside Blender. The way we do that currently is as follows: By using Blackmagic Fusion I convert the ProRes to a Linear EXR, but not rec709, instead it's Linear Arri Wide Gamut, in order to keep the data of that colorspace intact. Loading this in Blender looks wrong of course, since Blender assumes an EXR file to be Linear Rec709. In order to work around that, @sobotka thankfully created a new OpenColorIO config file, that uses the AWG colorspace when setting the view to Filmic. Using that new config.ocio the Footage looks correct in the Clip Editor. Obviously I need the Background Images in the 3D Viewport to look the same, since I want to integrate 3D elements into the footage. However, when I generate the Proxies, they seem to use the Default Rec709 View Transform. See this screenshot: {F4594896} The colors in MCE at the bottom are correct, but wrong in the 3d View above. I can understand that the 3D View cannot do realtime color conversions in order to maintain a decent playback. However, that's why I think the proxies need to take CM into account, including gamma and exposure. For anyone who wants to try it, I have attached a folder with one frame from that footage, the proxy, the blendfile, as well as a the adjusted colormanagement folder with the new config.ocio from @sobotka. (I left out the film responce curves). {F4595165}