Turnover Plates Standard Conventions

I was wondering whether there might already be standard conventions people use for what I need to do with raw live action footage; i.e. to save me going down a rabbit hole and ending up doing things in a far too custom way.

I have a load of MXF files on disk for the live action raw footage.

I’ve written some standalone python code which can be given: MXF path, start/end timecode, shot name, other parts of the name, and it writes out an EXR sequence to path which matches the ayon folder structure and naming convention I’ve set up so far; under the appropriate shot folder.

Eventually this will all be a lot more automated - coming from EDLs from editorial etc.

Also, would likely eventually make sense it’s performed by jobs on the render farm.

I know I could use the ayon python api to trigger the creation of shots and the publishing of the EXRs etc. (though I haven’t embarked upon the details yet).

It just occurred to me that there might already be more out-of-the-box standard ways of doing some parts of it.

tl;dr: is AYON often used for projects with lots of live action footage, and what approach is usually taken?

You don’t have actually to extract shots and eventually publish them via batch publisher. Editorial workflow should address this need.

AYON Tray publisher have Editorial Advanced and Editorial Simple both can parse your file and chop it into clips and publish each on to a dedicated task on AYON. I believe it should also create project hierarchy. I’m not sure if they support MXF but I know they support EDL.


Alternatively, you can use Hiero-Resolve-Flame for editorial publishes.
AYON Resolve addon works with free resolve.