-
FCPX from an Editor who used it on Iditarod 2012
-
[Jim Giberti] “Right, but I don’t think it’s just me…why did 1.0.3 go the other way with performance?
I was becoming a big fan, warts and all, because of performance and features, but I’m convinced that they made a boo boo with the update.”
So many beach balls for me as well. Notice his comments on using the Izotrope AU plugin. Obviously they made a change that impacted performance in ways they probably didn’t vet throughly. I think this is part of the “hurry up” schedule they’re on which seems to be at around 12 weeks for each release give or take.
I don’t doubt Apple is acutely aware of the flaws in their QC process but they’re also aware of what a slower rate of change would do. It’s a risk benefit analysis I suspect they’ve made. I suspect they’ll be bumps throughout the rest of this year as they try to push things out quickly. I suspect at some point they’re going to do a reconnoiter and do a major issue focused release (like 10.0.2 was but more extensive) but it’ll mean little movement in the feature set at that point. I think they’re juggling a bit, much like the guy on the Ed Sullivan show with all the plates and some of the plates are falling. I do think they’ll addresses them along the way.
I know we want everything and we want it now but their real world development is prioritizing things with their secret formula.
-
Implied rather than explicit but given he’s from NJ he either spend many a dime to go there or this was a real job which required a real decision on which NLE he used (unless you think Apple was the one who paid his way). The conclusion was certainly some issues that badly need to be addressed but an overall experience better than FCP7. Some of us, me included, really do prefer FCPX to 7 wherever and whenever possible.
-
[TImothy Auld] “And to put an even finer point on it there is nothing in this video that addresses his workflow from beginning to end. Or even from the beginning. What is it other than a house organ?
Tim”
Uh,
I didn’t realize that this was supposed to be a “workflow training product.”
It’s just the story of a working editor. Cutting a real project on real deadlines in the real world. Using a new tool that many people are interested in.
Nothing to get upset about, Tim.
(Do you tear up car brochures when you read them and decide that the model being shown doesn’t fork for your particular family situation? Must be a tough life for you if that’s your approach to all product change.)
“Before speaking out ask yourself whether your words are true, whether they are respectful and whether they are needed in our civil discussions.”-Justice O’Connor
-
[Craig Seeman] “Some of us, me included, really do prefer FCPX to 7 wherever and whenever possible.”
The straw man argument again. It is fair to Compare it to PPRO, Edius, Avid or Vegas, but comparing it to EOL’d software? – Why don’t you compare it to a Steinbeck while your at it.
Herb Sevush
Zebra Productions
—————————
nothin’ attached to nothin’
“Deciding the spine is the process of editing” F. Bieberkopf -
[Bill Davis] “Either we’re all crazy”
C’mon Bill, that’s too easy, you gotta make us work for it.
Herb Sevush
Zebra Productions
—————————
nothin’ attached to nothin’
“Deciding the spine is the process of editing” F. Bieberkopf -
Bill,
Careful what you “quote.” Did I say anywhere at at anytime that this was – entirely in your words by the way – a “workflow training product” No. I did not. What I said, and which you did not address, is that the original post seems very much like a house organ. So let the person who posted it come and defend it. I doubt he needs you to do so.
Tim
-
[Herb Sevush] “It is fair to Compare it to PPRO, Edius, Avid or Vegas, but comparing it to EOL’d software? – Why don’t you compare it to a Steinbeck while your at it.”
It’s certainly fair to compare it to non Apple NLEs. He doesn’t do that so there’s no “there” to look at in this video. He’s just pointing out that it’s better than FCPX in his opinion which, for some here, can’t seem to get past.
Certainly some of the features FCXP has, have been in PPro for some time and some are better implemented in Avid currently.
That set of comparisons are for someone else to make when they do an FCPX project having used Avid or PPro recently.
-
[Craig Seeman] ” I think this is part of the “hurry up” schedule they’re on which seems to be at around 12 weeks for each release give or take.”
Why can’t they now just get the wretched thing right instead of rushing out ill-considered and inadequately QC’d updates? They’re just looking more and more incompetent each time they do this.
PSD support, multicam, and broadcast support are clearly a mess that they thought they had to get out there in order to stem the flow of criticism. It’s become increasingly apparent that they’re panicking …
I so wish that weren’t the case and they were actually on top of this thing, but that’s a position it’s very, very hard to support.
Their pants are down around their ankles and it’s not a pretty sight.
Simon Ubsdell
http://www.tokyo-uk.com -
[Craig Seeman] ” this was a real job which required a real decision on which NLE he used (unless you think Apple was the one who paid his way).”
“I’ve been using it (chuckle) almost by force”
In the video he implied that the decision to use X wasn’t exactly his.
Herb Sevush
Zebra Productions
—————————
nothin’ attached to nothin’
“Deciding the spine is the process of editing” F. Bieberkopf -
[Simon Ubsdell] “Why can’t they now just get the wretched thing right instead of rushing out ill-considered and inadequately QC’d updates? They’re just looking more and more incompetent each time they do this.”
I’m sure it’s a managerial decision that they need to show feature progress. I’m sure there’s some serious internal “battles” on feature vs stability. They’re getting hit publicly from both sides so I’m sympathetic with the juggle.
[Simon Ubsdell] “PSD support, multicam, and broadcast support are clearly a mess that they thought they had to get out there in order to stem the flow of criticism. It’s become increasingly apparent that they’re panicking …”
I can’t blame them though. They’re getting damned if you do and damned if you don’t. In fact one could say this is what happens WHEN THEY DO LISTEN . . . and everybody is talking at once and with conflicting priorities.
I’d have to say, all things considered, even I’m “bitting the bullet” and appreciating the feature releasees (despite their issues) because they are showing “feature intent” and, I’d suspect from a marketing perspective that’s the most important “rescue” as far as their public face.
To put it one way. I have confidence they’ll fix the bugs, the lack of confidence comes from whether “professional” features will be implemented so they make decisions such as “beta” broadcast monitoring to let the world know they’re working on it. This is just Apple’s way of “informing” people.
[Simon Ubsdell] “Their pants are down around their ankles and it’s not a pretty sight.”
It depends on how you look at that. I’d argue it’s nice that they’re showing us their stuff at least.
Way back when I made the “autistic” analogy of listening and responding (I know analogies are against the COW law now) but this seems to be how they listen and respond.
People want to “hear” about the roadmap. Apple’s way is to reveal the road even though the pavement has yet to be smoothed. My own opinion is that it will get smoothed and I very much appreciate seeing the road even with its bumps.
Reply to this Discussion! Login or Sign Up