[Oliver Peters]

I have numbers against the iMac Pros, as well. Though not on the AE benchmarks. I would also recommend that you study the scores chart from Puget Systems that’s in the RedShark post. They covered a whole range of Macs and PCs.

It’s really not about the age of the machine. The 2013 Mac Pro actually still holds up against the iMac Pros and iMacs. It’s all about the components selected and how they are combined. Apple’s biggest disadvantage right now is their lack of CUDA support. That was a major differentiation in my testing. Apple’s designs right now play towards the advantages of use with FCPX to the detriment of other applications.

Regarding the price, remember that this PC has more drives and the NVMe SSD is lightning fast. There’s also a lot more connectivity than any iMac. A better comparison is the equivalent configuration in an iMac Pro. If you take that PC as an example, back out the 6TB media drive and add back in a 5K display, then you are at about the same price. Maybe a couple of hundred cheaper than the iMac Pro. If you run that comparison, the Premiere speeds are quite similar, and the AE and Resolve speeds are still faster on the PC. However, if you work a lot with native 6K/8K RED footage, then the PC is clearly superior with Premiere Pro.

– Oliver

Oliver Peters – oliverpeters.com

[Oliver Peters]

Thanks. It’s a sweet machine.

– Oliver

Oliver Peters – oliverpeters.com

[Oliver Peters]

[Doug Metz] “That’s why I edit with the compound clip”

OK, I see, you compound the track first and then edit with that as the source. I work differently. I build the edits and then compound that so I have a single edited track to length.

[Doug Metz] “your edits won’t be correct because the wav and mp3 files may not start at exactly the same time”

I’m not entirely sure you’ll get a relink in that situation.

– Oliver

Oliver Peters – oliverpeters.com

[Oliver Peters]

[Doug Metz] “Then open the compound after approval and replace the mp3 with the new wav.
“

Then you have to go segment by segment and make sure to match the correct edit points. Relinking solves all of that. But yes, if you can’t get relinking to work, then that’s the only way.

– Oliver

Oliver Peters – oliverpeters.com

[Oliver Peters]

[Michael Hancock] “Everything is on the QNAP. Libraries and media”

Yep, that hasn’t worked well for me.

– Oliver

Oliver Peters – oliverpeters.com

[Oliver Peters]

[Michael Hancock] “But we also make extensive use of proxies for a lot of our edits, which might help with overall performance?”

Yes, I think so. Are the Libraries local or all on QNAP?

– Oliver

Oliver Peters – oliverpeters.com

[Oliver Peters]

[Michael Hancock] “In general, or in regards to relinking and file tracking?”

In general. There are specific issues with the types of links it will support. If Ronny Courtens sees this thread he can elaborate. I never run Libraries on QNAP, only source media (in place), so I don’t know the full issue. In general, I don’t find performance to be good at all with FCPX and QNAP. I believe LumaForge recommends NFS if you are working with FCPX.

– Oliver

Oliver Peters – oliverpeters.com

[Oliver Peters]

[Bouke Vahl] “Do you have experience with Iscsi with Qnap?”

Me? no.

– Oliver

Oliver Peters – oliverpeters.com

[Oliver Peters]

[Michael Hancock] “I am not seeing this behavior for files stored on our QNAP. “

FCPX does not work well with SMB.

– Oliver

Oliver Peters – oliverpeters.com

[Oliver Peters]

[Warren Eig] “Is it possible there is a render file reference the old file? Delete renders?”

Doubtful. It’s audio and I don’t do BG renders. But there could be some sort of BG “conform” file.

– Oliver

Oliver Peters – oliverpeters.com