Charlie Austin
Forum Replies Created
-
Charlie Austin
October 28, 2013 at 7:17 pm in reply to: FCPX is not used by professionals and only suitable for editing home movies![Walter Soyka] “Charlie, it’s not all black and white. There are shades of gray. For example, I am a Luddite hack.”
🙂
————————————————————-
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
Charlie Austin
October 28, 2013 at 6:20 pm in reply to: FCPX is not used by professionals and only suitable for editing home movies![Steve Connor] “That’s a bit harsh, those sort of attitudes are mostly gone from here (with a few exceptions!)”
I agree. It’s generally quite civil and informative here these days… I was referring to the exceptions. And I must stress again, the exceptions are on both sides of the debate… 🙂
————————————————————-
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
Charlie Austin
October 28, 2013 at 6:15 pm in reply to: FCPX is not used by professionals and only suitable for editing home movies![Andy Branner] ” Got me again. :-(“
As you and Herb and others may have noticed, there are a few people here at the Cow, on both sides of this “debate”, with whom arguing is pretty much pointless.
If you do like FCPX, you are a home movie/cat video making fanboy hack, and clearly not a professional.
If you don’t like FCPX you are an irrelevant luddite incapable and afraid of learning new tricks.I think that about sums it up.
————————————————————-
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
Charlie Austin
October 28, 2013 at 5:12 pm in reply to: It is time to change the title of this forum.[Lance Bachelder] “This does not mean we’re not all holding out hope that Apple will still do something great with FCP, but as it sits it’s still not being used like those touting it as being ready for primetime wish it was.”
What, in your estimation, could Apple do that would be “great”?
————————————————————-
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
Charlie Austin
October 27, 2013 at 9:33 pm in reply to: It is time to change the title of this forum.[Bret Williams] “Did you try the new iMovie.”
I’ll say one thing, that little app is fast now.
[Bret Williams] “Everything is some hidden mystery. But the movie trailers are pretty addictive.”
You know you can convert them to “movies” i.e.: a regular timeline. Then you can replace music, change the cut etc. umm… not that I would ever do that as it would force me to have fun and sully my professional editing fingers with lowly consumer software…
————————————————————-
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
Charlie Austin
October 27, 2013 at 8:20 pm in reply to: It is time to change the title of this forum.FCPX sucks. It’s too complicated and costs too much. I’m moving all my sh*t to iMovie.
————————————————————-
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Chris Harlan] “[Jeremy Garchow] “Perhaps iMovie, in a shocking turn of events, is now iMovie Pro”
LOL”
After playing with it the other day, and having a fairly simple home video release spot to cut, I actually wanted to just do it in iMovie. 🙂 Unfortunately, my evil plan was foiled when I discovered there’s no XML export or anything like that in iMovie. What was Apple thinking! This is clearly not professional software! 😉
————————————————————-
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Simon Ubsdell] “For those of you to young to remember, it was always definitively argued that because FCP X was 64 bit and iMovie was only 32 bit there was self-evidently nothing that they could possibly have in common.
This argument was likely made by the same people who argue that FCPX was perfect when it was initially released, and to this day has absolutely no problems or shortcomings at all. It’s pretty self-evident that those people were/are wrong. 😉
[Simon Ubsdell] “Despite the apparently self-evident fact that the entire design underpinning of both products was identical at the point of X’s launch.
Instead we now have the rather bizarre scenario of folks arguing that the new iMovie is based on X – and of course wouldn’t look remotely like X if X hadn’t come first!!!!!”It’s pretty obvious, to anyone with eyes, that the design of FCP X was based on iMovie. Timeline, UI, event/project structure, skimming, magnetism, etc, etc. But, and I say this as someone who enjoys poking around in app packages, the guts of the 2 were very different. QtKit vs A/V foundation and totally different Plugin architecture were the biggies, but there were an enormous amount of fundamental differences, despite the similar look and feel.
Now, other than the vastly simplified UI, not so much. Maybe iMovie and X have a symbiotic, leapfrogging relationship…
A- Try out concepts in iMovie 8 -> build a brand new app, FCPX, based on those concepts.
—launch FCPX and make improvements over time. Meanwhile…
B- Rewrite new iMovie based on FCPX code and try out new concepts -> Use new concepts in FCP X ???
—I guess we’ll see in December… Maybe they’ll put “Pro Quality” Trailer Templates in X, and we’ll all be out of jobs. lol————————————————————-
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Jeremy Garchow] “That has probably changed with this new version, though.”
It has. It’s 64 now..,
————————————————————-
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Andrew Kimery] “If it’s it’s true it’s gonna be expensive,”
Probably, but if they are replaceable – which they probably are – and there’s a “pro” need for another card, I’d bet they’ll become available. As you say though, at a price…
————————————————————-
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~