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.

  • Oliver Peters

    January 20, 2017 at 4:39 pm

    [Joe Marler] “This was apparently a new problem. Previous versions have been tested with a timeline up to 588 *days* long, and with up to 1,000 layers:”

    None of those are realistic tests. The real test is to take a long timeline, like a 90+ min. feature film. Drag a primary clip (with numerous connected clips) from the back to the front and see how laggy it is. Especially is you have an adjustment layer across the entire timeline. That’s the real issue and largely a mess in X. Much faster to copy, delete, paste insert and adjust.

    Now in fairness, it’s tough for other NLEs, too, because of look-forward and look-behind playback functions. It’s what Avid calls “building the pipes”. To get around these issues, they have long offered the ability to alter the playlength. That’s a command that controls how long a sequence has to play before it stops. It a similar issue with X and other NLEs. However, Premiere is about the smoothest in this regard.

    That being said, I’ve cut a feature film back in the 10.09 days and it was fine. However, like most features and other feature editors, I cut in reels and then combined them for the final film sequence. And I used proxies the whole way, as this was a RED-originated film. Worked fine on a 2010 tower.

    – Oliver

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

  • Oliver Peters

    January 20, 2017 at 4:40 pm

    [Scott Witthaus] “Took Premiere a lot longer, though.”

    No, not really.

    https://digitalfilms.wordpress.com/2015/03/31/focus/
    https://digitalfilms.wordpress.com/2014/11/07/gone-girl/

    Compare the dates.

    – Oliver

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

  • Bill Davis

    January 20, 2017 at 4:42 pm

    This deserves a response.

    I’ve known Mads and Ryan Velin since NAB last year.

    They have successfully deployed X on shows that Metronome produces. Hour long episodic shows , even COOKING shows (imagine that!) – the very type of shows you have long opined that X wasn’t capable enough to do.

    Well some years back, instead of imagining how a thing “might” work – they actually investigated it, analyzed it, selected it, and then made it work. Delivered series to air with it effectively and now are delighted to find that something big changed yesterday to make it work even better.

    Sorry that wasn’t news about anything you use. But it wasn’t.

    It was news for those of us who use FCP X. Which is why I posted it here – in the forum about FCP X.

    So trying to spin this as “now it finally works” is unadulterated BS and a bit “sour grapy” IMO

    And I suspect that deep down, you know that Herb.

    FWIW.

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

  • Oliver Peters

    January 20, 2017 at 4:51 pm

    [Eric Santiago] “I just spent a week trying to get a dongle to work.
    Maybe that other A*** should use Apples Cloud licensing option next time around ☺”

    Or maybe you could just change from the dongle option to the other licensing methods, like others have.

    – Oliver

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

  • Andrew Kimery

    January 20, 2017 at 5:17 pm

    [Bill Davis] “And I suspect that deep down, you know that Herb.”

    I suspect part of Herb’s snark is in that you purposefully left off Mads last line about the performance improvement in the timeline (initially I had wondered why you didn’t provide a link to the article where the comment was made). You could have acknowledged the performance issue and highlighted that Apple fixing it is proof positive that Apple listens to its customers that might have more challenging projects than most, and is continuing to advance FCP X for all users.

    [Bill Davis] “So trying to spin this as “now it finally works” is unadulterated BS and a bit “sour grapy” IMO “

    From a comment below the one Mads made, Stefan Sundlöf said, “This is the most important update so far for us who work in longer formats. I’ve waited over five years for this.”

    Don’t paint FCP X as all unicorns and pixies and other people will probably stop pointing out that those creatures don’t exist.

  • Herb Sevush

    January 20, 2017 at 5:21 pm

    [Bill Davis] “So trying to spin this as “now it finally works” is unadulterated BS and a bit “sour grapy” IMO

    And I suspect that deep down, you know that Herb.”

    I didn’t say “now it finally works,” Mads did. If you have a problem with that phrase maybe you shouldn’t have posted it. Given the other posts I see that this was a reference to something that had been lost in a recent update, a common occurrence in all software, and I understand it in context. On the other hand it was a little questionable to leave that bit of the quote out, gets one to wondering.

    Herb Sevush
    Zebra Productions
    —————————
    nothin\’ attached to nothin\’
    \”Deciding the spine is the process of editing\” F. Bieberkopf

  • Oliver Peters

    January 20, 2017 at 6:21 pm

    [Andrew Kimery] “Don’t paint FCP X as all unicorns and pixies and other people will probably stop pointing out that those creatures don’t exist.”

    Just to add to that. I was just now converting an FCPX short film for a friend to XML and AAF for further audio and video post. The director cut it and used X, because that’s what he knows, but my friend wants to do color correction in Resolve and possibly final edit tweaks in Premiere.

    The FCPX project “appears” to be fine. Yet the XML through XtoCC was completely unusable. Resolve interpreted the FCPXML OK (I think), but can’t find one clip. I have now idea whether the AAF through X2Pro is correct until the Pro Tools guy checks in. The XML out of Resolve is also useless (we haven’t generated new Resolve media yet).

    My point with all of this is that FCPX is fine as a closed ecosystem, but every time I have to go out of it to the larger post world, I have to hold my breath. More so than with either Premiere or Media Composer.

    – Oliver

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

  • Steve Connor

    January 20, 2017 at 6:30 pm

    Just checked with a couple of projects that I have that are over 90 mins and there IS a noticeable difference in speed and responsiveness. However it wasn’t actually that bad before the update, certainly not unusable!

  • Andrew Kimery

    January 20, 2017 at 6:34 pm

    Have you tried comparing notes with Shane Ross? I think he’s finished 3 or 4 documentaries in Resolve that were cut in X. Maybe you two can become the Dynamic Duo of X to Resolve! 😉

  • Tangier Clarke

    January 20, 2017 at 7:14 pm

    I can actually drag clips on the second storyline now without the spinning beachball showing up on my more-than-adequately setup iMac 5K with thunderbolt RAID attached.

Page 3 of 10

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