It even shows the occasional red 100% bar when doing absolutely nothing. A funny thing is that when Pro Tools is stopped, the CPU Usage meters are a lot more jumpy then when Pro Tools is playing. And to be alerted when Pro Tools has received an error during processing, I turned off ‘Ignore errors during playback/record’.Īll tracks of the test Session in the Pro Tools Mix window.During playback on the old Mac Pro, the CPU Usage window hovers somewhere between 80 and 90%. To have an honest comparison with Logic in a later post, I turned off the Disk Cache and Dynamic Plugin Processing options. The playback buffer size is set automatically in Pro Tools and can’t be altered manually. Even though this is the Input Buffer meant for low latency during recording, it still reserves some CPU power when you are only playing back. The Hardware Buffer Size is set to 1024 samples. At the moment of writing it runs the latest version of Pro Tools HD, which is 11.1.2.Īt first the Playback Engine settings are set to get maximum performance out of Pro Tools. The session was initially created on the 2007 Mac Pro to push it to its CPU limits. Later we’ll see how many the new Mac Pro can actually cope with if there are lots of plug-ins on the tracks. Using these session specifications, Pro Tools 11 HD is able to run a maximum of 128 tracks natively. The test session runs at 96 kHz and 24-bit. The 2013 Mac Pro has the HD Native Thunderbolt box variant with the same HD OMNI Interface connected during testing.
The 2007 Mac Pro has an Avid HD Native card installed with an HD OMNI Interface connected.
It has 16 GB of RAM, dual D300 AMD FirePro graphics cards, and I’m running the session off the same Seagate drive housed in a FireWire 800 enclosure connected to one of the Thunderbolt ports using an Apple FireWire to Thunderbolt adapter. The other Mac is of course a late 2013 Mac Pro with a 6-core Xeon E5 1650 V2 ‘Ivy Bridge’ running at 3.5 GHz with Turbo Boost to 3.9 GHz.
0 kommentar(er)
