In this video Mark Spencer and Steve Martin from MacBreak Studio once again focus on building the ultimate 4K Final Cut Pro X system around the Mac Pro. It is the last part of a 4-part series and in case you didn’t have the opportunity to watch the previous episodes, you will find the first three parts here.
We found this episode interesting as it tackles 4K workflow on the new MacPro and answers the very important question: how many streams of 4K can you play on a new Mac Pro? Or, to be more precise, how many streams of UHD RAW, Optimized, or Proxy media can you play on an 8-core Mac Pro with 32GB of RAM and dual D700 graphics cards connected to a Pegasus2 R8 RAID via Thunderbolt 2?
And below some more on this topic from Mark:
“Because the RED media we are using, 3860×2160, or exactly 4 times the size of a 1920×1080 frame, is usually referred to as “UHD” for Ulta-High Definition while the term “4K” is technically reserved for the full 4096×2160 pixels according to the DCI. But these days do a search on “4K” and you’ll see UHD referred to as 4K everywhere. For the purposes of data throughput comparisons, they are essentially the same.
The other huge factor on throughput is the device storing the data, and the Pegasus2 R8 we are using (configured as RAID 5) is wicked fast. Not quite as fast as the internal SSD on the Mac Pro, mind you, but you aren’t going to want to load that drive up with a bunch of 4K footage anyway.”
“In other words, so what if I can play multiple streams of RED RAW on this machine, when I can do the same thing with Proxy versions of the media on my Mac Book Pro? Does the ability to skip transcoding justify the additional expense of a higher-end system configuration? For some folks the answer will be “absolutely”. For others, a laptop or a high-end iMac may be the sweet spot for performance vs. cost. We hope the information in this and the past 3 episodes will help you make that decision for yourself.”
Source: http://provideocoalition.com
Is this the ultimate 4k Mac Pro editing system?
No comments:
Post a Comment