Heya Folks,
Here's a bit of a dumb one for you. i've got a render setup where I have two different zdepth elements set to different values (even though it's float - comper has a setup he likes from a previous render of a less "deep" scene) and I was finding that when I converted from exr, it was dropping one of the elements. I was curious as to why nuke was reading the channel as depth and also not "VrayZdepth" as it was originally named. The lovely Thorsten had a look at it and using the -info part of vrmig2exr found that both channels were tagged with the same thing which might have written the second over the first. This is probably a totally stupid request since you can just use float to get any range but just as an fyi.
Cheers,
John
Here's a bit of a dumb one for you. i've got a render setup where I have two different zdepth elements set to different values (even though it's float - comper has a setup he likes from a previous render of a less "deep" scene) and I was finding that when I converted from exr, it was dropping one of the elements. I was curious as to why nuke was reading the channel as depth and also not "VrayZdepth" as it was originally named. The lovely Thorsten had a look at it and using the -info part of vrmig2exr found that both channels were tagged with the same thing which might have written the second over the first. This is probably a totally stupid request since you can just use float to get any range but just as an fyi.
Cheers,
John
Comment