Hi friends,
2 years ago i set up an Logic CPU Test that simulated situations like having enough power but CPU spikes causing CPU dropouts stopping the playback
It took some time to find the right balance but it was pretty helpful to understand how to deal with CPU settings, diffrent output devices can cause different results aso...
I tested with:
---
MacOS: Mojave 10.14.6
Mac Model: Mac Pro (Early 2009)
Prozessor: 12 x 3.46 Intel Xeon
RAM: 48 GB
Logic Version: 10.4.8 - 10.5.1
---
Depending on the output device, I was able to (clean) playback
20 Tracks with MH2882 2D Output Device (MH had a driver Issue that caused cpu "crackles" at an early stage and only 20 tracks could be playbacke dean)
89 Tracks with Loopback Output Device
91 Tracks with Merging VAD Output Device
This Mac Pro setup Geebenches @ 559 (single core) 3905 (muli core)
Now I have an M1 MacBook Air 16 GB RAM too, and it Geekbenches @ 1705 (single core) 7415 (muli core)
Following the Geekbench scores everybody would assume, the M1 Air preforms better in this test, but it doesn't, it preforms way worse!
---
MacOS: Big Sur 11.6.1
Mac Model: MacBook Air (2020)
Prozessor: M1 8 core
RAM: 16 GB
Logic Version: 10.7.2
Output Device: Internal Speaker
clean playback: 40 tracks with Internal Speaker Output Device
---
Temp Summary: My M1 AirBook with a 3x higher single core and 1.9x higher multi core Geekbench performance clean playbacks 2.25x lesser tracks in this test compared to my old Mac Pro.
What is the issue? I don't know, that's why I opened this thread cause I want to replace my old Mac Pro with a new Mac Studio and this result confuses me.
I would appriciate if folks in this forum, would do the test to, especially those who own a M1 Max to see if there is something wrong with my MacBook Air of it's a general issue that should be reported to Apple.
1) Please use the following Logic Audio Settings:
I/O Buffersize: 128 Samples .... (if only playback, lower settings bring more preformance when you push the cpu to the limit)
Processing Threads: Automatic
Processor Buffer Range: Large
Multithreading: Playback & Live Tracks
Summing: Standard Precision (32 Bit)
Rewire Behavior: Off
2) Please do the test with different Output Devices if possible. I tested my M1 only with the Internal Speakers cause all my audio Interfaces now have a ethernet connection and I don't have a thunderbolt adapter.
3) When you open the test project, you will see only one software instrument track loaded with an alchemy setting and a Bach midifile on it. Send 1 is open and points to an AUX Track with 5 Chroma Verbs in a row. Make sure all verbs are turned on. Stay on the set playback loop cause that's the part where the CPU always drops out cause there are midi glissandos. (more data at once for the CPU). You will see also an Midi Track. Some people use it to push the limit cause if you select the Midi track and start the playback, Logic says: cool, no software instrument i have to calculate if the user decides to play on on the midi keyboard and releases more cpu power.
Is this a real world test? No, cause we are testing the CPU, but since I alway ran into CPU spikes in a production that caused CPU dropouts, stopping the playback, it simulates what happens when you run into real world limits. And no, don't let the test frustrate you, it is set up to start with an heavy cpu load.
Download Link SPUMD Logic CPU Test
Stop the playback, duplicate the Alchemy tracks (best in 10s), copy the midi region to the new alchemy tracks, playback again till the cpu drops out. Write the results in this thread providing the following informations: (p.s. close all other applications like safari while testing)
---
MacOS: xxx
Mac Model: xxx
Prozessor: xxx
RAM: xxx
Logic Version: xxx
clean playback: xxx tracks with xxx Output Device
---
Thanks for participating.
Greetings SPUMD