EXR - Renaming individual Channels, not layers

Hello Flamingos,

I have a project with an unusual request, that I 100% understand the reasoning behind but flagged concerns about downstream issues (which we are experiencing but that is another story). They want to rename individual channels within a RGB layer. This is for mattes.

So instead of having the usual naming convention where each channel takes the name of the layer followed by a .. As an example:
Layer: matte01
R: matte01.red (which for the purposes of this explantion would contain BG matte)
G: matte01.green ((which for the purposes of this explantion would contain FG matte)
B: matte01.blue ((which for the purposes of this explantion would contain sky matte)

Instead they want to name it this way where every channel has a different name
Layer:matte01
R: matte01.bg (so no “.red” in the channel name)
G: matte01.fg (no “.green” in the channel name)
B: matte01.sky (no “.blue” in the channel name)

We can do this in Nuke but are getting crosstalk (mattes from one channel affecting another in weird ways). I don’t think this is even possible in Flame. You can change the layer name but not individual channels I believe.

Does anyone have a suggested fix? I could potentially create some kind of renaming python script to run after the exr sequence is rendered but does anyone have a smart way of doing this within Flame? It is so unconventional that I doubt there is a way. I am not about to make a feature request fr it as this is the only time I have been asked to deliver this way.

@Slabrie @fredwarren Is this something that can be done within Flame?

Hello @AdamArcher It is sadly not possible to name individual channels withing the application. I guess you could write a post export script using the OpenEXR SDK tools. You will have to recreate a new set of EXR files since it is not possible to edit in place metadata.

Please add this request to Flame-Feedback and share the improvement ID here.

Thanks for your response @Slabrie

I’m not actually going to submit a feature request for this yet. It is the first time I have ever been asked for this and we have come across some cross channel contamination that we can’t explain in Nuke.

There are many, many fantastic feature requests on here that I would much prefer you spend your valuable time on.