![]() ![]() The Import process took significant time, because (as I later confirmed) it was doing a transcode (to DNxHD 120) rather than a re-wrap. So I tried the next-best (RightClick) option, namely. I tried Bin: but the option was greyed-out. Regardless, I wasn’t impressed by Avid’s programmer-level “cryptic” error messages. One can only guess at which company is at fault here, but one poster blames Adobe. I had previously succeeded in exporting AAF from Avid to Adobe.Ī forum post says Adobe can read Avid but not vice-versa – confirming my (limited) experience. However, not only were they not linked, but Avid’s Relink function failed to recognize them. I had naively assumed that the Media objects would have been AMA-linked to the source footage, which by the way included DNxHD recorded by BlackMagic Cinema Camera. Result: Bin created, containing what appeared to be (from brief glance) all relevant Media and Sequence objects (now in Avid’s representation), but the Media objects were offline/unlinked and various “cryptic” popup error messages appeared from Avid. Given a simple 3-minute dramatic scene with footage from BMCC (as DNxHD 185 of HD 1920×1080 at 25fps) and a Windows-7 system:įrom Adobe Premiere CC (latest version) I exported AAF.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |