Same as source export – MXF

[Shane Ross]

It’s my understanding that a “same as source” QT export is an export to a Quicktime File that has the same codec as the source. But there are many file types that, while are MXF, cannot be exported “same as source.” Most often you need to transcode the sequence to DNxHD, and then export same as source. And it won’t be MXF…because in the EXPORT window you are choosing SEND TO QT…that’s when you get the interface where you can choose SAME AS SOURCE

Shane
Little Frog Post
Read my blog, Little Frog in High Def

[Pat Horridge]

Same As Source just means don’t transcode. The Wrapper has no real impact. So H264 in QT to H264 in MXF is transparent in quality. SAS should be quicker as well.
The only impact changing the wrapper has is the wrappers ability or not to carry metadata and if thats passed across.
That’s effectively what the old log and transfer resolved in legacy FCP. QT has poor metadata support so the metadata was transfered to the clip info when a file was rewrapped to QT.

Pat Horridge
Technical Director, Trainer, Avid Certified Instructor
VET
Production Editing Digital Media Design DVD
T +44 (0)20 7505 4701 | F +44 (0)20 7505 4800 | E pat@vet.co.uk |
http://www.vet.co.uk | Lux Building 2-4 Hoxton Square London N1 6US

[Neil Forsyth]

Make sure you what you are trying to link to in resolve is a supported format.

https://images.blackmagicdesign.com/media/5407521/DaVinci_Resolve_9.1_Supported_Codec_List.pdf

Is it a PIX 240? these save as:

Apple ProRes 4444, 330 Mb/s, 12-bit
Apple ProRes 36, 100, 145, 220 Mb/s, 8 and 10-bit
Avid DNxHD 36, 145, 220 and 220x
Quicktime wrapper (.MOV), UDF File System

When I ingest rushes I tend to AMA all media and then comp sequences and transcode everything a DNx MXF which gives me a files I can link to via AAF import in resolve.

Hope this helps.