Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Creative Community Conversations Insightful post from Daring Fireball aka John Gruber

  • Greg Burke

    June 24, 2011 at 11:36 pm

    (mono tone) yay…

    I wear many hats.
    http://www.gregburkepost.com

  • Nigel Thompson

    June 25, 2011 at 12:20 am

    Just as I said ….. All they had to do was wait. Wait till it was really ready

    RED,DSLR, FCS and more,
    High End, Production & Post Production
    in the Caribbean
    http://www.bistt.com

  • Rick Fetters

    June 25, 2011 at 12:50 am

    I don’t know what the real numbers are, I think the three orders of magnitude difference mentioned in the Twitter post is high but I bet it could be two orders (100x) between the true Pros ~10,000 and the prosumers/amateurs 1 million plus. So why cater to the needs of 1% of your users? We are at the beginning of an explosion in the use of video, whether in smartphones, DSLRs, point and shoots, etc. The market for simple, easy to use, “professional” editing software ala FCE will be huge.
    I suspect that FCPX will eventually be a true professional app with all the bells and whistles that pros need. Right now it is more like FCE in abilities, not a true pro app. So why release it now? Because it is perfect timing with the soon to be released Lion to have an advanced amateur editor out that takes full advantage of the new recently released hardware and OS. By Apple not naming FCPX…FCEX, they have announced their intent for it to (eventually/ultimately) be a true pro app. I think they assumed the pros would not want to immediately jump on a brand new app and would want to wait until all the bugs were worked out. By that time (6mo-1year) they would have had a chance to upgrade it to pro specs. I think Apple probably anticipated the adverse reaction to the UI in FCPX, but not the FUD caused by the lack of pro features, or at least the level of hostility. Their MO has always been to hold their cards close to their chest and this has worked well for them. But in this case, I don’t think it was the best strategy. They should at the very least announce a time-line for feature development, assuming they want FCPX to really be a pro tool. With the current @#it-storm I think it forces their hand to be a bit more forthcoming.

  • Greg Burke

    June 25, 2011 at 12:52 am

    well avid will never pull this crap, and using FCPX in the industry just jumped back another 10 years.

    I wear many hats.
    http://www.gregburkepost.com

  • Rick Fetters

    June 25, 2011 at 1:13 am

    Apple probably considered waiting but obviously thought that waiting another 6mo or a year was just too long, especially when they had the basic core functionality completely finished. FCPX is a GREAT editor for those wanting to step up from iMovie or FCE, huge benefits in performance and features and all for $300. Why preclude all of those potential buyers for the next 6mo-1year while the full pro features are finished (again assuming they will be)?
    So they pulled the trigger with an early release.
    I don’t think they were prepared for the level or breadth of the hostile reaction to that decision. I bet we will see a clarification of their plans for FCPX very soon.

  • Aindreas Gallagher

    June 25, 2011 at 1:21 am

    that’s the thing I love about Gruber when he’s firehosing for apple – you really get the big italics.

    Apple made a play to make ipods out of editing. That as much speaks for itself.

    yep.

    https://bit.ly/ivsrTr

    http://www.ogallchoir.net
    promo producer/editor.grading/motion graphics

  • Jim Bachalo

    June 25, 2011 at 12:45 pm

    ‘They should at the very least announce a time-line for feature development, assuming they want FCPX to really be a pro tool. With the current @#it-storm I think it forces their hand to be a bit more forthcoming.’

    agree1000%

    Local is the new global

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy