Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Creative Community Conversations Thank you Apple – and don’t change course. Please

  • Jules Bowman

    May 3, 2012 at 10:12 am

    That was a thoroughly enjoyable and well articulated read. It should be a full stop at the end of the Debate, but sadly it won’t be. Anyway, cheers Scott.

  • David Cherniack

    May 3, 2012 at 11:01 am

    Well and passionately put, Scott.

    I would question if FCPX will ever be up to main stream high-end use. I do believe that Apple probably intends to get there but on its own terms. However NLEs are the most complex applications in computerdom and it would take them a number of years (possibly 3, as many as 5) before they could even hope to regain a footing as a player in the high end. In that time, of course the competition won’t be standing still. And both Adobe and Autodesk and even Avid have superb engineering and the freedom to develop innovative technology that Apple, perhaps, as primarily an ‘experience’ company, doesn’t have. What great applications have they ever developed in house from scratch? Even the non-application OSX is derived from elsewhere.

    So I’m not convinced that despite what I perceive as their intentions, that they’ll again be a major player in the higher end of the industry. They made their bed with FCPX and the use categories it serves, and that will most certainly spill over into the high end here and there, but will they ever be a fixed point around which most of the industry revolves? I very much doubt it.

    David
    AllinOneFilms.com

  • Carsten Orlt

    May 3, 2012 at 11:30 am

    What I don’t understand is why you are so angry that you have to throw around insults after insult just because I stated my personal opinion. I did so openly clearly stating that it is MY opinion.

    And this is exactly why I do not care about people like you who clearly confirm the ‘my way or the highway’ attitude.
    If I do not share your opinion I’m 80 years old or some lunatic amateur. Real classy response…

    Sorry that you feel so betrayed by Apple and fair enough that it makes you decide to use other software and hardware. But please do not call me things without knowing who I am or what I do and how many years experience I have using any NLE. I did not call you anything nor did I call anybody not using FCPx or not wanting to use it not a storyteller or anything else.
    I used the term to express that I’m not a heavy FX user. Just a lot of straight forward editing. Maybe I should have said documentary editing if that makes you feel less annoyed. And some docu people can’t use FCPx because they need multi editor workflows as Mark pointed out.

    But I said it is my story, not yours or anybodies else’s.

    Now you have to excuse me because I need to upload another Youtube video before I join my mates at our retirement home annual wheelchair party 🙂

  • Timothy Auld

    May 3, 2012 at 11:34 am

    I’ve only used X once on a short piece with uncomplicated audio and it performed fine. Despite what I read about how it is a totally new way to do things and people are too – lazy, old, stupid, set in their ways; just pick one – to understand it, I found it pretty easy to adapt. But normally I work on longer form jobs with a lot more media and often with other editors. I could not even begin to trust X in a situation like that. And more practically speaking, the folks I do that sort of work for would not take me seriously if I suggested working with it.

    Tim

  • Dennis Radeke

    May 3, 2012 at 11:38 am

    [Carsten Orlt] “A lot of discussion here is also about native format support. I understand if you have fast turnarounds you like the fact that nothing needs to be transcoded initially (eventually it will). When you work for month on a single project I couldn’t care less about a few nights the computer humming away to get footage transcoded. Again exactly what FCPx does best. Ingest fast to get going and transcode in background. So mercury engine is cool but not necessary.”

    As Greg already pointed out the Mercury Playback Engine is not what gives Adobe Premiere Pro it’s capabilities, it was there before the MPE came into existence with CS5. Apple actually called out in its announcement that they are ‘resolution independent’, something that Adobe said around the CS3 timeframe and actually goes back to the complete re-write that became Premiere Pro 1.0 (as opposed to Premiere).

    The key difference between FCPX and Premiere Pro in this case is that FCPX still encourages you to transcode, though you can turn it off. Premiere Pro fundamentally believes in editing real-time natively all the time. You don’t HAVE to convert your footage ever. You can transcode if you wish, but we strive to make that a non-issue from an editorial perspective.

    That said, with an iffy (read old) computer and highly compressed temporal footage (think DSLR and AVCHD), your experience in an all native edit might encourage you to convert your footage, which of course both FCP X and Premiere Pro (and many others) can do.

    Hope this clarifies,
    Dennis – Adobe guy

  • Daniel Frome

    May 3, 2012 at 11:51 am

    By the way Dennis I…ugh… ‘came across’ that CS6 trial that was floating around the RED forums. Amazing.

    /fist bump

  • Carsten Orlt

    May 3, 2012 at 11:51 am

    [Dennis Radeke] “You don’t HAVE to convert your footage ever”

    Thank you for the clarification Dennis. I do not know Premiere in detail so I was misinformed.

    Could you explain how it does work when you put 5 different codecs into one sequence? Will the final output switch on the fly between the different codecs or does it convert everything on the fly to a chosen master codec? I always thought you need a final render in the end at least?

    Cheers
    Carsten

  • Michael Gissing

    May 3, 2012 at 11:51 am

    I know Carsten and I can verify he is experienced and does excellent broadcast documentary work. I can understand that he finds X to be heading in a direction that suits him and to be fair he did say very clearly that he was stating an opinion.

    I am no fan of FCPX but I do think it has reached a point where I can advise editors that there is a broadcast workflow if you want to use it. I know many feel burnt by Apple and this debate has certainly gone beyond bland comment often but slagging off at people in ignorance is hardly edifying.

  • Carsten Orlt

    May 3, 2012 at 11:56 am

    What I don’t understand is why you are so angry that you have to throw around insults after insult just because I stated my personal opinion. I did so openly clearly stating that it is MY opinion.

    And this is exactly why I do not care about people like you who clearly confirm the ‘my way or the highway’ attitude.
    If I do not share your opinion I’m 80 years old or some lunatic amateur. Real classy response…

    Sorry that you feel so betrayed by Apple and fair enough that it makes you decide to use other software and hardware. But please do not call me things without knowing who I am or what I do and how many years experience I have using any NLE. I did not call you anything nor did I call anybody not using FCPx or not wanting to use it not a storyteller or anything else.
    I used the term to express that I’m not a heavy FX user. Just a lot of straight forward editing. Maybe I should have said documentary editing if that makes you feel less annoyed. And some docu people can’t use FCPx because they need multi editor workflows as Mark pointed out.

    But I said it is my story, not yours or anybodies else’s.

    Now you have to excuse me because I need to upload another Youtube video before I join my mates at our retirement home annual wheelchair party 🙂

  • James Mortner

    May 3, 2012 at 12:12 pm

    [TImothy Auld] “I could not even begin to trust X in a situation like that.”

    Yes, after reading some horror stories Im quite happy to let others do the beata testing for me !

Page 2 of 14

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