Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Creative Community Conversations Issues with FCPX, mac dustbin and anecdotal resolution

  • Issues with FCPX, mac dustbin and anecdotal resolution

    Posted by Julian Bowman on April 16, 2014 at 4:40 pm

    So, I had really bad performance issues with FCPX on my new mac dustbin. I have posted here about it. I took the machine into the Apple store and they did a base level scan and said it seemed fine. I also had a chat with a lad who made some suggestions etc. with regards to trouble shooting and seeing if it is a plugin conflict.

    I haven’t had any time to test it so have been soldiering on.

    yesterday I went to export an edit and everytime I tried FCPX crashed. Then I tried rendering, same thing. I then deleted the text plugin I had used, one I owned but had never used before, and everything was fine.

    It was made by Pixel Film Studios, a company I am not overly enamoured with after the ripping off of motionvfx event and mainly because they seem to release a lot of rather poor plugins (look good in the trailer, reality is they aren’t). So I deleted every plugin I had installed by them, and although I haven’t had the time to test old projects I really struggled with, simply using FCPX seems much quicker and slicker already.

    So, currently it is only anecdotal and I will do a fuller test, but deleting their plugins definitely makes everything feel a lot better inside the app.

    Just thought I’d share in case others are having issues with FCPX and have Pixel plugins installed.

    Julian Bowman replied 12 years ago 9 Members · 21 Replies
  • 21 Replies
  • Mathieu Ghekiere

    April 16, 2014 at 6:54 pm

    Good to know, thanks!

    We sometimes have performance issues, and I think we have one plug-in from them. I’m not a fan of the company because of the same reasons you posted, but they had a plug-in that seemed worthwile for our work. Haven’t tested it, but thanks for the update.

  • John Davidson

    April 16, 2014 at 7:49 pm

    And that’s why I avoid FX Factory and most 3rd party plugins as well. You just don’t know what’s going on under the hood.

    Great example was just this week – we’re doing an update to our FCPX On Air series and I couldn’t get screen recording to work via QuickTime. This was a problem that had gone on for months and I wrote it off to a Mavericks issue. Then I updated my Blackmagic Drivers and suddenly Screen Recording worked again.

    It’s a challenge because FCPX needs 3rd parties for lots of things, but when they can’t control what the 3rd parties do it opens the door for lots of issues. At least Apps (like X2Pro) don’t screw up FCPX because of the whole sandboxing thing.

    John Davidson | President / Creative Director | Magic Feather Inc.

  • Michael Gissing

    April 17, 2014 at 12:05 am

    I did go on record years ago saying I had reservations about excessive need for third parties to do basic functions. My recent FCPX job threw up some issues with getting audio out.

    Getting pictures in Resolve was fine on the way in but returning to X was an issue as I had to render the grades to my internal drive and then dump the folder onto the external. X just couldn’t reconnect until the editor opened the project in Resolve at his end and it reconnected. He then made an new xml and this time X was fine.

    So still I have concerns about third party round tripping for normal workflows that include post facilities.

  • Charlie Austin

    April 17, 2014 at 1:25 am

    [John Davidson] “And that’s why I avoid FX Factory and most 3rd party plugins as well. You just don’t know what’s going on under the hood.”

    Me too, though I did just install fxfactory to use one specific plugin. First thing i did was disable everything. Then I DL’s the single one I needed. 😉

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

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

  • Jeremy Garchow

    April 17, 2014 at 1:25 am

    How is X to Resolve to X a third party workflow? It’s all FCPXML, no?

  • Michael Gissing

    April 17, 2014 at 2:12 am

    Jeremy it was xto7 for the audio. Dogs breakfast. Clips that should have been enabled were disabled. Clips were not organised by roles into sensible tracks. Music tracks had to be refitted – wouldn’t connect. X – Xto7 – FCP7 – OMF to Fairlight. Far too many steps.

    Then X to Resolve and back to X for pictures via FCPXml. On the return X couldn’t reconnect to the grade files without a fiddle to reconnect in the editors Resolve and make another xml. However the discussion of third parties is more to do with needing outside software to do the basics of audio export.

    After two years it continues to be a cludge. And I was reacting to the topic of this thread that sometimes third party plugin software can have a detrimental effect on the primary NLE software. Tight integration with developers is needed but not particularly something Apple is known for.

    If Resolve 11 is as good an edit/ finishing tool as it seems to be then I expect every editor to get their project into R11 first to deliver to me. I would be happy if R11 is the only step from every NLE into post finishing and no round trip returning. Lets see if they put OMF/AAF export in R11.It isn’t rocket science.

    Meanwhile I am talking to Fairlight about reading FCPXmls directly like they did with FCP7. Apple may think they can ignore industry standard interchange formats and develop yet another but it hardly makes me respect them and the years of grief.

  • Kevin Rag

    April 17, 2014 at 4:06 am

    Oh darn! I just had my eyes set on the SliceX/Track X bundle:(
    Probably won’t buy it for now.

    Kannan Raghavan
    The Big Toad Films Pte. Ltd.

  • Charlie Austin

    April 17, 2014 at 4:11 am

    [Kannan Raghavan] “Oh darn! I just had my eyes set on the SliceX/Track X bundle:(
    Probably won’t buy it for now.”

    Totally different company. CoreMelt plugins work great, and they are super responsive if one does have issues. 🙂

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

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

  • Michael Gissing

    April 17, 2014 at 4:19 am

    I should clarify that although Resolve 10 does have AAF export already it is the whole timeline, picture and sound. I am talking about options to consolidate with handles and do Vid, audio or any combination rather than a no option AAF of everything.

    So they are closer already than FCPX.

  • David Mathis

    April 17, 2014 at 4:49 am

    I have purchased a few FX Factory plug-ins but have not ran into real issues with one exception. I ran an update but kept getting an error message. Did a clean install from the ground up and the update worked with no further issues. This was back on Mountain Lion, and a software update to the OS was probably corrupted causing the issue.

    I did contact customer support and they were very helpful. I do not remember who I talked to but they gave really great support.

Page 1 of 3

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