Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

MXF file replace - Proxy for Finish file help

KevinStanley

Active member
Joined
Jan 12, 2009
Messages
33
Reaction score
0
Points
0
Location
Huntington Beach, CA
Website
www.kevinstanley.com
I have project that I delivered to client in quarter debayer low res DNX HD for offline that I rendered quickly so client could start cutting. While he's cutting I'm rendering all the same material to DNX175 10bit 1080 full debayer. I noticed that redcine x makes new names for the MXF media and I'm wondering if I will have any issues when I give him the full res replacement files. Can you replace the proxy files with the full res 175 files (new versions of AAF, MXF, ALE, based on same original R3D media) and have the edit auto conform to the new finish files?

The files are the same names, folder structure is the same, the AAF files match by name, but the MXF files appear to be different, RCX is creating different names for them?

Any help here would be greatly appreciated.
 
I have project that I delivered to client in quarter debayer low res DNX HD for offline that I rendered quickly so client could start cutting. While he's cutting I'm rendering all the same material to DNX175 10bit 1080 full debayer. I noticed that redcine x makes new names for the MXF media and I'm wondering if I will have any issues when I give him the full res replacement files. Can you replace the proxy files with the full res 175 files (new versions of AAF, MXF, ALE, based on same original R3D media) and have the edit auto conform to the new finish files?

The files are the same names, folder structure is the same, the AAF files match by name, but the MXF files appear to be different, RCX is creating different names for them?

Any help here would be greatly appreciated.

Avid doesn't relink to the filename. Instead it uses metadata inside the MXF files to establish a connection between a clip in the application and a media file on the drive.

For example, if you transcode to a different resolution in Avid you get new MXFs in the same folder with different names. Your client can just put the new files in the Avid MediaFiles folder and relink the sequence (or master clips) to the new DNxHD 175x media. In this case there's not really any need for the ALE or AAF.
 
Last edited:
Tape Name (aka file name) and timecode is what is used. A relink to KeyKode is also available, but not valid for this purpose.

Michael
 
Back
Top