[John Heagy]

As long as SD (analog or digital) simulcasts are derived from HD, 29.97 will be necessary. One can’t broadcast SD in 30.00fps.

[John Heagy]

[Bill Davis] “ask yourself what they’re ACTUALLY doing for you”

It can be boiled down to UUID vs Reel. UUID is what a computer needs “Reel” is what people need.

To answer what it does for us specifically. Reel, along with TC, identify content while UUID identify files. How is this different. If I have a 1hr interview and I select a sound bite and save it off preserving reel and TC. A UUID based system see these two as completely different as they will have different UUIDs, that’s the universal part of UUID. If I look at reel and TC I can easily determine that the1hr interview contains the select and they have content in common. This enables advanced workflows like linking to small files that used to be a large file. This is necessary when doing partial file restore. It can also link disparate media, as mentioned before, like linking video and audio from different recordings.

[Bill Davis] “After all, a card is NOT a reel.”

And a file is not a piece of celluloid hanging in a bin but everyone still calls them “clips” including Apple.

John

[John Heagy]

[Oliver Peters] “I don’t think there’s any conspiracy here. Merely unfinished software.”

I certainly hope you’re right. I have high hopes reading embedded “reel/tape” ID in .mov files will be in the next version. I spoke directly to Apple multiple times on this request and, given it’s utter ease of implementation, seeing it missing in the next version would really dash my hopes that Apple is still interested in the Pro customer.

John

[John Heagy]

Grain and today’s compressed distribution don’t work well together. Take a look at AMC’s the Walking Dead which is shot in 16mm film. I’ve seen many shots where close ups have visible posteration due to the compressor’s bandwidth being gobbled up reproducing the grain.

Tread carefully with grain and compression. That aspect of “the film look” is hopefully fading away… literally.

John

[John Heagy]

Thanks Ruben,

Looking at cvmkfile it appears it makes a file with data. Would it be possible to use cvmkfile and then have QT render a .mov into it?

Thanks
John

[John Heagy]

If people appreciate inventive workflows like this enabled by Quicktime reference movies, please ask Apple to add reference movie creation in AVFoundation. The lack of ref mov support in AVFoundation is why FCPX can’t export one.

If anyone wants to send feedback I suggest using the “Provide Final Cut Pro Feedback..” under the “Final Cut Pro” menu in FCPX and the Apple Feedback site, both OS X and Quicktime.

https://www.apple.com/feedback/quicktime.html

https://www.apple.com/feedback/macosx.html

Thanks
John

[John Heagy]

Joseph is correct. 1:00:00:00 in NDF equals 1:00:03:18 in DF

[John Heagy]

[Jeremy Garchow] “What I hope this points to, is an AVFoundation universe free of QuickTime.”

So QuickTime would be the “dark matter” of the Universe 😉

[John Heagy]

[Jeremy Garchow] “I’m talking about the engine not so much the QT player. “

So am I. Windows without the Quicktime APIs is something I’m not ready for.

[John Heagy]

[Jeremy Garchow] “What I hope this points to, is an AVFoundation universe free of QuickTime.”

Are you ready for a Quicktime free Windows? I don’t see Apple ever doing AVFoundation for Windows.

As long as Macs and Windows can run 32bit apps Quicktime will be around. When the time comes the OS can no longer run 32bit natively, there will be a 32bit “rosetta”