Creative COW SIGN IN :: SPONSORS :: ADVERTISING :: ABOUT US :: CONTACT US
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 ForumTrainingPodcastFAQ

Re: 'send to motion' in fxp x

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


Walter SoykaRe: 'send to motion' in fxp x
by on Feb 15, 2012 at 5:40:04 am

[Jeremy Garchow] "So while it is certainly a function of Quicktime, the instructions that the component carries out are probably via some sort of language. In that link you sent, it said it gave him a flattened file, which means that the component is running a translation, it isn't simply saying motion is a codec."

I think the Motion component was a frame server [link]. When the requesting application (be it FCP7, QuickTime Player, or in that example, AE) asks for the next frame of video from a .MOTN file, the Motion QT component directs the Motion engine to render that frame and then passes it back to the application as if it were any other piece of traditional media.

In other words, from FCP's or AE's perspective, it is very much like a codec (decoded by the QuickTime framework). From the component's perspective, and from the Motion renderer's perspective, yes, it's Motion's internal format, not pre-rendered video.

The brilliance of the old system was abstracting all that away from other apps, so they never had to know that they were using a Motion project; it just felt like a regular piece of media, just like any other .MOV file. By engineering the system well, integration came for free.


[Jeremy Garchow] "And then going FROM FCPX to Motion is different again, as things need to be timed and layered and sorted which seems to indicate some sort of language that's being used. I don't know, it's speculation on my part, but QT components aren't available in FCPX as there's no QT API like there used to be."

I'd buy that.

Here's some wild, baseless, utterly uninformed speculation of my own: maybe Apple initially developed XMEML for their own internal use for round-tripping with Motion/STP, before it took on a life of its own as general interchange.

All our speculation aside, though, I think Jim's right to call Apple out for this. It's not like the ProApps team found out that XMEML and QuickTime integration wouldn't work last June. Even if it's only temporary, this workflow gap is a step backward.

Walter Soyka
Principal & Designer at Keen Live
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
RenderBreak Blog - What I'm thinking when my workstation's thinking
Creative Cow Forum Host: Live & Stage Events


Posts IndexRead Thread
Reply   Like  
Share on Facebook


Current Message Thread:




LOGIN TO REPLY



FORUMSTUTORIALSMAGAZINESTOCKYARDVIDEOSPODCASTSEVENTSSERVICESNEWSLETTERNEWSBLOGS

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

[Top]