Z Depth AOV is black in After effects
Moderators: ChrisHekman, aoktar
-
henningricke
- Posts: 40
- Joined: Wed Feb 22, 2017 1:08 pm
I just wanted to note, that this issue still exists in 2022.1.1(R3)
DWAB compression still messes up the Z-Depth. At least when rendered as single layer files. It turns out black.
However, in multilayered EXR it produces a Z-Depth.a in red channel and Z-Depth.y in green channel. This type of output is new to me. Can anyone elaborate on this?
Is there no way to get a normal black and white Z-Depth channel when rendering out single file EXRs in DWAB compression?
I personally very much prefer using single files over clunky multylayered ones that tend to have a lot of useless extra data in them.
DWAB compression still messes up the Z-Depth. At least when rendered as single layer files. It turns out black.
However, in multilayered EXR it produces a Z-Depth.a in red channel and Z-Depth.y in green channel. This type of output is new to me. Can anyone elaborate on this?
Is there no way to get a normal black and white Z-Depth channel when rendering out single file EXRs in DWAB compression?
I personally very much prefer using single files over clunky multylayered ones that tend to have a lot of useless extra data in them.
-
henningricke
- Posts: 40
- Joined: Wed Feb 22, 2017 1:08 pm
Damn! I get it now!
Extracor needs to be used even when it is only a single layer file. I assumed this workflow only applies to multy layered files.
Sorry for the inconvenience!
Extracor needs to be used even when it is only a single layer file. I assumed this workflow only applies to multy layered files.
Sorry for the inconvenience!
-
SilentPartnersStudio
- Posts: 12
- Joined: Mon Feb 15, 2016 4:38 pm
viewtopic.php?f=85&t=80351&p=416748#p416748
The problem is rather dumb, and can be seen as an AE issue, or a Octane issue, and both companies would probably bounce the ball back and forth.
So the issue is that Octane write the data channels with "Lowercase" letters, and AE expects "Uppercase" letters.
Most other compositing apps and views don't care about the case, but AE does.
Octane writes the channel with the correct case in all exports except DWAA / DWAB
I brought this up a year ago and it was completely ignored even though I clearly outlined the issue
The problem is rather dumb, and can be seen as an AE issue, or a Octane issue, and both companies would probably bounce the ball back and forth.
So the issue is that Octane write the data channels with "Lowercase" letters, and AE expects "Uppercase" letters.
Most other compositing apps and views don't care about the case, but AE does.
Octane writes the channel with the correct case in all exports except DWAA / DWAB
I brought this up a year ago and it was completely ignored even though I clearly outlined the issue