Creative Communities of the World Forums

The peer to peer support community for media production professionals.

  • David Roth weiss

    March 4, 2012 at 6:17 pm

    [Floris van Eck] “FCP X is one of the best applications I ever used.”

    Editing in solitary confinement may be great for you Floris, but if you don’t fully understand why many of us can’t embrace that model, you’re hardly the right person to tell us how and what we should be thinking.

  • Bob Woodhead

    March 4, 2012 at 7:38 pm

    Noob. (@Floris)

  • David Cherniack

    March 4, 2012 at 8:10 pm

    [Herb Sevush] “[Floris van Eck] “To me, it makes Premiere and Avid look like a toy.”

    Hyperbolic overstatement.”

    I hate to say it, Herb, but yours is a hyperbolic understatement. He, she, it, is obviously as clueless as they come. And I don’t mean that as a personal attack, merely as a statement of fact.

    David
    AllinOneFilms.com

  • Steve Connor

    March 4, 2012 at 8:26 pm

    [David Cherniack] “I hate to say it, Herb, but yours is a hyperbolic understatement. He, she, it, is obviously as clueless as they come. And I don’t mean that as a personal attack, merely as a statement of fact.”

    Sounds a bit like a personal attack though?

    Steve Connor
    “FCPX Agitator”
    Adrenalin Television

  • David Cherniack

    March 4, 2012 at 8:45 pm

    [Steve Connor] “Sounds a bit like a personal attack though?”

    True, enough, but the point is that in the face of such a massively inflamatory and ignorant statement, a little bit of a calling a spade a spade is justified. If I’ve offended anyone I’ll re-phrase:

    “What an ignorant, inflammatory statement. I bet that person either doesn’t know what they’re talking about or is a troll.”

    David
    AllinOneFilms.com

  • Steve Connor

    March 4, 2012 at 8:50 pm

    [David Cherniack] “True, enough, but the point is that in the face of such a massively inflamatory and ignorant statement, a little bit of a calling a spade a spade is justified. If I’ve offended anyone I’ll re-phrase:

    “What an ignorant, inflammatory statement. I bet that person either doesn’t know what they’re talking about or is a troll.””

    I wasn’t offended, just pointing it out!

    Fortunately the type of post Floris made is now increasingly rare here.

    Steve Connor
    “FCPX Agitator”
    Adrenalin Television

  • Jim Giberti

    March 5, 2012 at 6:27 pm

    Any professional working with FCPX knows that it’s not just an incomplete program, but an incomplete concept.

    Accepting an incomplete program as a step ahead of the competition is counter productive.
    Companies need reasonable and firm response from users in order to implement critical changes and fixes.

    Contrary to some companies philosophies, no one knows what needs to be in a toolset better than the people using the tools.

    Campuses and teams are great, but the real work happens in the field and that’s where the real innovations are born.

  • David Lawrence

    March 6, 2012 at 2:01 am

    [Andrew Richards] “That fork was at WWDC 2007 when Apple suddenly nixed the 64-bit Carbon API plan. This is likely why FCP7 was so underwhelming compared to FCP6 and FCP5- FCP7 was going to be 64-bit, but the FCP team had the same rug pulled out from under them as Adobe and any other developers of apps that dated back to the OS 9 era. Mid-2007, Pro Apps all of a sudden had to punt on their plans for FCP7 and simultaneously start a ground-up re-write of FCP.”

    Agreed. There’s no question the switch away from Carbon was totally disruptive and caused a reboot. But as Avid and Adobe clearly demonstrate, there’s no reason a 64-bit rebuild requires a radical UI redesign.

    The AppleInsider article was spot on about target market changes in FCPX. Given how rushed and incomplete the initial release was, I think they got the corresponding management changes and timing right as well. Totally believable that Ubillos came back in sometime in 2010 with an order to simplify and build on his iMovie work. To me, this scenario makes the most sense and explains the baffling nature of the release. This implies the fork was sometime in 2010.

    [Andrew Richards] “It could also be proof they had an evolving idea of how they would implement their goal of eliminating clip collisions and maintaining audio sync for video+audio clips versus just audio. Looking at that image, I see an attempt to do it with something resembling tracks, but with zones for different kinds of media. I don’t think that was necessarily a fully baked idea that got abandoned. I find it more likely that it is a step on the path that got us here, especially given its continued presence in the .app bundle.”

    I see it a bit differently. First, the name – Sequence.icns. That says a lot right there. Seems obvious this is a sequence icon. With tracks. Clearly they’re thinking about better organization schemes. Stereo(?) audio is grouped into single clips. This is something Logic Pro and Soundtrack Pro have done for years so it’s not surprising. Audio is below video with variably sized tracks and dividers. Synced clips are shown in the darkened region.

    I don’t see anything that indicates clip collision avoidance is even on the radar. I think that and the magnetic timeline came when Ubillos was brought back in.

    Also, the Cocoa-flavored graphics suggest a very different direction for FCPX building on Cocoa.

    Curious, what’s your take on why this mysterious icon is still in the package after two updates?

    [Andrew Richards] “There was another very significant development disruption confounding FCP development following the death of 64-bit Carbon, and that was the false start of 64-bit QuickTime with QTKit and the development of QuickTime’s ultimate successor in AVFoundation and CoreMedia. As that shift took place from 2008-2010, the burden of handling much of the pro video codecs and processing was being shifted from the Pro Apps team to the CoreOS team. That doesn’t explain away the 40 layoffs, but it is reasonable based on what we now know about the APIs that FCPX calls to imagine a redundancy arising between the dev team on FCP and the dev team on OS X and iOS that was taking over responsibility for dealing with that significant component of what FCP does.

    You could be right, I could be wrong, but I think my scenario is at least as plausible as yours.”

    Absolutely, we’re both reading tea-leaves and speculating on hieroglyphics. It’s a fun sport. 😉

    _______________________
    David Lawrence
    art~media~design~research
    propaganda.com
    publicmattersgroup.com
    facebook.com/dlawrence
    twitter.com/dhl

  • David Roth weiss

    March 6, 2012 at 2:20 am

    [Jim Giberti] “Contrary to some companies philosophies, no one knows what needs to be in a toolset better than the people using the tools.

    Campuses and teams are great, but the real work happens in the field and that’s where the real innovations are born.”

    Right on the money as always Jim.

    David Roth Weiss
    ProMax Systems
    Burbank
    DRW@ProMax.com
    http://www.ProMax.com
    Sales | Integration | Support

    David is a Creative COW contributing editor and a forum host of the Apple Final Cut Pro forum.

  • Andrew Richards

    March 6, 2012 at 2:22 am

    [David Lawrence] “Curious, what’s your take on why this mysterious icon is still in the package after two updates?”

    I doubt anyone in Pro Apps is attuned to our Show Package Contents augury. My inner Occam’s Razor tells me it is the software equivalent of a drywaller’s coffee cup sealed in the wall and forgotten about. That is why I came to the conclusion it is part of an evolution, that they didn’t start over with a new codebase, they carried forward an existing one with different UI concepts sketched out.

    Or maybe it is an easter egg put there by an insubordinate developer who disagrees with the direction they ultimately went. It is certainly a puzzling artifact.

    Best,
    Andy

Page 4 of 6

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