Can anyone describe what the parent/child relationship in V5 does? Note that I am not a previous version user so don't go referencing "well, it's like v4 but..."
I've played with it and it doesn't make sense how it works, infact, I can't really figure out what it does at all. Logically, I would THINK that children composite up into their parents before the parents are composited into something else. For example, if I have 3 track A, B, C:
A: Vid1
B: Vid2
C: Vid3
I would expect, with no PC relationship, that C would be layed down first, then B composited on top of that obscuring portions of it, then A composited on top of the result, with A as the highest track being the most dominant. If B were a child of A, then I would EXPECT that C is layed down, but then B is composited with A, and the combined AB is then composited on top of C.
It doesn't seem to be that way. Perhaps it does something useful that I just am missing? Can someone explain this?
-Jayson
I've played with it and it doesn't make sense how it works, infact, I can't really figure out what it does at all. Logically, I would THINK that children composite up into their parents before the parents are composited into something else. For example, if I have 3 track A, B, C:
A: Vid1
B: Vid2
C: Vid3
I would expect, with no PC relationship, that C would be layed down first, then B composited on top of that obscuring portions of it, then A composited on top of the result, with A as the highest track being the most dominant. If B were a child of A, then I would EXPECT that C is layed down, but then B is composited with A, and the combined AB is then composited on top of C.
It doesn't seem to be that way. Perhaps it does something useful that I just am missing? Can someone explain this?
-Jayson