-
Henry Ford on FCP X
-
[Michael Gissing] “Few of us are that important to Apple. They are tossing some tasty bones and like faithfully puppies we follow, keenly hoping for more scraps from the great table.”
No. You misunderstand. It is the future of the whole world and the beginning of the Singularity. Gods are among us. Ask yourself–do you ever–I mean ever–see Mecca and Cupertino in the same place, at the same time, at the same party? I though not.
-
[Michael Gissing] “prosumers”
Do you editorgeeks remember when the HVX200 hit the market?
Do you EGs remember when red hit the market?
XDCAM?
How about the weird “rosetta” interregnum?
Does anyone, anywhere remember (Bueller? Bueller? Bueller?) AIC?It’s a real question.
Follow up: Where are we now?
-
[Bill Davis] “paid to look farther downstream”
or is it further
-
[Bill Davis] “fixed lots of issues and bugs”
Ok. here it is. PIOPs suck. Folks in this forum (the three blind mice) arguing for PIOPs though they don’t use X are notcool — the extent to which Apple heard their arguments.
Simple easy point: If you ain’t usin’ the software, stop “improving it” from your (malapropisms) point of view of “theory” guised actually as speculation. It was laughable when the three blind mice said piops were impossible because of the codebase and then they b begging blindly for siops. Threeblindmice, if you ain’t usin it. go away.
I.M. feeling better now.
deep breath.
moving on…we need single payer health care. -
[Oliver Peters] “Sometimes complexity and the need to put in effort to LEARN your tools is a good thing. “
oh olly. You can’t even export a file out of X, man. Hard to take your critique seriously. Seriously.
No offense intended. Your ethos is flopping on the deck like Truckee river salmon. Just pointing out the obvious. If you don’t like the software, stop using it. Sheesh.Like you said “…LEARN your tools…”
–all in good faith and humor, Rich
-
[Walter Soyka] “The best lesson of FCP7: there’s no one perfect NLE.”
Bone to pick here too:
ok if that’s actually true, then you need to stop trying to “fix” what you don’t like about X. Just live with its failings and move on. A final kiss goodnight. X goes that way <– you go that way –>. You don’t have to hate each other or sue for child support. Just break up. Move on. Find a new one. Plenty of fish in the sea. Other cliches to type.
The speculation you posited proved false, ergo PIOPs are impossible because of the code. Well, apple proved you wrong and screwed up my workflow. I use X. You don’t. Easy peesy: move on.Not trying to be a dick (though my name is Richard) just pointing out the obvious.
-
[Richard Herd] “[Oliver Peters] “Sometimes complexity and the need to put in effort to LEARN your tools is a good thing. ”
oh olly. You can’t even export a file out of X, man. Hard to take your critique seriously. Seriously.
No offense intended. Your ethos is flopping on the deck like Truckee river salmon. Just pointing out the obvious. If you don’t like the software, stop using it. Sheesh.Like you said “…LEARN your tools…”
–all in good faith and humor, Rich
“
What? Are you drunk or something? Chill out.
-
Hello,
the role of consumer demands and innovations is scientifically well researched.
FCP-X is what Clayton M. Christensen has called a Disruptive Innovation.
See his book The Innovator’s Dilemma.
A Disruptive Innovation not only introduces an innovation –
every successful company need to do so – but also shifts
the valuation criteria of the market itself.One interesting point of Disruptive Innovations is, that at their introduction
they can’t compete with established premium products, but within a niche they
evolve much more faster that the established competition that is already over-engineered.I would recommend to read this book to everyone who wonders about Apple’s product strategy – for Steve Jobs it was one of the most influential books he ever read!
Clayton M. Christensen: The Innovator’s Dilemma
Best regards,
Bernhard -
[Aindreas Gallagher] “I made this point a while ago, but I wonder at Apple’s pricing here, and whether the new 299 figure represents a realisation that they can take an amazon style approach to the market. In that they are engaged in market decimation through pricing, simply because they can. “
Well, yes, the application is cheap, but when you realize that you need a new system (computer, HDs, monitoring) to make it work and the price and time for “wrapping your mind around the new paradigma, you realize that the 700 bucks you save in the application are peanuts.
rafael -
[Walter Soyka] “The best lesson of FCP7: there’s no one perfect NLE.””
[Richard Herd] “Bone to pick here too: ok if that’s actually true, then you need to stop trying to “fix” what you don’t like about X. Just live with its failings and move on. A final kiss goodnight. X goes that way <– you go that way –>. You don’t have to hate each other or sue for child support. Just break up. Move on. Find a new one. Plenty of fish in the sea. Other cliches to type.”
As I said, there’s no one perfect NLE. There are things in every one of them I’d like to see improved.
I have been very critical of elements of FCPX, but I’ve always liked FCPX’s metadata-driven log/search approach, I think it’s effects architecture is wonderful, and I’ve even been making the case for why the parent/child timeline is a valid approach. If I were doing the interview-driven corporates today that I did 10 years ago, I think I would be a major FCPX cheerleader. As it stands, it’s a bit less useful for my work now, as all the really good stuff benefits other workflows. I don’t want to change FCPX to FCP8, but I do think there’s room for improvement within its current paradigm.
If you’d like to talk about the lists of things I don’t like in Premiere or Smoke and want to see improved, we can do that, too! (Sorry, MC. I know we haven’t seen each other much lately. It’s not you, it’s me.)
[Richard Herd] “The speculation you posited proved false, ergo PIOPs are impossible because of the code. Well, apple proved you wrong and screwed up my workflow. I use X. You don’t. Easy peesy: move on.”
You are really mad at me for PIOPs, aren’t you? You bring it up in every thread. I am sorry if my Internet rants about data fragility carry such incredible influence in Cupertino that they caused Apple to break your workflow. (Or just maybe a lot of other editors were frustrated by fragile ranges, too.)
Phillip H. and Jeremy G. gave excellent reasons to think PIOPs couldn’t happen (because there is more than one entry point to the same piece of media, raising both database and UI issues), and I bought into it. Obviously, I was wrong. Further, I agree with you that the implementation is poor and takes away something that was very good about FCPX. I’d rather drop PIOPs (10.0.5) than have the implementation we have now (10.0.6).
I think I pointed out a problem (range fragility). As we’ve all seen since then, and as I’m the first to admit, my proposed solution (PIOPs) failed badly. A bad solution doesn’t prove the non-existence of the problem it purported to solve.
TL;DR: FCP7/FCPX has opened my eyes to the fact that our NLEs could all be a lot better. I do hope they all become better, and one way that we as users can help the developers improve the products is by sharing our experiences using them.
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
Reply to this Discussion! Login or Sign Up