Showing related tags and posts accross the entire site.
-
Close but not quite - Using the Avid AAF method from ClipBrowser you get two specific output for each clip - the first is a set of OP Atom MXF files that Avid can read natively, the second in an AAF file that contains no essence, only the metadata. You need to set the OPAtom folder to be one of Avid's...
-
I have over 600 clips that have been logged (name and description changed) by an assistant in the XDCAM clip browser. However, when I imported them into the avid, the orriginal name was restored and the "comments" column doesn´t have anything. Is the option to change the name in browser...
-
Hi, I have MC3.0 on Windows. I haven't figured everything out yet. But as I understand it, I should be exporting AAFs in Clip Browser 2, then importing those AAFs in MC3.0 (which point to MXF files placed in your AVID Media Files folders), then transcoding the XDCAM video files to DNxHD145 (virually...
-
At the end of any xdcam ex project, to obtain a master in native mp4, clip browser could rewrap the MXF OPAtom from MC back to mp4. Exactly the other way around clip browser does to creaye MXF OPAtom from mp4.
-
I'm trying to figure out how to export my project back from media composer 3 natively in mp4. Cilp browser will create the BPAV structure to save it and play it with the camera, if needed, the down conversion as well.
-
David, you have really milked (and cookied) my analogy to a sweet death. Thank you for your response. Some new insights: - - the AAF imported clips are no longer orphaned. They seemed to have become adopted after I did a transcoding which is a bizarre way for a problem to be solved. - the TC that was...
-
Hello This is my understanding of the workflow. Correct me if I am wrong. Pretend that the EX camera is a cookie making machine throwing their product into a box (mp4). Exporting the cookies to MXF puts them into a generic paper bag. Importing them into Avid puts them into a Avid plastic bag with a label...
Page 1 of 1 (7 items)