Not aware of a channel naming spec for openexr. Afaik an openexr channel
doesn't have to have a layer/chan split in its name - but Nuke does. Nuke's
not so much trying to 'fix it' for you more than it's attempting to fit the
openexr channel name into it's layer/channel scheme.
Nuke doesn't
Does nuke really have a bad name handling bug if the layer names aren't
written to the
exr spec? Seems like it would be a lot better to make the fixes
upstream than wait/have nuke do a fix that could end up creating other
issues. I'd be curious how other viewers read your layer?
I have to
DJV sees all the layers correctly in that file. I haven't tried other
viewers.
R
On Sat, Oct 22, 2011 at 12:43 PM, John RA Benson
john.benson.macg...@gmail.com wrote:
**
Does nuke really have a bad name handling bug if the layer names aren't
written to the exr spec? Seems like it would be a
Thanks. Will do.
R
On Thu, Oct 20, 2011 at 3:44 PM, Jonathan Egstad jegs...@earthlink.netwrote:
The exrReader is not doing the correct name munging when converting the
file's channel name into the Nuke channel name.
The vray channel is likely missing a separator in it's name ('.') that the
I've noticed that our renderId and UV passes from maya vray 2.0 come in to
nuke as a channel named other.
The UV layer is missing, but it's channels end up as separate channels in
other.
We haven't had this issue before mainly because we weren't using
multichannel files. Is there a naming
