Forum Replies Created

Page 29 of 51
  • Ronny Courtens

    October 25, 2013 at 8:14 pm in reply to: Development

    Was FCPX based on iMovie? No. Is the new iMovie based on FCPX? Absolutely yes.
    The new iMovie X is getting much closer now to FCPX than ever before. I now call it FCPXpress (-:

    If you play around with it you even discover some things that some of us have been asking for FCPX (this little list is from TPayton + some by me):

    – Rethought UI – Flatter, square corners, less depth on timeline.
    – No more separate „Projects” folders. Project files reside in the Events folders.
    – Individual import progress indicators in the Event for clips that are being imported.
    – “Used Media” range markers on clips in Event.
    – Greatly improved performance (scrolling filmstrips)
    – Titles based on Motion templates (some are the same as in X)
    – Blazing fast Motion Template performance (iMovie X is monumentally faster at editing titles than current FCPX)
    – Notifications after completed exports
    – Video fade-in fade-out handles
    – Length indicators for handles
    – An extra audio track (yes, a track) that is not connected to the Storyline

    It runs on the same Framework as FCPX, you can share templates between them, it has the same (but simplified) retiming and stabilization features, etc…

    I have found it quite performant, playing three layers (PIP) of non-optimized 1080p30 MPEG4 with effects and titles on top in realtime and without any hiccups… on the most basic Mini with 2 GB RAM.

    Here’s an iMovieX timeline:

    – Ronny

  • Yes App Nap stops FCPX from transcoding after a certain time.

    Go to your Applications folder, R-click on the FCPCX inch and select Show Info. Top of the Info window you will find a checkbox that allows you to deactivate App Nap for FCPX. When you have done this FCPC will never go to sleep anymore unless you want it.

    – Ronny

  • Ronny Courtens

    October 25, 2013 at 4:55 am in reply to: Render files strategy

    The best way for saving drive space is of course to not include render files on duplicates, and even delete any render files as soon as a Project has been exported. As you say: you can always re-render whenever you need to rework a Project again.

    If you wish to preserve your render files for whatever reason you can slim down the size of your Render folder by just deleting the unused render files. In many cases this makes a real difference, especially if you have been rendering the same effects over and over again.

    – Ronny

  • [Craig Shamwell] “Oliver you said a couple of good things about X, but almost in every breath you “take it back” with a remark like the one above”

    Oliver does this with any software he talks about, not only with FCPX. That’s why I respect his opinion. And I am a huge fan of FCPX. Just like any other NLE it has its weak spots, and only by exposing them can we influence Apple to make the app even better.

    – Ronny

  • Ronny Courtens

    October 22, 2013 at 6:41 pm in reply to: New Mac Pro AND a FCP-X shout out. Happy now?

    Actually Schiller did mention the new version of FCPX when he talked about the MacPro. It will be released in December, together with the new MP.

    – Ronny

  • Ronny Courtens

    October 22, 2013 at 2:18 pm in reply to: Apple Announcement today

    I think the will be streaming it live:

    https://www.apple.com/apple-events/october-2013/

    – Ronny

  • If you see your face appearing here and you don’t want it to, just click on your photo and select Remove. You have full control over this.

    – Ronny

  • Ronny Courtens

    October 20, 2013 at 2:29 pm in reply to: A Bug?

    Agreed. I have tried to reproduce this issue with a still on the Primary, with an adjustment layer over a still, with anything I can think of, and all of these things seem to work correctly. So this seems to be related to a specific issue on your system. Try the suggestions above and please keep us posted, this is interesting to know.

    – Ronny

  • The guy says about FCPX (quote) “the times I’ve used it have been few and far between.”

    Is this the same guy who is listed as a Cow Master in the FCPX Techniques forum? LMAO!!

    – Ronny

  • Ronny Courtens

    October 19, 2013 at 8:59 am in reply to: A Bug?

    I have tried to reproduce this.

    Here you have a clip on the Primary with some Transform and Crop (Trim) keyframes as well as some audio keyframes applied to it, and a connected clip above the Primary:

    When I disable (V) the connected clip all keyframes in the clip on the Primary stay intact:

    When I enable the connected clip again all keyframes in the Primary clip are still intact.

    Of course your setup may be totally different, but this little test seems to work. If you would like me to do some other tests, no problem.

    – Ronny

Page 29 of 51

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