[Erik Lindahl]

I can also add PP sadly has a very unreliable graphics / rendering engine. It’s quite sad actually. One could say odd even. Given Adobe has some of the most used graphics and animation apps out there one would imagine better integration and consistency. Today this isn’t the case by a long shot and I doubt it ever will be.

[Erik Lindahl]

Being in the Adobe-camp for a few key reasons I can say a lot of things aren’t as impressive as they make it sound.

– Tracks are key for my work doing online / finishing. FCPX is far to messy. Having lanes for video would probably solve this but not so yet.

– Relinking is imparritive for me. Every iteration of FCPX has had issues with this. This is virtually not an issue in PP.

– XML / EDL / AAF i/o is impartivie. This is virtually a non-issue in PP as long as you know how to make the app work the way you want.

– A/V output is chockling unresponsive in FCPX. This isn’t an issue in PP.

– Dynamic linking I’ve never really found that impressive in PP, on the opposite you really need to know what works and to to make it work for you. It’s of course better than anything out there but it’s not THE solution. Copy & paste items from PP to AR works 90%. Filters are very much hit and miss. You’re still forced to organize everything in Finder, PP and AE. For the most part I always render everything out from AE manually adding it to the edit in PP. Force relink however works even if files change format, coded or duration.

– CC media files are very much hit an miss. For example rendings of .ai files is horrible in PP, AE sorts this perfectly but then having PP or FCPX doesn’t really matter – aside from the relinking issues I’ve had with FCPX (i.e. force updating file on disk).

– Format / codec support in PP is amazing and can also be a bane. But it’s wide support is a life-save and we’ve even had projects where AVID editors where required to use PP for this technical reason.

– The GUI of PP is something like a polished cluster f’k. FCPX looks so much better. I’m primary taking looks but to a degree also funktion. That said here FCPX has some massive downsides as well. Keeping track of media, source names / TC of various tracks and items in a timeline is a pain in the neck or impossible in FCPX vs PP. Comparing timelines also a pain, yet certain things in X are 10 times easier / faster.

Basically all systems have ups and downs. Some even remove your source media when clean out its cache! 😉

[Erik Lindahl]

Looking at it from my point of view and a “top OS” point of view they should build the i/o suppport into Core Video / AV Foundation rather than just FCPX. This would potentially mean any app could have the same output features as an NLE.

In theory this should be virtual interfaces as well such as a h264 realtime encoder and having a virtual screen as your output (i.e. stream your AV Output to another device).

[Erik Lindahl]

Dual GPU monitors isn’t a problem with FCPX. I think others have talked about having a third monitor vi for example the MP’s HDMI-port.

I only think it’s a matter of priority and optimization. Premiere was virtually useless when we started testing it back in I think CS 5.5. Performance died when using a video interface. Now that isn’t a problem at all most of the time (I say this since I have tested 4K monitoring).

[Erik Lindahl]

I can confirm the issue of FCPX performance when using AV-output via a video interface (BMD / AJA). No machine, no software or OS-version makes any difference for me. It’s the number one issue I’ve had with the app since day 1.

I talked to one of the guys behind “that shared storeage” for FCPX at IBC last year and he confirmed my issue also. Even one of the presenters there editing a feature in FCPX noted “outstanding performance” (as long as AV-output was turned off).

It’s really crap and defiantly is a deal breaker for me. It astounds me they haven’t fixed it by now as the FCPX engine aside from this massive omission is an amazing piece of technology.

[Erik Lindahl]

Great to hear progress for FCPX but I’ve lost hope that Apple will ever fix proper, delay-free video output over SDI. This omission renders the app hard to or even impossible for us to use in an online / finishing senario.

[Erik Lindahl]

I personally have way better experience with AJA hardware in general but in regards to this lag / playback delay issue I’ve seen no difference between a variety of systems. I even saw the same remark from the editor behind the massive Finnish war film being edited in FCPX. He turns off AV-output when he’s editing alone on the system as it’s way to slow otherwise.

This shouldn’t have to be the case. The FCPX pipelines is vastly superior to for example PREMIERE on the same system in terms of speed when doing a final render. It’s just got a terrible output delay happening.

[Erik Lindahl]

Sadly that’s a no-go since we use Resolve.

[Erik Lindahl]

8-core 2013 nMP / D700 / 64 GB / 1TB with a LaCie 8-big 24TB raid and a BMD Ultrastudio 4K.

Sadly this issue has persisted on every single version of FCPX / OSX and hardware I’ve tested. MacPro 2008 and MacBook Pro 2011 with AMD-GPU’s and AJA video-cards (Kona 3 and t-tap), iMac 2012 with a GTX680MX and BMD Ultra Studio Monitor and the nMP. I must have tested every macOS- / FCPX-combo.

[Erik Lindahl]

I’m very sad to see FCPX 10.3.1 still suffers from horrible latency when A/V output is active. I’ve sadly had it confirmed “that’s the way it is” more or less. Unusable I’d even say for people requiring this.