![]() ![]() ![]() And as a user of older hardware it's become more apparent. So yeah, while the sum of all parts may be beastly, the achilles heel with the older Mac Pro's is very much with the single core. Whether that increase is with the overheads of the OS or how Logic runs, or how plugins are optimised - i really don't know. Whereas you're clear, but will be on a threshold elsewhere. ![]() There's clearly a threshold that needs to be met there, and i'm teetering on the edge. Try loading a project up with a Chromaverb instance and flicking through presets - see if that causes you to spike. ![]() I have a newer Mac Book Pro which is far less powerful in regards of multi-core (Dual core i5), but much better single core and it can process Chromaverb at a stroll. But i'd say that threshold which was 1700 has now hit the 2000 mark, maybe higher. My CPU scores around the 2000 mark, and i can really notice it with some of the modern plugins, such as chroma verb that causes issues. In my experience i've worked out that i need at least 1700 per core on those benchmark results for a good Logic experience and i'm quite a modest user. It's worth looking down the list which orders the Mac Pro range by single thread benchmark score to see how the 2013 models really stepped it up, and well, the iMac Pro just is phenomenal on paper. While you've got a powerful 12 core machine, it's single core is probably the same as a 2009 4x core running at 2.7ghz, i.e.:. It seemed fine unless i automated it, OR changed presets while the project was running. And newer plugins are more likely to cause that to spike - this is the problem i had with Chromaverb. The trouble with the older multi core beasts is that if one thread spikes, you get overload. ![]()
0 Comments
Leave a Reply. |