Creative COW SIGN IN :: SPONSORS :: ADVERTISING :: ABOUT US :: CONTACT US :: FAQ
Creative COW's LinkedIn GroupCreative COW's Facebook PageCreative COW on TwitterCreative COW's Google+ PageCreative COW on YouTube
APPLE FINAL CUT PRO:HomeFCP ForumFCP XFCPX TechniquesFCP TutorialsFC ServerBasics ForumPodcastFAQ

Re: Might Be An Interesting Read

COW Forums : Apple FCPX or Not: The Debate

VIEW ALL   •   ADD A NEW POST   •   PRINT
Share on Facebook
Respond to this post   •   Return to posts index   •   Read entire thread


Chris HarlanRe: Might Be An Interesting Read
by on Nov 15, 2011 at 9:01:22 am

Bill, what you describe as robust wouldn't even have been considered so back in 1998. "Robust" would be the ability to re-write or reassign TC for any source material, monitor and match timecode across tracks or synced items, monitor and match timecode at different frame rates. I should be able to, using time code, replace a temp source with a master with matching code in any given timeline. I should be able to monitor in and outs of any given clip or a whole group of clips at the same time. I should have sync markers that demonstrate the number of frames paired or locked items are out of sync, and in what direction. I should have indicators that show sync or lack-there-of across all layers/tracks/or what-you-will. I should be able to generate an EDL, and of course, I should be able to read one and attach material to it. That's robust.

I agree with you that FCP X has more timecode support that a hobbyist might need, but to call it robust is absurd.


Posts IndexRead Thread
Reply   Like  
Share on Facebook


Current Message Thread:




LOGIN TO REPLY



FORUMSTUTORIALSFEATURESVIDEOSPODCASTSEVENTSSERVICESNEWSLETTERNEWSBLOGS

Creative COW LinkedIn Group Creative COW Facebook Page Creative COW on Twitter
© 2014 CreativeCOW.net All rights are reserved. - Privacy Policy

[Top]