-
One year later…
-
[Chris Kenny] “I find that very unlikely. The only realistic way Apple could have changed the perception of who was being targeted with the first release would have been to hold the entire release until additional high-end features could be implemented. Even then, the pump was primed — there were many people already buying into the “Apple is abandoning pros” narrative (ironically because an FCP replacement hadn’t shipped yet). People were looking to fit anything Apple shipped into this narrative — it would have been very hard to avoid.”
You find it unlikely that people would not have complained if Import from iMovie wasn’t a feature at launch? 😉
I agree that if FCPX would’ve launched with high-end features enabled that would have given a different perception to the launch. And what you are saying furthers my hypothesis. At some point during the development of FCPX the choice for launch features was set (iMovie thumbs up, XML thumbs down). If it was a time crunch issue why didn’t they get started on development earlier? I’m sure w/all of Apple’s in-house development experience they could do a good job of planning out realistic development schedule.
Honestly, I think the resources got pulled to work on iOS projects, which also explains the final, lackluster update to the FC Suite, and so there was a rush job to get FCPX out because they natives were really getting restless.
Which, again, goes back to my point that when push comes to shove the ProApps users are going to be placed on the back burner (If Mac OS development can be delayed because of iOS I assume anything can). It makes total business sense for Apple but does it make business sense for someone like me that uses these tools for a livelihood? Sure, Avid and Adobe might not be reinventing the wheel (though they are both doing a better job of supporting old media and new media workflows than Apple currently is) but I don’t worry about the next version of MC or PPro getting delayed, or under-delivered, because they diverted massive internal resources to work on an iDevice app. I can’t say the same for FCPX.
W/all that being said it’s not like I’m ruling out FCPX forever. If I see potential gigs start using it I’ll pick it up but I doubt I’ll make it my go-to NLE like FCP classic was.
-Andrew
2.9 GHz 8-core (4,1), FCP 7.0.3, 10.6.6
Blackmagic Multibridge Eclipse (7.9.5) -
[Chris Kenny] “Adobe wouldn’t suffer all that much without Premiere.”
I was talking about Adobe’s entire professional line of software, not just PPro (which I agree is the ugly duckling of the bunch). I don’t think PS Elements would sustain Adobe for very long. 😉2.9 GHz 8-core (4,1), FCP 7.0.3, 10.6.6
Blackmagic Multibridge Eclipse (7.9.5) -
Check their NAB demo. They demo’d how their ISIS systems can do cloud editing with their “Interplay Shere” product.
-
Always interesting to hear the thoughts of someone in your shoes.
-
[Chris Kenny] “Adobe wouldn’t suffer all that much without Premiere. After all, it hasn’t been taken very seriously to date, and they’ve been doing just fine. It’s not clear how many additional copies of Creative Suite Adobe can even sell by improving Premiere. For instance, if we decided to migrate to Premiere here, it would result in zero additional sales for Adobe, as the systems we’d use it on already have Creative Suite licenses which were purchased to get Photoshop/Illustrator/AE/Encore. This is probably true for a lot of potential Premiere users.”
I think many people miss what I consider to be the main point – namely the workflow of Production Premium in its entirety. In this case, Premiere Pro is the ‘hub’ application – where things like After Effects, Photoshop and others feed into the main organizational, story-telling tool.
From a business side, lacking a serious NLE client in the suite WOULD hurt sales because it would be incomplete. While Avid, FCP, et al users wouldn’t be affected, there are many MANY who would.
Your statement of using Premiere Pro would increase Adobe sales by zero is true for you and others, but for many larger organizations who are determining which NLE to use in the future, they have different groups like graphics vs. editorial that would result in new seats. As a person who primarily focuses on broadcast and large media companies, I’ve seen many different variations of this over the last couple of years.
The above is a statement of 2010’s growth in video – prior to FCP X. I can tell you that our growth for 2011 with FCP X out in the wild wasn’t too bad either. 😉 That growth had to come from somewhere and I would tell you that it’s my personal belief that it comes from a complete suite of tools and workflow that are most compelling to those users who purchased Production Premium in the last two years.
While you may dismiss Premiere Pro (and that is your prerogative) , there are evidently a number of people who are taking Premiere Pro seriously in the pro market.
Respectfully,
Dennis – Adobe guy -
[Chris Kenny] “I’ve seen zero interest thus far in Premere among real-world contacts, ”
Our mileage differs. I hope your opinions are based on observation rather than wishful thinking. Personally I am NLE agnostic so I am only interested in reporting what other tell me. My decisions are purely based on serving the most popular systems.
“We seem to keep hearing that FCP X’s feature set is still considered insufficient, but I can’t help but notice that unlike a year ago there aren’t many specific features being mentioned.”
Again wishful thinking and observational bias. Just today on this forum issues like keyframing, auto saves, opening multiple sequence, copying file attributes were mentioned. For me I add lack of machine control, the fact that the output via SDI is still not video and audio synced. Yes I can work around these things but why should I?
The only reason why specifics are not being mentioned is because many here have just grown tired of reminding the forum of what is still missing. Great that our list is getting smaller.
Once the list is gone we can then just look at the NLE in direct comparison to systems that already offer the ‘must have features’ that define our workflows. Until then do not misconstrue our lack of constant lists of complaints as compliance or acceptance that we will do without, not now that Autodesk, Avid and Adobe are making serious strides in the right direction. Rather take it as a sign that we are giving up on Apple in the short term and moving to those viable options. By all means Chris, stay and argue the cause. Just don’t be surprised if we remain unconvinced.
-
Not quite sure how to interpret that. What shoes do you see me as wearing?
-
[Daniel Frome] “Check their NAB demo. They demo’d how their ISIS systems can do cloud editing with their “Interplay Shere” product.”
Thanks. That’s an example that shows Isis is more than a bit bucket. It also shows what one can lose if Avid folds or is sold or makes a major structural change for financial reasons that impact certain products.
-
Ugh, thanks. So if Avid actually folding? Why are you insinuating this?
Reply to this Discussion! Login or Sign Up