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: Todays FCP X announcement

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


Paul DickinRe: Todays FCP X announcement
by on Feb 1, 2012 at 11:03:34 pm

[Aindreas Gallagher] "...in straightforward terms the transformative importance of the database..."
Hi
My most straightforward 'need' is for different captures (tape) or transfers (card) of the same material - A/V + timecode + Reel Name - to be seen by the NLE as linkable with no issues, regardless of clip in/outs etc. So for example if a whole tape had been captured overall, then fragmentary clip sections subsequently recaptured would work in the edited project without any relink fiddling and fooling around.

A label based spreadsheet like FCP Legacy couldn't do this as it can't see beyond the original capture/ingest labeling of the video. All that Shift-F matchback malarky if you've brought clips into the browser from another project.

A proper database would see clips from identical assets as being the same thing even if brought to the project by different ingest methods.

That's where my puck has been - awaiting an NLE to catch up with it... ;-)



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]