Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Creative Community Conversations Is FCPX development slower than you’d like?

  • Is FCPX development slower than you’d like?

    Posted by Steve Connor on October 30, 2014 at 11:13 am

    Considering how fast Resolve and PPro are evolving, I have to say I’m a little disappointed that the pace of FCPX development seems to be slowing. I know Bill will say it’s great as it is and that is true in some respects, but if I’m honest I thought that we’d see a lot more features added.

    Robin S. kurz replied 11 years, 7 months ago 15 Members · 32 Replies
  • 32 Replies
  • Simon Ubsdell

    October 30, 2014 at 11:51 am

    If you think the pace of development has slowed for FCP X, spare a thought for the pace of development of Motion, where Apple have moved over to geological time frames 😉

    Simon Ubsdell
    tokyo-uk.com

  • Michael Phillips

    October 30, 2014 at 12:54 pm

    Do you think that Motion becomes part of FCPx at some point, and one might think (hope) that the lack of standalone development is about integration development?

    On a similar note, you just have to think that Blackmagic will be integrating Eyeon Fusion into Resolve at some point in the future, and Fusion has some great graphics functionality – not to mention compositing, etc.

    Michael

  • Bret Williams

    October 30, 2014 at 2:21 pm

    Why not throw HitFilm 3 into the mix? It’s basically a little inexpensive Smoke.

    I’d agree it has slowed to a crawl. Other than a few niceties, there was nothing last year. Just file management. And before that, a year ago, we were having this exact same conversation.

    With Motion, sure they’re could be some high end stuff added, but I’m not making use of what all has to offer as it is. Kinda like PS, AE, Illustrator and such. I haven’t really outgrown the likes of my old CS5 versions.

    The biggest problem with FCP X: It has increasingly with every version become a resource hog. Get a free memory meter and watch it just eat the memory. Just scrubbing potential effects in the browser will eventually do it. But it’ll start to lag way before memory is gobbled up. There are some serious resource management issues here. It needs some sort of internal overhaul. Bill can love it all he wants. But when you ask it to actually do something other than logging and cuts and dissolves, it really sucks in performance.

  • Mark Suszko

    October 30, 2014 at 3:28 pm

    I think what we see with FCPX is that the way forward is externally developed modular plug-ins that hook into a central app framework, rather than Apple re-building the underlying code from scratch every time they upgrade. This is the fastest way to get more new functions added as demand drives them. The burden on the FCPX dev team then is to keep it all working in harmony.

  • Jeremy Garchow

    October 30, 2014 at 4:16 pm

    I have a feeling that Yosemite will bring a lot of functionality. It has been a long wait, to be sure. Apple seems to be building a pretty big framework in order to hang third party development off of it. It is taking a while to get there, but I think it’s getting there. I also think Apple still has a few tricks up their sleeves as well.

    https://www.youtube.com/watch?v=21zy13JsCYA

    I have been having a lot of fun in fcpx, more fun than any other NLE I’ve used in the past. Our office has switched to 10.1.3 almost exclusively. I finally feel comfortable enough with the Library system to start and maintain an archive of past projects, and 10.1.3 has been as stable as fcpx has ever been.

    Simon is making some wicked plugins, Hawaki Style is a real blast, and I don’t find X to be a resource hog, but I am editing on a tube with mostly ProRes/XAVC iFrame material. Even editing on a laptop is surprisingly good. I can get a whole lot of work done inside of fcpx that I wouldn’t do in 7 or any other NLE without another application or two.

    Apple has a lot of irons in the fire these days. I’m not sure my best interests and their best interests are as aligned as they once were, but that’s the way it goes.

    Pr CC is sitting on our machines waiting to be used if the need arises.

    Of course I’d like some more updates, and I’d really like some UI tweaks, but all in good time.

    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.

  • Bret Williams

    October 30, 2014 at 4:24 pm

    [Jeremy Garchow] “Simon is making some wicked plugins, Hawaki Style is a real blast, and I don’t find X to be a resource hog, but I am editing on a tube with mostly ProRes/XAVC iFrame material.”

    Seriously there must be something horribly wrong with my system then. And many others. I have the top o the line 2012 27″ imac with 32gigs. Upon boot there are 26 gigs available. Launch X and there’s 24-25. Seems pretty good. But then browse some of Simon’s effects like mLogo or heaven forbid some mobject templates from the broswer and suddenly you’re dropping gigs of available RAM as fast as the app is bogging down. And if you put a motion template in the timeline and adjust, scrub etc it’s the same issue. Suddenly your available RAM is being calculate in megs instead of gigs. And that’s with one app open, FCP X. It needs a memory top off amount. To leave memory for other apps. Or to ditch memory when appropriate like when an app is launched. That’s how it’s supposed to work. But X doesn’t let go of memory until you quit. And it’ll keep grabbing it until – crash.

  • Bret Williams

    October 30, 2014 at 4:27 pm

    Don’t claim to be an expert, but it seems everything is tying into the built in Motion framework, which is tying into FCP X. So sometimes you have an app (mflare, mobject, etc) running on top of a full copy of motion, on top of a full copy of FCP X.

    Maybe FCP X development isn’t slower than I’d like, but just FCP X is slower than I’d like.

  • Simon Ubsdell

    October 30, 2014 at 5:05 pm

    [Bret Williams] “But then browse some of Simon’s effects like mLogo or heaven forbid some mobject templates from the broswer and suddenly you’re dropping gigs of available RAM as fast as the app is bogging down.”

    Hi Bret

    I’m afraid you’ve got me mixed up with the Szimon (sp?) who runs motionVFX. I have nothing to do with mObject or mLogo or any of their products or the company. They make terrific products and you should take up the performance issue with them as I’m sure they’d like to hear your concerns.

    You can find my plug-ins at Hawaiki or Tokyo.

    You should also check out my Motion Tutorials if you have a moment – they are quite good, at least in the opinion of quite a few of my subscribers.

    Simon Ubsdell
    tokyo-uk.com

  • Simon Ubsdell

    October 30, 2014 at 5:10 pm

    So just for clarification these are the details of the team at motionVFX:

    https://www.motionvfx.com/about_us.html

    Who is motionVFX?

    MotionVFX is a registered trademark of a company called MotionVFX, which is created and owned by Szymon Masiak.
    Szymon is very well known in computer graphic industry and has been working in it for over 20 years in areas like computer games, commercials and major motion pictures.

    MotionVFX is based in Poland and here is full address and the name of our company:

    MotionVFX Szymon Masiak
    Bielska 11
    43-340 Kozy
    Poland

    You may contact us via our official Support Channel at support (at) motionvfx.com

    (PS. I have never been to Poland, though I would like to some day …)

    Simon Ubsdell
    tokyo-uk.com

  • Bret Williams

    October 30, 2014 at 5:12 pm

    I thought Jeremy was referring to Szymon. I never spell it right either. But looking back he was referring to you. But the point is the same. All these people making cool stuff. But it all seems to suck up the RAM. Any thoughts on performance? AE sucks up RAM too just with RAM previews alone, but they have a nice little purge function that I use constantly.

    I have watched some of your tuts. You’re a Motion genius. One was way over my head. The one about green screen in motion by subtracting this channel from that…. way above my pay grade. I was having trouble with a key at the time but keylight came to the rescue in AE as it usually does.

Page 1 of 4

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