Avid > Monkey Extract > AutoDesk Inferno workflow not working :(

[Scott Dominick]

We're trying to go from Avid to Monkey Extract to Inferno and we're having issues relinking a CMX3600 EDL to DPX files in Inferno. We initially wanted to export an Red 16 EDL for use in Monkey Extract but ME can't find the r3d files even though they are there and it crashes right after. Upon exporting a CMX3600 EDL from Avid we can get ME to see the EDL and export proper DPX files. Now we're getting a snag when we try and import both the DPX files and the EDL and then subsequently relinking them in Inferno. The only workflows that pertain to Inferno are based on XML and Final Cut Pro. Should we be using Film Scribe to export XML that would work in Inferno?

SOS!@!
~Scotty D

[MichaelP]

XML is just not XML and just works. It only wraps existing metadata into an easy to parse language. Inferno would need to use the XSD (dictionary) for the FilmScribe XML in order to conform from that. It is easy enough for them to do as the XSD files are available on www.avid.com/filmscribe for them or anyone to code against for both the assemble and pull list versions of the XML. Change list versions coming soon.

The bigger issue for now is getting Inferno to link the EDL to the generated DPX files. There are a couple of issues that you can look into - does Inferno use the full 16 characters in the EDL or does it expect no more than 8 characters as per the CMX3600 specification? Does it use the source ID in the DPX header or can it re-index based on file name? Does it use the directory as a source ID if not the file name? Once you know what it expects for doing a conform, you can generate from Monkey the proper files and directory structure.

Michael

[Scott Dominick]

Michael,

Did you mean "XML is just XML and just works"? So basically we need to take that html template from the Avid website and import the library into Inferno? That's what it seems you're implying to do. Or is this something for AutoDesks software engineers to deal with?

I'm thinking the inferno is looking for the full 16 characters. The CMX3600 is only giving 8 characters. This is probably why things aren't linking. However, as I stated before Monkey Extract wouldn't even deal with the Red16 EDL (which is just a CMX3600 modified to handle 16 characters) We had to use a CMX3600 for Monkey Extract to do anything.

So the million dollar question is if we reexport a Red 16 EDL and bring that into Inferno directly from Avid and then use the DPX files generated by ME will they properly link up?

All this is very hacked together and I haven't found a solid solution yet. Hopefully, all parties can create something that is a little more robust and less time consuming.

~Scotty D

[MichaelP]

No, XML is just XML and does not just work - I as taking it from the other point of view. Autodesk engineers need to enable the parsing of the Avid XML to make it work.

The latest Monkey does have a menu selection to select Avid 16 character template so that should not be an issue. Are you using the latest version?

With that said, it should work if it supports the 16 character EDL.

The most robust would be for Autodesk to support the AAF format which would have the metadata needed from the sequence as well as the source R3D file names in whatever format they want to use.

Michael

[simonpeterarnold]

Always make sure that you project is the set up the same as the resolution you are importing in as that can cause problems relinking EDL to image sequences. We have had the issue a few times.