Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Creative Community Conversations Thoughts on 10.1.2

  • Jeremy Garchow

    June 30, 2014 at 8:50 pm

    [Craig Alan] “Why then would they fall behind CC in features by re-writing its organization structure … twice? “

    I think this is the difference in opinion.

    Some may see it that Apple “rewrote” the organization twice, but what if those releases were planned? Events and Projects are now wrapped in to Libraries. It’s not like Events and Projects disappeared completely, rather, they simply had more functionality added to them, along with the media management to come with it, and the Library container. I think that this was planned, see Marcus’s point about Libraries requiring Mavericks.

  • Robert Gilman

    June 30, 2014 at 8:53 pm

    AFIK GarageBandX is LPX-lite just the same way that iMovie X is FCPX-lite.

  • Oliver Peters

    June 30, 2014 at 9:02 pm

    [Jeremy Garchow] “It’s not like Events and Projects disappeared completely, rather, they simply had more functionality added to them”

    Actually, no. The Projects library disappeared completely and the current implementation of Projects is just as part of Events. Projects as a separate entity lost capabilities. I, for one, think what they did was correct, but others, like Bill might disagree, since the previous layout worked well for him. There’s no explanation of why it wasn’t like that to begin with, other than this was a course correction. Either they found out the Events/Projects layout had painted them into a corner or they acquiesced to user feedback.

    – Oliver

    Oliver Peters Post Production Services, LLC
    Orlando, FL
    http://www.oliverpeters.com

  • Charlie Austin

    June 30, 2014 at 9:12 pm

    [Oliver Peters] “Either they found out the Events/Projects layout had painted them into a corner or they acquiesced to user feedback.”

    Maybe a bit of both. I liked the functionality of the project browser, despite it’s limitations. And those limitations could probably have been ironed out. But maybe improving the original idea was not going to work given what users seemed to want so they decided to take it in a different, “simpler” direction. Only Apple knows. Works pretty good now though. Only thing about the original organization I miss is skimming/playing projects without opening them. Hopefully that’ll return..

    ————————————————————-

    ~ My FCPX Babbling blog ~
    ~”It is a poor craftsman who blames his tools.”~
    ~”The function you just attempted is not yet implemented”~

  • Jeremy Garchow

    June 30, 2014 at 9:15 pm

    [Oliver Peters] “The Projects library disappeared completely and the current implementation of Projects is just as part of Events. Projects as a separate entity lost capabilities. I, for one, think what they did was correct, but others, like Bill might disagree, since the previous layout worked well for him.”

    The Project browser disappeared, yes, but Projects themselves, the naming and convention did not disappear. The Project structure and idea was incorporated in to Libraries, not entirely excommunicated. The data did change a bit because Projects are now called “.fcpevents” in the Finder which is probably what needed to happen, and I know you’ll think I’m crazy, but I bet it was probably planned the whole time.

    Since Mavericks seems to have been required in order for FCPX to have Libraries, then how could we have had Libraries before Mavericks? We couldn’t, so they had to build the Project Browser and keep Projects and Events separate.

    Once you had a Library, then the Project Browser didn’t make any sense.

    Projects themselves gained a ton more media management capabilities and made things easier with, snapshots/versioning, and being able to open and close a library unto itself instead of browsing all Projects at all times. But I guess we can agree to disagree on what capabilities were lost.

  • Craig Alan

    June 30, 2014 at 9:22 pm

    So they decided to create a ton of development work for themselves and lost a lot of customers to Adobe by introducing FCP X before they were able to use the library system that was just introduced? I’ll grant you that Thunderbolt was introduced with its future evolution mapped out. But if the current library system was part of FCP X’s design from the get go why did it take this much time to write the code? Granted they have deep pockets and can buy top talent to write their apps, but I think this theory is both cynical and illogical.

    Mac Pro, macbook pro, Imacs (i7); Canon 5D Mark III/70D, Panasonic AG-HPX170/AG-HPX250P, Canon HV40, Sony Z7U/VX2000/PD170; FCP 6 certified; FCP X write professionally for a variety of media; teach video production in L.A.

  • Craig Alan

    June 30, 2014 at 9:25 pm

    Libraries existed way before Mavericks. They did not have to wait for Mavericks to organize FC media this way.

    Mac Pro, macbook pro, Imacs (i7); Canon 5D Mark III/70D, Panasonic AG-HPX170/AG-HPX250P, Canon HV40, Sony Z7U/VX2000/PD170; FCP 6 certified; FCP X write professionally for a variety of media; teach video production in L.A.

  • Jeremy Garchow

    June 30, 2014 at 9:37 pm

    [Craig Alan] “So they decided to create a ton of development work for themselves and lost a lot of customers to Adobe by introducing FCP X before they were able to use the library system that was just introduced? I’ll grant you that Thunderbolt was introduced with its future evolution mapped out. But if the current library system was part of FCP X’s design from the get go why did it take this much time to write the code? Granted they have deep pockets and can buy top talent to write their apps, but I think this theory is both cynical and illogical.”

    We see this problem for two very different points of view. The early versions of FCPX were the stepping stones.

    They didn’t create a ton development work for themselves, they were actually putting in the work developing it. Was FCPX released a bit too soon? Perhaps, but looking back, there was really no other way to do it.

    As mentioned in a previous response, I don’t know why it’s taking so long. It must be hard work, or Apple isn’t in a hurry, or, they are waiting for OS level functionality in order to make FCPX what they want it to ultimately be.

  • Marcus Moore

    June 30, 2014 at 9:54 pm

    My thinking that some form of unmanaged library would have been possible in 2011, since they exist in other NLEs. I’m just saying this particular implementation using these Library bundles specifically, wasn’t possible before Mavericks.

  • Franz Bieberkopf

    June 30, 2014 at 10:02 pm

    [Marcus Moore] ” I’m just saying this particular implementation using these Library bundles specifically, wasn’t possible before Mavericks.”

    Marcus,

    Why not?

    Franz

Page 5 of 8

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