AYON shot handle workflow

General
,
1

Hi,

I need to understand how to deal with shot handles when working on VFX shots.

Scenario: we need to replace the face of an actor on a shot by a 3D rendered skull. for that we will do tracking in 3DEqualizer.

  1. Our IN/OUT department receive the .mov raw plate from the client
  2. We export it to an EXR sequence
  3. That EXR sequence has frame handles (10-10 before start and after end)
  4. In Kitsu we create the shot and fill the In and Nb Frames values to the “real” shot duration without handles (for example 1001-1401)
  5. The shot get’s sync in AYON and has handles 10-10 (setup in the project setting globally)
  6. We publish the plate .exr files using the Publisher. We choose all the EXR images including the handles so (1401-1001 = 400 + 20 = 420 files)

Now let’s suppose an artist did the tracking in 3DE and published the track. In a Maya matchmove scene the person will import it’s camera and create some geo for the Matchmove scene.

The issue is that the created Maya scene uses the frame range of the real sequence without handles (like 1001-1401) but we need to work with the handles too (991-1411). What is the correct way to do this?

I thought that the AYON Set frame range button in Maya would set the scene frame range to (frame_start - handle_start) / (frame_end + handle_end)?

This is linked to: Publishing plates with Handle and start/end frame

2

Maya: Include handles of current context in the scene

Use the setting here: ayon+settings://maya/include_handles/include_handles_default

image

And say you have a few task types for which you purposefully want to exclude handles regardless, you can use the list below it. For example:

image
image896×302 13.4 KB

Maya: Created instances default frame range to match current context

You may also want to enable this: ayon+settings://maya/create/use_entity_attributes_as_defaults

image
image774×143 14.5 KB

Due to legacy reasons creating an instance via the Creator has the frame range of the instance default to the current scene timeline and not to the current task entity you’re working on.

By enabling this - newly created instances that have frame ranges should default to the current context.

1 Like