Remind me again, why EDL and not AAF

[Henrik Cednert]

Hello

It have totally slipped my mind. Why don't we export AAF from offline Avid when going into online? Is there something that doesn't work in the AAF's that work with the RED16 edl template?

 

[MichaelP]

It all depends on the receiving system's ability to mine the metadata as needed from the AAF.

Michael

 

[Henrik Cednert]

Aaaah! Cool. Then it's time to take the eQ for an AAF-ride. WE have some issues with the good ol 999 events with the EDL's.

Thanks Michael.

It all depends on the receiving system's ability to mine the metadata as needed from the AAF.

Michael

 

[MichaelP]

Nothing like using a pseudo standard from 10 years ago from a company that is no longer in existence!

Michael

 

[Henrik Cednert]

Hahahaha! So true. But AAF was a dead end in the eQ. I guess that all metadata that's in the Avid ends up in the AAF, right? So if the filenames are in the camroll column, that metadata is in the AAF? Right?

If it is in the AAF I should be able to convince Quantel to get us access to that "column".

 

[MichaelP]

Exactly... there is also an XML export from Avid FilmScibe to which the dictionary is published at www.avid.com/filmscribe.

Michael

 

[James Rayburn]

We use AAFs for going to Discreet Smoke. We have to follow steps provided by Discreet for XML / DPX conform, but it works great.

 

[Henrik Cednert]

We use AAFs for going to Discreet Smoke. We have to follow steps provided by Discreet for XML / DPX conform, but it works great.

Are those steps available somewhere. Can only find Autodesks FCP/RED Whitepaper.

 

[James Rayburn]

I think that is the same steps we use. We use this whitepaper:

http://images.autodesk.com/adsk/files/red_autodesk_whitepaper1.pdf

We use the steps on page 6, entitled "Finishing with Smoke or Flame". Anywhere where it says XML we instead use our Avid AAF, and it works the same.

Not sure if it matters, but we use the RedCine XSLT method to create our Avid ALE. And we generate our DPX files from RedCine.

But it works great. I do remember having to follow the whitepaper exactly. Any small changes and we were not able to conform. (ie: make sure your smoke project is set to 10 bit if your DPX files are 10 bit)