-
DaVinci Resolve 8.1 — now with FCPXML roundtrip support
-
[Jeremy Garchow] “In the words of a wise man, “Now what, haters?” :-D”
Sorry, But I have MOVED ON
Sohrab
FCS 3, AJA Kona Lhi & Adobe PPro
“The creative person wants to be a know-it-all. He wants to know about all kinds of things: ancient history, nineteenth-century mathematics, current manufacturing techniques, flower arranging, and hog futures. Because he never knows when these ideas might come together to form a new idea. It may happen six minutes later or six months, or six years down the road. But he has faith that it will happen.” — Carl Ally
-
[Jeremy Garchow] “Uh. Wasn’t this the point? Apple gives the hooks, VideoCompany#1 takes it over from there?”
If FCPX could output either EDL or FCP7’s flavor of XML, it would have been interoperable at launch. Apple put the burden of interchange on the rest of the industry instead of assuming any themselves. It strikes me as a statement about their priorities.
But that doesn’t change the fact that this is a big development in the ongoing saga. Tune in next week to see if Autodesk follows suit with Smoke…
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 -
[Jeremy Garchow] “Now what, haters!?”
LOL! FCPX is AWESOME! *
* For everything but actual editing :p
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl -
[Walter Soyka] “If FCPX could output either EDL or FCP7’s flavor of XML, it would have been interoperable at launch. Apple put the burden of interchange on the rest of the industry instead of assuming any themselves. It strikes me as a statement about their priorities.”
From another post, here’s how I feel about 3rd parties, complete with repeat:
“Here is my thoughts on third party development.
I think this is really smart. The video business is becoming very fragmented. This can lead to specialization (“we only shoot, Red, man”) or it can lead to generalization (“I have SD, 720p, 1080i, 23.98, 59.94, 29.97i, , 29.97p, 5k, 4k, Alexa, Beta, DV, Digibeta, 7000fps, MPEG4, MPEG2, AVI, wmv all going in one timeline. Help me”). Camera manufacturers are developing their asses off right now. There is some really healthy competition out there. Film, is truly dying. This means that every manufacturer is going to have their way of doing things. By creating a proprietary digital system, this means you need to support a proprietary method of handling that media. So, with all the variety out there, would you rather have a specialized system or a generalized system? What if you could create a specialized system depending on your needs? What if you could turn the specialized system in to a more general system ? This is how I see third party support working in FCPX. FCPX will provide the underlying language and method, then people would be able to hook in to this to interact and interchange. When Red’s 28k sensor comes out, we won’t have to wait for Apple/Avid/Adobe to develop a method, Red will have to support it in FCPX. They have the hooks, go to town. Support yourself.
Now apply this to OMF, AAF, XYZ, CBS, NBC, ABC, PBS and Discovery. If you need specialization, you purchase it and interact with that developer who will listen and respond to you directly. I do not see this as a bad thing. Apple broke their own stuff, (Qt/itunes Updates causing FCP craziness) so owning the whole system didn’t prevent them for making mistakes. Things break sometimes. Apple has a pretty decent developer relationship going. They have leveraged that relationship to everyone’s advantage. Why can’t this happen with FCPX and why is it a bad idea? Sure it’s a new idea, but is it a bad one? Look at Lightworks. Open source. Is that a bad idea?”
Jeremy
-
[David Lawrence] “LOL! FCPX is AWESOME! *
“i knew you’d come round eventually 🙂
“My Name is Steve and I’m an FCPX user”
-
[Walter Soyka] “Apple put the burden of interchange on the rest of the industry “
That’s almost what XML is all about!
It’s not a file format – it’s an eXstensible Markup Language.
A readable, well documented description of a fcpx project.
It cannot have the same flavor as fcp7.XML makes it very easy to import/export for the rest of the industry.
That’s why it didn’t take long. -
[David Lawrence] “LOL! FCPX is AWESOME! *”
Especially if you own stock in Avid and Adobe.
David Roth Weiss
Director/Editor/Colorist
David Weiss Productions, Inc.
Los Angeles
https://www.drwfilms.comDon’t miss my new Creative Cow Podcast: Bringing “The Whale” to the Big Screen:
https://library.creativecow.net/weiss_roth_david/Podcast-Series-2-MikeParfitandSuzanneChisholm/1POST-PRODUCTION WITHOUT THE USUAL INSANITY ™
Creative COW contributing editor and a forum host of the Business & Marketing and Apple Final Cut Pro forums.
-
[Jeremy Garchow] “VideoCompany#1 takes it over from there?”
No, Video Company#1 dropped the ball and went off to play with the opposition, don’t you remember?
Still, good for BMD – great news!
Simon Ubsdell
Director/Editor/Writer
http://www.tokyo-uk.com -
Apple leave desktop color grading segment in good hands. If windows version can render out prores, then we have winner.
Nikola Stefanovic
https://www.vimeo.com/nikolastefanovic/reel -
[Simon Ubsdell] “No, Video Company#1 dropped the ball and went off to play with the opposition, don’t you remember? “
I do have vague recollections of Adobe and Avid dropping the Mac platform altogether, yes.
Reply to this Discussion! Login or Sign Up