[Eric Tramp]

same here – mountain lion 10.8.2.
avid codecs le 2.3.4 acts like it is installing , then FAIL

[Eric Tramp]

First of all, thank you for answering my questions – you know far more than me, and I appreciate your insight…..I can’t figure it out.
you state:
“The AAF from resolve can’t have audio unless it was brought in with it.”
The prores444 logc files brought into resolve DO have audio embedded(recorded as a scratch track line in to camera). I also tried importing and syncing the BWF 2nd system .wav files from the sound mixer in Resolve(which synced by matching timecode just fine). In Resolve, I import Prores444logC and .wav files into media pool, then in conform room I sync .wav to Prores, in deliver room render DNxHD36 with render audio. 3 mxf are rendered /file(1 video, 2 audio).
I then save project, go back to conform room, then file/save AAF. When imported into avid, this aaf doesn’t link to the 2 audio mxf’s that are definitely siiting next to the video mxf in the avid mediafiles/mxf/001 folder.
You write:
“Another choice is to copy your rendered clips into a unique directory in you Avid Media_Files folder… and let it scan, then drag the mdb file into a fresh bin. And you have a bin with all your audio/video media. Then make an aaf as desired.”
This is what I’ve been doing on set to check that proxies work in avid. Unfortunately, the ass’t editors
first dealing with the proxies aren’t used to importing by dragging .mdb into bins, so when they use the Resolve generated .aaf and no sound plays, they send email to production claiming screwed up transcodes, etc. I guess I will import the .mdb files into avid, then generate an .aaf in avid to send with the Resolve rendered .mxf proxies.
I just wish I could figure out how to make the .aaf from Resolve import properly into Avid.

Thank You again for your advice

[Eric Tramp]

No, I don’t want to export an ALE.
Editorial specs for deliverables are the ProRes 444 LogC files, and MXF wrapped DNxHD36 with an .aaf file, to use as offline proxies in Avid Media Composer. The transcodes from Resolve definitely have a video mxf an audio1 mxf and an audio2 mxf for each file. The audio plays fine in Avid if I populate the bin by dragging the .mdb file that avid generates. The problem is that ass’t editors are used to importing files by importing an .aaf file, and the .aaf that Resolve is generating in the compose room (file/export AAF,XML….) doesn’t link the audio mxf’s to the video.
As I understand it, an MXF file contains all the metadata of a file along with the data, while an .aaf is more complete – documenting the CHANGES made to a file, input .aaf to output .aaf (color grades, effects, edits).
When I’ve used Colorfront ExpressDailies to make DNxHD dailies, an .aaf file was generated into the folder automatically – not so with Resolve.
Online doc’s describe roundtrips from avid to resolve to avid (export .aaf from avid, import .aaf to resolve, do grade, export updated .aaf from resolve, import updated .aaf back into avid). But since I’m starting IN resolve, the files don’t have an input .aaf. And if I generate an .aaf from mastertimeline of files (in resolve), then import THAT .aaf into resolve(trying to emulate a roundtrip), render onelites, save an updated .aaf, the updated .aaf STILL won’t link audio when imported into avid.
How can I generate an .aaf of a file that tracks the changes made from Prores444LogC to Rec709DNxHD
that will import properly, sound and all, into avid?