Unable To Link Transcoded Alexa Footage in Media Composer

[Michael Phillips]

Thanks for the files. Here is what I found:

1. MXF file plays fine
2. AAF imports and directly links to MXF file as expected
3. ALE will not merge because it is not correctly structured. As you can see in the frame grab that compares both the MXF/AAF and the ALE file, the reference to the source is incorrect. The AAF shows it in the TAPE column which is what the Avid AMT does, but the source name is the name of the AAF file and not the original ProRes file. The ALE file is incorrect as Source File is used for files referenced under AMA and there is no value in TAPE which is needed in order to merge. There needs to be a match – either Source File to Source File or Tape to Tape.

Someone from 3cP needs to get a hold of someone at Avid, or hire me (;)). I consult with manufacturers on these types of issues.

Michael

Michael Phillips

[Andrew Thompson]

Wow – you’re very good at this.

For the short term im trudging along using the media tool. When i get my head above water Im going to attempt the AAF option again.

I will absolutely pass your name along to 3Cp people.

Thanks again Michael!

[Michael Phillips]

Glad to help. And 3cP should remember me… 😉 Haven’t spoken to then in a while though.

Michael

Michael Phillips

[Michael Phillips]

You should also be aware that the files as they are being created now can never have an EDL generated from them that would make sense to any system out there. If you look at the frame grab I did, the metadata in the Tape field shows as:
B030C002_120819_R1XC_3cP_DNxHD_MXF
and not
B030C002_120819_R1XC

So either some text editing in the EDL or some expression work for source relink will need to be done. They really need to change that ASAP. In the meantime, you might want to hilight the NAME column, so a command-D or contrl-D and select Labroll or Camroll from the pop-up dialog box. This way you can generate an EDL on the proper filename.

Michael

Michael Phillips

[Andrew Thompson]

The reason I was not able to import AAF’s was because our DIT had the media buried in a series of folders of which some contained forward slashes. Once I replaced those with periods the AAF’s imported fine and linked with the media.

Regarding EDL, I made one from a sequence comprised of footage we received before and after our new workflow and sent it off to the facility that will be handeling our DI. I can’t wait to hear what they say!

[Andrew Thompson]

The reason I was not able to import AAF’s was because our DIT had the media buried in a series of folders of which some contained forward slashes. Once I replaced those with periods the AAF’s imported fine and linked with the media.

Regarding the EDL, I made one last night and sent it off to the facility that will be handeling our DI. I can’t wait to hear what they say!

[Michael Phillips]

Which EDL template did you use? You would need to use the File_32 to get the entire string in the EDL as currently define in the Tape column.

Michael

[Andrew Thompson]

CMX 3600.

[Michael Phillips]

Well that will only grab the first 8 characters from the Tape field which would take:

B030C002_120819_R1XC_3cP_DNxHD_MXF

and make it

B030C002

Which may or may not work assuming its the only file with that start to the filename. Usually the 8 character representation of a ProRes file as done by the camera and listed as REEL in the QuickTime header would be:

B030R1XC

It will be interesting to see what you hear back.

Michael

[Andrew Thompson]

Indeed.

Im operating off a spec sheet they gave us. We did a conform test a few weeks ago when we did our camera test and everything linked up without any issues. I’ll keep you posted.

Thanks for the tip about the 32 character file name.