Support Op-Atom MXF files with Correct Timecode
Premiere pro is already able to load DNxHD Op-Atom MXF files, but it links audio to video for each instance of the file. For example; FILEA01, FILEA02, FILEA03, FILEA04, and FILE_V01 will all load into the project browser, and each will include 1 video track and 4 audio tracks. Honestly, we don't mind that, as it's helpful to have everything connect while editing.
The issue is that at the moment Premiere cannot read the correct timecode from Op-Atom MXF files. Perhaps there is some inherent difference in how Op-Atom and Op-1a files are created, but for whatever reason all Op-Atom MXF files come in with timecode that starts at 00:00:00:00.
If you use an avid .aaf file to import, Premiere recognizes that there should be different timecode in the video track, and says that the video track is missing.
Furthermore, the file will display non-drop frame timecode, even if the original clip is supposed to use drop-frame timecode.
The original timecodes were verified using a trial media composer software as well as Davinci Resolve. Only Premiere has an issue with the timecode.
Why is this feature important to you?
We deal with a big client who creates files from a Cinedeck MX 4.51:
MXF File details:
Wrapper type: MXF-OP Atom (type: N Tracks 1 SourceClip)
File generated by: Cinedeck, Cinedeck MX (4.51.13340)
Compression ID: DNxHD 1080i SQ 8-bit
Effective Video Bitrate: 145 Mbps
It's extremely important that we're able to use timecode that correctly matches the original files that are stored offsite and are also used in avid systems at another post house.
Obviously Premiere can cut the files fine; the only major issue is that the timecode does not come in correctly. We would be extremely grateful if Premiere could do this!