-
Steve Kanter: What FCPX CAN Do
-
“Apple made a huge design decision with FCPX, and legacy compatibility is one of the things they were willing to trade for it.”
And the fact is this is not unique to FCPX. Adobe, among others, did the same thing when going from Premiere to Premiere Pro, The difference being that Adobe was upgrading from a consumer app to a pro app, whereas Apple …
Herb Sevush
Zebra Productions -
Craig –
I like Motion, use it all the time. But it has had NO impact on the field of compositing. My statement was about “software of any importance”, as in creating software that influenced the field, was a category leader, etc. After Effects is such a program, and it wasn’t invented by Apple. I’m just questioning this vision of Apple as being the company to create the future of the NLE – they’ve have no track record that makes me believe they can do it.
Now track record isn’t everything, but then again software design isn’t hardware design, which, along with marketing, IS Apple’s field of excellence.
Herb Sevush
Zebra Productions -
[David Roth Weiss] “I am not a computer programmer, nor do I play one on TV, but I’ll go out on a limb and will suggest that eventually somebody, probably not Apple, will make an application or plugin or utility that will enable users to import legacy projects into FCP X. I’ll bet ya $1 if you’d care to make a wager?”
I won’t take the bet, because this is one of the things I’d really like to be wrong about.
What little Apple has said about interchange has been focused on OMF and XML export. On import, all they’ve said is that “there is no way to ‘translate’ or bring in old projects without changing or losing data.”
If Apple allows developers access to some sort of import hooks, they will be at the mercy of the importer’s interpretation of a legacy edit. If the importer guesses wrong, the FCPX timeline will not work correctly in some edits. If the FCPX timeline isn’t working correctly, it will reflect poorly on FCPX and on Apple.
On second thought, they don’t seem to mind FCPX reflecting poorly on them, so perhaps we will see import after all.
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 -
Liam, please let us know when you may by chance be stuck again at an airport, so that we can shower ourselves in your honey-dripped condescension. Just the thought that you might once again patronize a forum such as this, instead of sending your flunkies or assistants, adds a delicate beauty to my day that I cannot quite define. I knew that there had to be some reason to be grateful for flight delays.
Again, thank you.
-
After Effects was not invented by Adobe. It was invented by CoSA.
-
[Chris Harlan] “Liam, please let us know when you may by chance be stuck again at an airport, so that we can shower ourselves in your honey-dripped condescension. Just the thought that you might once again patronize a forum such as this, instead of sending your flunkies or assistants, adds a delicate beauty to my day that I cannot quite define. I knew that there had to be some reason to be grateful for flight delays.
Again, thank you.”
Fair point Chris, that did read badly!
Kind regards,
Liam
Liam Hall
Director/DoP/Editor
http://www.liamhall.net -
Ah! Well, more the gentleman for acknowledging it!
I’m waiting on client notes right now. That’s my excuse.
-
[Walter Soyka] “I won’t take the bet, because this is one of the things I’d really like to be wrong about.”
Completely understandable. I seldom bet against my heart no matter how good a bet seems. Winning isn’t everything…
[Walter Soyka] “What little Apple has said about interchange has been focused on OMF and XML export. On import, all they’ve said is that “there is no way to ‘translate’ or bring in old projects without changing or losing data.””
That’s the easy way out for them. Had Steve Jobs told Randy Ubillos from the outset that his job depended on the necessary code that would open legacy projects, we’d all be better off now. There are only two outcomes, and I’m not sure if either of them wouldn’t be a vast improvement.
[Walter Soyka] “If Apple allows developers access to some sort of import hooks, they will be at the mercy of the importer’s interpretation of a legacy edit. If the importer guesses wrong, the FCPX timeline will not work correctly in some edits. If the FCPX timeline isn’t working correctly, it will reflect poorly on FCPX and on Apple.”
Color 1.0 was not very good at round-tripping, and ver. 1.5 still doesn’t do a perfect job, but that hasn’t ruined Apple or kept most of us “pros” from performing our appointed duties.
David Roth Weiss
Director/Editor/Colorist
David Weiss Productions, Inc.
Los Angeles
https://www.drwfilms.comDon’t miss my new tutorial: Prepare for a seamless transition to FCP X and OS X Lion
https://library.creativecow.net/weiss_roth_david/FCP-10-MAC-Lion/1POST-PRODUCTION WITHOUT THE USUAL INSANITY ™
Creative COW contributing editor and a forum host of the Business & Marketing and Apple Final Cut Pro forums.
-
[Chris Harlan] “I’m waiting on client notes right now.”
So I have this image of Chris walking in to the edit room in a waiter’s uniform and asking the clients what they’d like for lunch as he jots the orders down on his pad.
It shows how language can be interpreted as it sits exposed to the elements in a forum post.
-
Really? May I suggest that you need to develop your interpretive skills just a bit?
Reply to this Discussion! Login or Sign Up