[Erik Lindahl]

I’ll make a recording of it. Even on state of the art hardware it’s MUCH slower than the unsupported FCP7 and Premiere Pro CC. I even think Resolve is more responsive.

We tend to work with ProRes in 1080p25.

[Erik Lindahl]

Well said!

[Erik Lindahl]

Adobe needs one red haired step child in their line-up now that Bridge is killed off. Premiere will be there to be beaten and laughed at… 😉

[Erik Lindahl]

The only caveat is that Affinity Photo is a photo-editor and has zero of the digital assets management features Aperture held. Apple killing Aperture is simply sad as it’s one of the best DAM’s available. It’s just gotten old, like many of Apples pro-tools before they’ve eventually killed them off.

[Erik Lindahl]

I’ve had issues with every single setup I’ve tried, from is it OS X 10.7 to 10.1, from a MacPro 2008 with three different GPU’s and a Kona 3, to a MacPro 2013 8-core / D700 / 64GB / 1TB / 1GBs RAID-5 with BMD video i/o. It’s always been laggy and I’ve talked to AJA about it at IBC and the reply is “you’re not the only one that’s commented on that”.

I guess some people aren’t as picky as me.

[Erik Lindahl]

Interesting read. To me it sounds like a yearly release cykle harms more than it helps for the end product. Maintenance should of course be kept up though-out a given version but major release say every two years sounds more resonable.

Looking at for example DaVincie Resolve they pump out features like crazy folks in a very impressive way. Then they spend a year bug-fixing before massive update hit again and rince and repeat.

The link also shedds light on why major features take so long to be implemented. At least on the OS-level. I could beilive FCPX suffers due to other factors, primarily as it’s not very prioritized with-in Apple anymore. If another media-related project requires crunch time I wouldn’t be suspired if FCPX takes the hit.

[Erik Lindahl]

I mean using “A/V Output” via a AJA och BMD interface. It’s dog slow on every system I’ve ever tried and unreliable as well.

If I press SPACE there’s a good second or two lag before playback starts.

The above ONLY is the case with A/V Output switched on. With out it FCPX is very responsive. When doing finishing or client-assisted session, this is a requirement sadly.

[Erik Lindahl]

Impressive. Let’s hope Apple updates FCPX to make it usable with external video references. It’s insanely laggy / slow at the moment for serious work.

[Erik Lindahl]

Brilliant!

[Erik Lindahl]

It sort of depends on your budget but I’d go with:

– 6- or 8-core machine
– 64 GB RAM
– Dual D700
– 512GB or 1TB SSD

The 6-core machine is probably the best bang for the buck, given for some tasks the 8-core will offer better performance. I’d only opt for the 12-core for very specific work – 3D and video encoding for example. After Effects, Premiere and Photohsop will likely perfom better on the 6- or 8-core in general.

If you can afford it, max the RAM out. I’d say 32 GB of RAM might be ok on the 6-core but if you use AE… Well I’ve seen that app eating 48GB RAM on my 8-core system.

The dual D700 is optional for things like grading, especially looking forward with UHD.

The internal SSD costs a bit but it’s blazing and will speed a lot of apps up – caching in AE for example. 512GB is mostly good but if you can afford it… 1TB! 🙂