Forum Replies Created

Page 1 of 3
  • Steve Mcgarrigle

    October 29, 2016 at 8:10 pm in reply to: MacOs Snow Leopard FCP6 – wtf?

    I have a copy of FCP 6.0.6 that I can confirm works just fine on Sierra 10.12.1.
    I have absolutely no interest in using it anymore though as it really does feel old, slow and clunky compared to FCPX or PP.

  • Steve Mcgarrigle

    October 10, 2014 at 10:53 am in reply to: Cutting a major Hollywood Feature on FCPX

    A teaser trailer for Focus has just been released. Here’s a link:https://youtu.be/A1PqBFHoeTA

    Some contents or functionalities here are not available due to your cookie preferences!

    This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.

  • Check out the Digital Anarchy – ‘Flicker Free’ plug-in if you haven’t already – you did post this a little while ago so you may already be aware of this.

  • Steve Mcgarrigle

    December 19, 2013 at 8:26 pm in reply to: er, is that it?

    Yeah – you’ve kinda got a point there. Now that the dust is settling and I’m looking down the list of new features have to agree with you. I thought The playhead and audio features would be there for sure. There was enough people making enough noise about this surely to have got noticed.
    My opinion is they messed up real bad with the initial release of FCPX – i mean we know they did right? but further down the road i think they realised that the fundamental underlying structure and foundations of FCPX just weren’t adequate. It was essentially “A house built on sand’ – prone to corruption and “not ready for prime time” consequently it would seem they have had to spend all of there time rewriting the organisational structural basics yet again instead of implementing all the stuff users actually wanted.

  • With no manufacturing costs as in the old days with disks and boxes and printing i guess they only need to claw back the development costs to break even. I suspect FCPX is seen at least in part as a marketing tool to drive people to buy the new MacPros and to a lesser extent maybe macbook Pros. Hardware is where the money is for Apple and the current push is “get yourself a new machine to power that future 4K production!”.

  • Steve Mcgarrigle

    November 14, 2013 at 9:37 am in reply to: Don’t mess with compound clips after 2am

    Absolutely – i couldn’t agree more.

  • Steve Mcgarrigle

    November 10, 2013 at 2:36 pm in reply to: Final Cut 6 and Mavericks

    What is this image tearing of which you speak?
    I haven’t experienced this. When did it start?

  • Steve Mcgarrigle

    October 29, 2013 at 5:39 pm in reply to: OSX ProApps Codec “Update” Kills our QuickTime

    Do you have Time Machine back ups or the earlier codecs package on a different non updated machine?
    Maybe you could manually remove the updated codecs from their folder by simply dragging them to the trash or keeping them somewhere where they wont be a nuisance and replace them with the earlier versions?

    Just an idea.

  • Steve Mcgarrigle

    October 26, 2013 at 10:27 am in reply to: Final Cut 6 and Mavericks

    Hi Shane,

    I have just updated my ageing 2009 Mac Book Pro to Mavericks.
    As it goes i have an old install of Final Cut Studio 2 on there.
    I am pleased to tell you that FCP6 does in fact work fine although some of the plug ins did not.
    After updating and on first launching the application it would hang while attempting to load Boris Continuum Shaders making it then “Quit Suddenly” while still on the loading splash screen.
    After uninstalling BCS plug ins however it all now works fine.
    I haven’t tested it thoroughly as i don’t really use it anymore, however just for you and in the name of science i opened up a pre existing project, made a new sequence, set in and out points on some footage, dragged it to the timeline. Bladed it, trimmed it, added a cross dissolve, rendered some colour correction and exported a ProRes 422 Quicktime successfully, all of which is fairly conclusive i would say.

    There you go!

    Steve.

  • If it’s afile size issue – remember that Compressor gives you the estimated file size as a calculation in the inspector when you are making your settings. As for what those settings should be? That depends on the files end purpose.

Page 1 of 3

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