Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Creative Community Conversations 10.3.2 Is out – WOW review from a huge X facility in Europe.

  • Ronny Courtens

    January 22, 2017 at 7:57 pm

    Allow me to put some things in the right perspective.

    I can understand Mads’ enthusiastic reaction to this update. It solves an issue for them that has been around since day 1 and that typically affected very complex timelines with tons of stacked connected clips. Obviously, the longer the timeline the more the problem was apparent. We have reported this issue, even sending complete projects with media over to Apple. I can only guess why it has taken until now to see a solution. Probably because the root of the issue required some changes in the fundamentals of FCP X which were completed with 10.3, but also because the problem was only really apparent with very specific types of productions and not with long-form projects in general.

    Metronome has gone from 3 FCP X seats in 2012 to 50+ seats now (at the expense of Avid), and the “drag-lag” issue as we started calling it has not stopped them from delivering over 300 hours of content each year. This means they have always been ABLE to do their work, but not in the best circumstances.

    A few months ago another major production company started complaining about the issue. They sent us their projects and we noticed their timelines (long-form docs with loads of stacked titles, graphics and connected multichannel audio) were very similar to the ones we saw from Metronome. So I started calling everyone in Europe who works on long-form with FCP X to ask if they had similar issues. Only a few of the 50 companies I called confirmed that they did experience the drag-lag issue in the same way as the guys from Metronome. I guess that’s why Mads says that “many would argue that the problem does not exist”. So I asked everyone who had problems to send their projects to Apple, and apparently this has resulted in getting the issue on the priority list. I got confirmation from all of them now that the new update has indeed solved the problem for them. All is well that ends well, up to the next update.

    – Ronny

  • Oliver Peters

    January 22, 2017 at 11:51 pm

    [Ronny Courtens] “Allow me to put some things in the right perspective.”

    Thanks for a very clear explanation.

    – Oliver

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

  • Tim Wilson

    January 23, 2017 at 12:07 am

    [Oliver Peters] “[Ronny Courtens] “Allow me to put some things in the right perspective.”

    Thanks for a very clear explanation.”

    My thanks also, Ronny!

    Best,
    Tim

  • Bill Davis

    January 23, 2017 at 3:43 am

    [Andrew Kimery] “(and don’t complain even more when your hypocrisy gets pointed out). Just own your actions and go with it.”

    Hypocrisy?

    Good god, man – all I did was post a link to a high end facility editors direct experience with the tool this entire forum is supposedly about!

    It wasn’t me leading the brigade of – “yeah, but look at all the other stuff that still sucks about X.

    It’s like the forum is just loaded with participants deathly afraid that this thing will keep improving.

    Hint: if advancements in X make you crazy – don’t freaking use it.

    But it’s not OK in my book to have to turn a forum ABOUT FCP X into a place specifically hostile to it. Not when it works perfectly well for millions of editors.

    I’ve already long since stopped inviting some of the brightest folks using it to stop by to discuss it in this forum – because the ones that I did just didn’t want to waste their time with the constant bitching and negativity here.

    If it’s what the Cow wants – a Final Cut Pro X forum where every single positive comment about it must be aggressively challenged by default – well,good luck with that.

    Creator of XinTwo – https://www.xintwo.com
    The shortest path to FCP X mastery.

  • Andy Patterson

    January 23, 2017 at 5:39 am

    [Bill Davis] “But it’s not OK in my book to have to turn a forum ABOUT FCP X into a place specifically hostile to it. Not when it works perfectly well for millions of editors.”

    I don’t see hostile people. Having said that this form is about debating the merits of FCPX compared to other NLEs. The forum functions as it should, not as you would like. If you don’t want to hear comments and criticisms about FCPX and other NLEs this is not the forum for you. Having said that I posted a link below to the forum dedicated to FCPX editors that use it.

    https://forums.creativecow.net/fcpx

    [Bill Davis] “I’ve already long since stopped inviting some of the brightest folks using it to stop by to discuss it in this forum – because the ones that I did just didn’t want to waste their time with the constant bitching and negativity here.”

    Once again this is a forum to discuss the merits of FCPX and other NLE. If they want to go to the FCPX forum the link is below.

    https://forums.creativecow.net/fcpx

    [Bill Davis] “If it’s what the Cow wants – a Final Cut Pro X forum where every single positive comment about it must be aggressively challenged by default – well,good luck with that.”

    I think perhaps you do live in an alternate universe with pixies and unicorns as others have suggested. Having said that some could argue that you want this forum to be a place where all editors (Avid, Edius, Premiere) praise, honor and worship FCPX. That is not the purpose of this forum. I now you wish it was but once again the link below might do you some good.

    https://forums.creativecow.net/fcpx

  • Andrew Kimery

    January 23, 2017 at 6:55 am

    [Bill Davis] “Good god, man – all I did was post a link to a high end facility editors direct experience with the tool this entire forum is supposedly about!

    This side discussion isn’t about your original post and you know it. As previously stated, it’s about the hypocrisy of complaining that other people do XYZ while also choosing to do XYZ.

    [Bill Davis] “It wasn’t me leading the brigade of – “yeah, but look at all the other stuff that still sucks about X.”

    But you willfully participate and perpetuate those types of exchanges because, and I quote, “When you have a sword swung AT you enough – it’s traditional to learn to parry and swing one right back.”

    Revisiting my previous example, when Walter mentioned how Premiere has integration with stock photo libraries to help automate that process you replied with a comment about Adobe seemingly taking an unduly high percentage of each stock footage sale. It’s a completely out of left field dig at Adobe. It would be you saying “Hey, aren’t these new Lanes in X great?” and me replying, “I guess so… but don’t you think it’s unfair that Apple pays the workers that assemble iPhones in China so little?”

    [Bill Davis] “If it’s what the Cow wants – a Final Cut Pro X forum where every single positive comment about it must be aggressively challenged by default – well,good luck with that.”

    I think this is where Tim pops in and mentions all the traffic this place gets…

    I really can’t think of any place I’ve been where the relative merits of so many NLEs are broken down on a regular basis than here. There are plenty of forums, Facebook groups, mailing lists, etc., which all cater to their respective user/fan bases, but for critical thinking across the board I’m not aware of any other place like this forum.

  • Walter Soyka

    January 24, 2017 at 3:09 am

    Bill, sorry I missed this before.

    [Bill Davis] “How do they handle the asset management stuff without something like Roles in operation?”

    Metadata:
    https://helpx.adobe.com/premiere-pro/using/metadata.html

    Adobe’s XMP metadata platform is extensive. (It’s also an open technology and I think it would be very cool if Apple had used XMP as the basis for FCPX’s metadata management.)

    [Bill Davis] “How does the Adobe ecosystem manage which clips are embedded in the projects? Is it this handled by the “panels” thing?”

    I’m afraid I don’t understand the question. Premiere Pro (like all NLEs) uses a relational database under the hood, but I don’t really understand what you’re asking here. If you can re-state the question a different way, maybe I’ll understand better and then I could answer.

    Here’s the best layman’s description of the CEP panel architecture I could find:
    https://blogs.adobe.com/creativecloud/adobe-cep-extensions-and-developing-add-ons-for-audition/

    Walter Soyka
    Designer & Mad Scientist at Keen Live [link]
    Motion Graphics, Widescreen Events, Presentation Design, and Consulting
    @keenlive   |   RenderBreak [blog]   |   Profile [LinkedIn]

  • Robin S. kurz

    January 25, 2017 at 3:11 pm

    [David Mathis] “but still no out of sync indicators.”

    And don’t hold your breath, seeing that they are of zero relevance in X.

    Unless of course you can outline any situation or task in FCP X where you haven’t simply done something completely unnecessary to your synced audio to equally unnecessarily cause the asynchronous result to begin with. Anything where the proposed sync indicators could be of global and practical use, as opposed to simply switching to a more sensible, existing workflow alternative to whatever it is you’re doing. Something that can somehow make the obvious point that shows why sync indicators could in fact be considered a constructive improvement or necessity. Including for every other X user that has actually understood the most basic concepts of how X works and not just for making the lives of those easier that are just ignorant of certain workflows (and unwilling to learn/adapt). The latter, from my experience, being the only ones that ever felt synch indicators could actually make any sense. And always for mere familiarity reasons, not out of objective necessity. So yes, I’d truly be very curious what that task or situation could be.

    I’ve asked that every time I see that come up, too, and to date not once actually gotten an answer that didn’t simply describe the above. Or I just simply got the ol’ “Because I need them. Period.” response as their only logical justification (much like it seems to be the case here once again?). Or no response at all. At least I haven’t seen any practical explanations as to why we should be hoping for them. But maybe I just overlooked them? Or could this be a first? ????

    – RK

  • Robin S. kurz

    January 25, 2017 at 3:18 pm

    [Steve Connor] “Kudos to Apple though for the recent pace of FCPX updates, really inspires confidence in the future”

    So the, until now, mere 3 to max 4 months (with one exception) between updates, i.e. over 20 in just five years weren’t enough for that already? Wow. Okay.

    – RK

    ____________________________________________________
    Deutsch? Hier gibt es ein umfassendes FCP X Training für dich!

  • Steve Connor

    January 25, 2017 at 4:03 pm

    [Robin S. Kurz] “So the, until now, mere 3 to max 4 months (with one exception) between updates, i.e. over 20 in just five years weren’t enough for that already? Wow. Okay.

    No it wasn’t Robin, I was getting to the point where I almost ran out of Kool-Aid, should have asked for some of your plentiful supply of it really.

    Has it got to the point where someone posts a COMPLIMENT to the FCPX team and you still have to charge in with a snide comment?

Page 9 of 10

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