[Bill Davis] “But there’s a case to be made that in the modern metadata world, Traditional timecode is a less critical and, more important, DIMINISHINGLY USEFUL – tool.
“
No argument here… I’d just argue HOW diminishing. Depending on the size scale and scope of your project, I’d argue that TC can either be a minor issue or a dead in the water deal breaker.
Bill, In your rush to move forward into your brave new database/keyword world, you’re dismissing an effective time honored (pun intended) tool that serves a useful purpose for multiple workflows, genres, and editorial styles. If Apple was in agreement with you, they probably would have eliminated TC reading from the program. They didn’t.
I’m well past the realization that FCP-X was NOT optimized for me and the kinds of workflows that I rely upon. No hard feelings. It’s business. Just please stop preaching that we just don’t “Get it”. I DO GET IT! It’s NOT for me and my specific needs. That doesn’t belittle you or anyone else. It just means that it’s NOT right for a certain kind of workflow that I require.
Now let’s get back to arguing about total cost of ownership, shall we?