Comments on: What is Apple doing with Final Cut Pro?

By: Philip

Philip — Tue, 16 Mar 2010 16:50:42 +0000

QuickTime has both pluses and minuses compared with other formats. As a developer we’re not seeing the timecode rounding errors and one of our core products (and an unreleased one) are 100% TC based. But gamma has been a problem, so you’ll know if you stay within the proapps family of products you won’t experience gamma shifts anymore. That problem has been fixed to the degree the ProApps Team can. Remember that’s the only code the Pro Apps team actually control. Sadly they don’t control the QT team.

philip

By: John T.

John T. — Tue, 16 Mar 2010 15:38:09 +0000

One thing to really look at is how to solve the fundamental fiasco that is Quicktime. I do a lot of work with QT as well as other formats, and never do I have to spend more time fixing problems than with QT – gamma shifts, timecode rounding errors… please Apple, it’s been long enough, fix these problems.

By: Philip

Philip — Mon, 15 Mar 2010 22:50:48 +0000

If only that were universal John, if only. A film now in production in 2010 was planning to use digital betacam SD for dailies, losing all reference to original media (video and audio). Until I pointed it out, no thought had been put into determining who and how matchback would have been managed. They ultimately decided on digital dailies so metadata could be tracked via Media Composer.

Philip

By: Philip

Philip — Mon, 15 Mar 2010 22:49:05 +0000

The Adobe Mercury engine is indeed awesome… *if* you have one of the four supported graphics cards (just one on OS X). I also doubt that real-time performance is the only criteria for choosing an NLE.

Philip

By: John Miller

John Miller — Mon, 15 Mar 2010 22:39:50 +0000

I agree re the metadata, however any 2nd assistant/ production assist/continuity person should always note this info anyway, and the editor gets a hard copy as backup.

By: mpheadley

mpheadley — Mon, 15 Mar 2010 22:29:41 +0000

FCP editors should really watch the demo videos of in development Premiere CS5 in combination with the NVidia cards. Good luck FCP!

By: Philip

Philip — Thu, 11 Mar 2010 17:24:14 +0000

I just submitted an article for the 4th Supermeet Magazine – out at NAB in April – that deals with exactly that Dustin. How we can use and acquire that metadata and make post easier.

Philip

By: Valerian Bennett

Valerian Bennett — Thu, 11 Mar 2010 15:10:06 +0000

I’m just hoping they fix the underlying inefficiencies with the project file format. Those file sizes can grow to be absurd.

By: Dustin Lau

Dustin Lau — Thu, 11 Mar 2010 08:44:42 +0000

The most useful application I can think of off the top of my head that currently does not already exist in NLEs for the extended metadata would be location, camera movement, face recognition, and transcribed audio once the requisite sensors (GPS/Accelerometer/face recognition engine/voice recognition) are integrated either in the camera hardware or at the ingest phase on the computer.

There is so much logging time to be saved from never having to type in location, camera movement, name of person in shot ever again.

By: Tony Williams

Tony Williams — Tue, 09 Mar 2010 06:14:04 +0000

Phillip,

You might also want to think about which parts of Final Cut Pro might benefit from the speed increases 64 bit would bring.

(Not being a major user of FCP I can’t offer an opinion.)

// Tony