Taking FCPX out for a new test drive

[Greg Janza]

Richard, sorry, i didn’t fully pay attention the first time to the difference in how the shared folder was set up in that video and how i had my raid share set up.

I shared a folder from the raid with that process and voila, all works now. FCPX works fine with the NTFS raid and I can save the FCPX library to the raid as well. Thanks!

Adobe Premiere 2017.1.1
Windows 10 Pro
Samsung SSD 850 EVO system
Samsung SSD 850 EVO Adobe cache
NVIDIA GeForce GTX 970
OWC Thunderbay 12t x 2 in Raid10 configuration (thru Storage Spaces and Disk Management)

[Bill Davis]

[greg janza] “If all of my problems are a result of my lack of FCPX knowledge then perhaps this critique isn’t quite fair. However, I’ve scoured the features of FCPX enough to know that there remains a list of things that are virtually a no brainer in Premiere and previously the old FCP, but in FCPX require either helper apps or workarounds to accomplish. That continuing lack of basic professional features remains so frustrating that it cancels out the positives.”

And after several dozen posts, it turns out the OPs entire problem was an extremely simple to fix in X.

Can we all just agree that anytime anyone comes here for help – can weplease leave the diatribes about how something doesn’t work properly – until there’s a bit of investigation as to if it ACTUALLY doesn’t work properly – or a particularly user just doesn’t understand how to make it work properly?

While I’d contend, X is still the most widely mis-understood NLE here – I would think this approach would be valuable about ALL the NLEs under discussion in the forum.

My 2 cents.

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

[Greg Janza]

[Bill Davis] ” it turns out the OPs entire problem was an extremely simple to fix in X.”

My main issue wasn’t a FCPX fix. Instead it was a windows fix.

The issues that remain for me with FCPX:

sluggish performance overall. Zooming in and out of timelines/projects is slow as is a variety of other basic tasks. It could be my mac but again, I’m using Premiere for comparison and I experience none of the sluggishness performing basic tasks in Premiere.

making submixes within projects is no small task. I saw another post here explaining it in detail but I’ve yet to dive in fully. I generally like how audio is dealt with in FCPX though.

Having spent some more time with FCPX, I generally like it. There’s plenty of things within it that work very well.

Others have recently mentioned the idea that editors now have the option of working in a variety of NLE programs and I’d guess that being versed in FCPX, Premiere and whatever other NLE takes hold (i.e., Resolve) will serve all editors well going forward.

Adobe Premiere 2017.1.1
Windows 10 Pro
Samsung SSD 850 EVO system
Samsung SSD 850 EVO Adobe cache
NVIDIA GeForce GTX 970
OWC Thunderbay 12t x 2 in Raid10 configuration (thru Storage Spaces and Disk Management)

[Bill Davis]

[greg janza] “The issues that remain for me with FCPX:

sluggish performance overall. Zooming in and out of timelines/projects is slow as is a variety of other basic tasks. It could be my mac but again, I’m using Premiere for comparison and I experience none of the sluggishness performing basic tasks in Premiere.”

Fair enough.

I’ll just note that the above runs counter to the general universe of independent performance testing videos that clog the internet these days. Overall, X on it’s appropriate hardware – tends to best Premiere on it’s appropriate hardware time and time again in those.

And I can say that communicating with a worldwide group of X editors near daily, I don’t hear widespread tails of sluggishness or poor performance.

At least not from other than relatively new users who haven’t learned their systems very well to date.

FWIW.

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