State:New|TargetRelease:No Target|icon_bug|icon_katana|database:public|Resolution:Fixed|BugID:375230|
Problem summary
When several EXR render outputs are merged using the ExrCombine utility (i.e. by rendering a render output of type "merge"), unexpected names may be constructed for the channels in the resulting output image. This applies specifically to EXR files rendered using RenderMan.
When merging EXR images, ExrCombine constructs the names of individual channels as "passName.channelName", with pass name being specified in the ExrCombine command, e.g.:
ExrCombine <exrfile 1> <passname 1> ... <exrfile n> <passname n> <outputfile> Customer reported version
Katana 3.1v1
Customer reported platform
Linux
Steps to reproduce
Expected behaviour
Both EXR files contain the same channels with the same names.
Actual behaviour
The second EXR file contains a channel called 'P_P' instead of 'P'.
Workaround
As a workaround, you can perform the merge via a 'script' output, using either ExrCombine and "primary" pass names, or if you have access to RenderMan the exrmerge tool shipped with RenderMan to combine raw EXR images.
Reproduced by support
Katana 5.0v3 - CentOS 7
Katana 5.0v1 - CentOS 7
Katana 4.5v3 - CentOS 7
Katana 4.5v1 - CentOS 7
Katana 4.0v8 - CentOS 7
Katana 4.0v1 - CentOS 7
Katana 3.6v1 - CentOS 7
Katana 3.5v1 - CentOS 7
Katana 3.1v1 - Windows 10 - CentOS 7
Katana 3.0v6 - Windows 10
Katana 2.6v4 - Windows 10
Katana 2.5v7 - Windows 10
Katana 2.0v1 - CentOS 7
Earliest version tested
Katana 2.0v1 - This issue appears to be in all versions of the product
Could not find a working RfK version to test with 1.6v3
We're sorry to hear that
Please tell us why