Adding a slate to a comp

[andymilkis]

There is a post render python hook that can trigger a script. Mine works on the iterate hook, so the slate updates when you iterate.

[milanesa]

Cool! Is it the post-render one from the Logik Portal?

[andymilkis]

I haven’t seen that, but it’s likely using the same hooks. There are samples in the example python scripts in the opt/Autodesk/flame folder.

[paul_round]

@andymilkis

Let me know what time works and I’ll show you.

Hi Andy, I’m in work today until around 6pm BST

[andymilkis]

Hi Paul,

Sorry that I missed this. Let’s try again on Monday. I’ll buzz you in the morning.

[WayneS]

@AdamArcher

…arter way of doing it in batch rather than opening a timeline and adding a smart slate to the front of it. Is there some cool Python script for that?I had thought about if I used a write node instead of a render node for my comps then have a user setup that I drag with smart burn-in data that writes a single frame at frame 1000 to its own write node every time (since comps will start at frame 1001).

I’m a little late to the conversation, but here’s the way I’m doing it. Basically setting up a slate at frame 0 and using a comp node to to “edit” from the slate at 0 to the first frame of the comp 1 and setting to render form frame 0 in the render list.

[AdamArcher]

Do you have a way to automatically set duration of the render to add a frame duration and back tone the start of the comp by 1?

[WayneS]

In my template I have a custom range set in the Render List that starts at 0 but I do have to manually set the out frame number, 117 in this case. That’s one of the only things I have to set manually. The slate picks up the name, version and length from the render settings using the Burn-In Metadata node and a T from the Render Node…