Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Creative Community Conversations still driving me nuts

  • James Culbertson

    June 2, 2015 at 11:59 pm

    [Jeremy Garchow]
    The word Project has never ever ever not once, caused any modicum of confusion.

    As a matter of fact, because of the ease of Roles, getting organized for finish is very easy with X.

    Also, I don’t experience the performance issues you are experiencing. What computer are you on?”

    My experience too. It may be the case that the colorists and audio post folks I work with talk about how immature FCPX’s nomenclature is, but they also have no issues with what I send them and the process is as smooth as any I have encountered with other NLEs.

    Editing is smooth as silk on a new MacPro and new MacBookPro.

  • Andy Neil

    June 3, 2015 at 12:08 am

    [Mike Warmels] “And trimming: you don’t have to select. I have my smart tool of trimming always ON… and then it just click with the CTRL and you can trim by hand immediately. If you want to do it differently, go to trimming mode. AVID allow for several methods.”

    I was responding to you specifically comparing FCPX trim using keyboard shortcuts versus using Avid with keyboard shortcuts.

    If you’re talking mouse controls, then you can trim by just clicking the audio or video edge and either drag or use keyboard shortcuts. Same number of steps. You work with smart trim tool always active? You can work with all audio expanded in X if you like. Instant access to your audio tracks.

    I’m never going to suggest that X has as good trimming tools as Avid, it obviously doesn’t. But it’s just as easy to make the kind of split edit trims you’re talking about. I see no measurable difference in editing time.

    As far as your waveform workaround, it’s just that. A workaround. I don’t want to have to mark INs/OUTs to view waveforms. And I don’t want it to have to redraw the damn things every time I resize my timeline view. FCPX draws waveforms faster, and they react to changes, and it just works better.

    And I don’t see the slow downs you’re experiencing. Not since the 10.0… versions. FCPX works snappy for hours. The only lag I get is if I’m editing with a large number of multiclips up or editing with the inspector open. Is your Avid system on the same computer as your FCPX or are we talking two separate computers?

    Andy

    https://plus.google.com/u/0/107277729326633563425/videos

  • Neil Goodman

    June 3, 2015 at 12:17 am

    [Andy Neil] “As far as your waveform workaround, it’s just that. A workaround. I don’t want to have to mark INs/OUTs to view waveforms. And I don’t want it to have to redraw the damn things every time I resize my timeline view. FCPX draws waveforms faster, and they react to changes, and it just works better. “

    Avid caches the wave-forms now since version 7. I never have to redraw FWIW.

  • David Lawrence

    June 3, 2015 at 1:25 am

    [Oliver Peters] “You’ll note the word Timeline is capitalized and it says “in”, referring to the pane and not the edited sequence/project. So basically anything you do in that pane is the Timeline. The thing you create is the project.”

    Also note this language:

    “When you create a new library it auto creates an event but no timeline (project).”

    Timeline (project).

    Even Apple can’t keep it straight. It’s an embarrassment, really.

    I look forward to Jeremy’s post when he gets around to it (no rush), but I’m deeply skeptical Apple thought this language through. It’s just stupid and unnecessary.

    _______________________
    David Lawrence
    art~media~design~research
    propaganda.com
    publicmattersgroup.com
    https://lnkd.in/Cfz92F
    facebook.com/dlawrence
    twitter.com/dhl
    vimeo.com/dlawrence/albums

  • Oliver Peters

    June 3, 2015 at 1:36 am

    “I look forward to Jeremy’s post when he gets around to it (no rush), but I’m deeply skeptical Apple thought this language through. It’s just stupid and unnecessary.”

    I still contend that they simply used terminology that was consistent with other Apple software. I think way more thought has been given to it here in this forum than in the halls of Cupertino.

    Oliver

    Oliver Peters Post Production Services, LLC
    Orlando, FL
    http://www.oliverpeters.com

  • Jeremy Garchow

    June 3, 2015 at 1:50 am

    [Oliver Peters] “”I look forward to Jeremy’s post when he gets around to it (no rush), but I’m deeply skeptical Apple thought this language through. It’s just stupid and unnecessary.”

    I still contend that they simply used terminology that was consistent with other Apple software. I think way more thought has been given to it here in this forum than in the halls of Cupertino.”

    It very well could be that simple, but it is no where near as fun.

    I do think some thought was given to it, to what a Project means and why it’s more than a timeline.

    Even if Apple didn’t think it through (although I don’t think that Apple is the type of company to not think anything through, that is to say, they think it through even if it involves risk and failure) but even if they didn’t, I still think the name has a bit of merit.

  • David Lawrence

    June 3, 2015 at 1:51 am

    [Oliver Peters] “I still contend that they simply used terminology that was consistent with other Apple software.”

    Yep, that’s the only explanation that makes any sense. Still wrong though! 😉

    [Oliver Peters] “I think way more thought has been given to it here in this forum than in the halls of Cupertino.”

    I completely agree!

    _______________________
    David Lawrence
    art~media~design~research
    propaganda.com
    publicmattersgroup.com
    https://lnkd.in/Cfz92F
    facebook.com/dlawrence
    twitter.com/dhl
    vimeo.com/dlawrence/albums

  • Bill Davis

    June 3, 2015 at 5:06 am

    [Oliver Peters]
    So standards, best practices and terminology are very important and something Apple too easily casts aside. Speaking of which, how long do you think you can count on Thunderbolt being around?

    – Oliver

    Actually, since Intel announced that USB 3 and Thunderbolt will be connector and protocol compatible going forward, likely a very, very long time.

    Know someone who teaches video editing in elementary school, high school or college? Tell them to check out http://www.StartEditingNow.com – video editing curriculum complete with licensed practice content.

  • Andrew Kimery

    June 3, 2015 at 5:11 am

    [David Lawrence] “[Oliver Peters] “I think way more thought has been given to it here in this forum than in the halls of Cupertino.”

    I completely agree!”

    88 replies and counting!

  • Mike Warmels

    June 3, 2015 at 6:59 am

    I work on a brand new MacPro, 6 core, D700 graphics card and 48GB of RAM. That should suffice, I would say.

    But it’s not just me. There are two editing facility houses that I work with and they to have this issue that FCPX slows down after 1-2 hours of editing. Maybe we’re working too fast on it or something. 😉

    And yes, I run the AVID and FCPX on the same computer. And to be honest, waveforms build really quickly on this machine in AVID. I just use the other method (or work around as you would have it) because I kinda like that I can see them when I need them.

    But to be honest, I think FCPX is Work Around Central. In general I run into some very weird stuff. Some examples

    1.Reveal in browser (a favourite option of mine in all NLE’s – others call it Match Frame). I press reveal in browser (for which I have to select the clip first) and the browser opens up, needs time to load everything and for the waveforms (takes a little time). But then… I can’t directly see the clip I wanted revealed. So I press ‘reveal in browser’ again and then it goes to the particular clip. Again: it’s slowish and I need to reveal it twice…
    2. Using XD-CAM stuff (or any MXF material like footage from the Canon C300). For some reason you can’t import this. I looked this up and what I found is that Apple wants you to use XD-CAM material als native. So it cannot import it and convert it to Apple Pro Res. But… when handling non-Apple Pro Res footage, FCPX uses only one of your cores… And then I think: WHAAT? I thought this was a 64 bit machine? Why can’t I use it now as it should.
    3. Export (or “Share” – rolls eyes 😉 ). Exporting to different codecs is limited. You need Compressor to make a HUGE work around, but Compressor is a really outdated program. Plus the hassle of making profiles in one program and then importing that in FCPX is downright silly. FCP7 didn’t have that, AVID or Premiere don’t have that. IT’s silly. So I now make an export and use my trusted old Quicktime7 to convert it to the size I want. And this is something I use a lot to get viewing versions out of the door.
    4. Keyword are great. I think that works very nice. But what I don’t get is why the browser sorts everything on date or something else I don’t need. For instance, I am using lots of music sorted by kind. Say “funky”. So I have like 50 track of funky music. But I have only two options to see them: as blocks with waveforms or as a list sorted bij date folders… I can’t see just the list. I have to open all these folders, or minimise the clip browser where I see them al. Why can’t I just see the list of tracks??

    It’s a lot of these things. And as I said: it works, it has some very powerful tools, there’s a certain elegance…. but it is extremely clumsy on other counts. And to me it says: FCPX is immature… it’s an adolescent at best.

    Now, AVID may be a bit of an old geezer. But in my kind of work I prefer AVID for a few reasons:
    1. The mediamanagement system is great. Yes, you have to digitise your footage first to make it work, but then: you have to transfer everything to Apple Pro Res for FCPX as well to really benefit from it.
    But AVID’s mediamanagement system makes the media work very direct plus a lot of effects and stuff are real time in the sense that it either is really REAL time or doesn’t stutter, like FCPX does when effects ae involved.
    2. It works great with color grading, audio mixing studios. The export features are excellent.
    3. The ISIS network system when working in a larger facility works very well and is very solid. The SAN system you need voor FCPX is… well… not entirely developed.

    To make sure, AVID isn’t perfect. It has it s quirks. But so has any NLE I have worked on or with. the major redeeming factor for FCPX is it price: you get a lot of money worth. But my main point is that I don’t really understand why the ‘new paradigm’ was necessary, what it added to workflow for professionals (so far)… but I can see it suits the need something that looks like could actually work on a iPad kind of device: it looks modern.

    But if FCPX was priced like AVID used to be, I’d wonder if people would bother all the hassle.

Page 9 of 29

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