Success! Now Check Your Email

To complete Subscribe, click the confirmation link in your inbox. If it doesn’t arrive within 3 minutes, check your spam folder.

Ok, Thanks
ENDA Episode 166→ The time when ENDA tells a little secret called: Cloning (Part 2) 1 min read
Posts

ENDA Episode 166→ The time when ENDA tells a little secret called: Cloning (Part 2)

But if those FrameHold nodes are cloned, all it takes is changing one of them, and the entire comp updates instantly, ready to test the new version.

By Gonzalo Castaneda
ENDA Episode 166→ The time when ENDA tells a little secret called: Cloning (Part 2) Post image

In a previous episode, I mentioned that I had an example to showcase just how useful cloning can be when working on a shot.

And here it is the proof!

In the video below, you can see the current breakdown we’re working with. It uses a specific hero frame to establish the exact moment where the wipes need to happen.

Now, if we put ourselves in the client’s shoes, what would we ask for?

A version that showcases a different hero, of course.

A tedious request?

Yes. Normally, we would have to adjust every single FrameHold node individually just to test whether our wipes still read well with the new frame.

But if those FrameHold nodes are cloned, all it takes is changing one of them, and the entire comp updates instantly, ready to test the new version.

If cloning can streamline something as simple as a breakdown driven by a FrameHold node, just imagine what becomes possible when you apply the same logic to colour nodes or transform nodes.

But that will be a story for another episode.

So, stay tuned!

The journey continues...

0:00
/1:11

Comments