Creative Communities of the World Forums

The peer to peer support community for media production professionals.

  • Stephen Galinsky

    June 29, 2011 at 8:32 am

    Booo, my post is in moderation so you beat me to it 😛

    But yeah, I agree with your assessment.


    Ed it.

  • David Battistella

    June 29, 2011 at 8:48 am

    I think that clearly answers pretty much every grave, heart stopping, business ending, I’m defecting, not professional, iMovie pro, how do I export?, how do I capture?, what about sound, open old projects, concern raised in the wild, frenzied, crazed, wild dog, rabid, uptight, passionate, heartfelt comment, discusion and debate raised in the past week.

    David

    ______________________________
    Believe me. Everything is a lie.

  • Tomislav Rupic

    June 29, 2011 at 8:52 am

    well, I am much more optimistic now, it just might end up being great
    software after all… more I work in it more I like it but without XML its no go…

  • David Battistella

    June 29, 2011 at 8:56 am

    I think many people will begin to share your opinion when the get over the way it looks and get into the way it performs.
    People love to gripe

    ______________________________
    Believe me. Everything is a lie.

  • Aindreas Gallagher

    June 29, 2011 at 9:06 am

    Really? Are you sure it does? What exactly has changed after that press release? Aren’t they saying basically the same kind of deflecting defense of the app that they were to pogue? And why in the hell didn’t they say they were restoring FCS 7 to the sales channel for even twelve months? As actually truly nearly everyone agrees, that one action would go a long way to mitigating the problems caused by the release of this software. The worst of it is – this is all we’re getting – essentially a restatement of their position. All the heat and light we generated in debate got us a pat press release. Not one person from apple will stand up and answer questions.

    https://bit.ly/jIUH2N

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

  • Ben Holmes

    June 29, 2011 at 9:18 am

    [Steve Connor] “Nothing much new here”

    Nothing new?

    “Final Cut Pro 7 will work with Mac OS X Lion”. WOW.

    “Does Final Cut Pro X support multicam editing?
    Not yet, but it will. Multicam editing is an important and popular feature, and we will provide great multicam support in the next major release.” OK.

    “Developers can also build 64-bit FxPlug 2 plug-ins for Motion 5, and integrate those plug-ins into templates that can be used in Final Cut Pro X. These templates, together with any associated FxPlug 2 plug-ins, will work in Final Cut Pro X even if Motion is not installed on the computer.” GOOD. OH, AND I SEE GENARTS ARE RELEASING PLUGINS FOR X, AND THERE WILL BE A FREE UPDATE FOR MAGIC BULLET LOOKS ON X.

    “Can Final Cut Pro X export XML?
    Not yet, but we know how important XML export is to our developers and our users, and we expect to add this functionality to Final Cut Pro X. We will release a set of APIs in the next few weeks so that third-party developers can access the next-generation XML in Final Cut Pro X.” PHEW.

    “When the APIs for XML export are available, third-party developers will be able to create tools to support OMF, AAF, EDL, and other exchange formats”. MAKES SENSE.

    “Does Final Cut Pro X allow you to assign audio tracks for export?
    Not yet. An update this summer will allow you to use metadata tags to categorize your audio clips by type and export them directly from Final Cut Pro X.” SOUNDS INTERESTING. And a lot like some sensible suggestions on this forum.

    Oh – and finally:

    “Can I purchase a volume license?
    Final Cut Pro X, Motion 5, and Compressor 4 Commercial and Education Volume Licensing will be available soon via the Apple Online Store for quantities of 20 or more. After purchasing, customers will receive redemption codes they can use to download the applications from the Mac App Store.” OH – I WAS ABOUT TO WRITE ANOTHER RANT ABOUT TIHS ON….

    One more clarification from me personally:

    “I hear on the COW FCPX projects won’t be read on an ethernet SAN?
    Not true – it took my SAN vendor about 5 minutes and a couple of lines of code to get this working”. OH – OK.

    But I guess these, and other clarifications about project sharing and so forth will not be enough for some people. There are certainly things in there to bother people – Apple have definitely decided to leave some things, like tape capture, to third parties from now on. If you can afford to buy or rent an HDCAM deck, my guess is you won’t mind. I think the media management needs urgent updating – it still looks inflexible to me, and moving projects out of the event folder to hide them is a massive kludge. But do you think this will be hard to fix? Not really. Sure – they SHOULD HAVE DONE THIS THE FIRST TIME. I get it.

    Incidentally, I’ve heard much the same about an SDK and APIs from my vendors – they are keen to work with Apple (and that includes those working on products with AVID and ADOBE, since previous Apple APIs have made third party integration much easier than (especially) AVID. If Apple knows one thing, it knows developers (even if it’s occasionally heavy-handed). In all cases, Apple has said “APIs are coming”.

    Now – we can all agree Apple’s PR was awful, and they handled this terribly. I still believe they should have continued to sell FCS3 (I just bought a couple of licenses to see me through on legacy work and existing broadcast projects), but can we now get back to reality with X? You may not like the paradigm, but surely we can put to bed the ‘Apple hates Pros’ meme? Some people need to get past that ‘import from iMovie’ menu item (another PR disaster) and look again.

    X will NEVER suit everybody. It may not suit anyone who doesn’t have the time or inclination to look at another paradigm. You may look at the paradigm and hate it. No worries – I get you. I haven’t decided yet – I’ve been hard at work most of the week, and have only just started learning X. But PLEASE – stop the personal attacks on the designer, and keep it civil. I don’t think much of what has been said here is fair or respectful. Would you have said the same to their face? I doubt it. This FAQ appears to show that in many cases, people were flat out wrong as well.

    Best wishes to everyone on the COW, whatever side of the argument you are on.

    Ben

    Edit Out Ltd
    —————————-
    FCP Editor/Trainer/System Consultant
    EVS/VT Supervisor for live broadcast
    RED camera transfer/post
    Independent Director/Producer

    https://www.blackmagic-design.com/community/communitydetails/?UserStoryId=8757

  • Ben Holmes

    June 29, 2011 at 9:20 am

    I enjoy every one of your posts David. Thanks for sticking around.

    Ben

    Edit Out Ltd
    —————————-
    FCP Editor/Trainer/System Consultant
    EVS/VT Supervisor for live broadcast
    RED camera transfer/post
    Independent Director/Producer

    https://www.blackmagic-design.com/community/communitydetails/?UserStoryId=8757

  • Paul Jay

    June 29, 2011 at 9:45 am

    Appel says Native XDCAM?

    So i can import MXF files into FCPX?

    Doesn’t work. XDCAM Quicktimes are NOT native. Apple loves the word NATIVE, when it’s not.

  • Ben Holmes

    June 29, 2011 at 10:04 am

    [Paul Jay] “XDCAM Quicktimes are NOT native. Apple loves the word NATIVE, when it’s not”

    The codec is native. The wrapper is not. Native MXFs are not nice to work with on PPro in my experience. What’s the issue with re-wrapping? Copying the media I guess…

    Edit Out Ltd
    —————————-
    FCP Editor/Trainer/System Consultant
    EVS/VT Supervisor for live broadcast
    RED camera transfer/post
    Independent Director/Producer

    https://www.blackmagic-design.com/community/communitydetails/?UserStoryId=8757

  • John Spirou

    June 29, 2011 at 11:02 am

    Exactly , different wrapper… its not transcoded.
    Same with dslrs… no problem.

Page 1 of 3

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