QT File or QT Reference File. Lossless?

[Chris Borjis]

[John Heagy] “[Chris Borjis] “Reference exports can
cause you major pain later.”

Only if one doesn’t understand them.

It’s a powerful tool that can speed exports and save space.

It sounds like the ref movie worked. A self contained will be no better.

John”

That’s exactly what I’m talking about. I’ve had other editors
bring in files they’ve exported as reference and they decided
to delete or not copy the sources to their backup, thus having a useless
non working reference file. Then it delays an already tight deadline
and if media was deleted you’re sol. No thank you.

This has happened a number of times in past years.

That = pain in my world.
The mandated policy at our facility is not to use them as an extra precaution.

For this instance it’s fine and worked. Just re-iterating why it’s not the best
idea for those that “don’t understand.”

[John Heagy]

[Walter Soyka] “I drive a manual, but I like to ironically refer to it as a “standard.””

Nice!

[Walter Soyka] “I rely on tools from a broader ecosystem, I find not just reference movies, but QuickTime as a whole to be quite a bit less appealing.”

Understood, and I’d be all for a ProRes.mxf as there is a mxf ref.mov equivalent (MXF OP1b) that I would embrace. I don’t know of any apps that support MXF OP1b.

From speaking to developers at NAB is seems Apple is making clear which QT API calls are going away, indicating to me that the entire API is not going away. Of all the processes that would suffer from calling a 32 bit QT API the creation of a 64k QT ref.mov would not be one of them. Hint… Hint.. Adobe!

John