Jump to content

New Logic Multitrack Benchmark Test


TTOZ
 Share

Recommended Posts

I've gone for the Air, it does seem more stable compared to the Pro once you've hit the warm temperature while the Pro is more jumpy and that at a performance difference of 7% in real tasks.

 

Also I like that it's always quiet and that I don't have to deal with the touchbar.

 

The Air has the same performance as the 2.3 GHz i9 Macbook Pro so I'm very happy.

Link to comment
Share on other sites

  • 1 month later...

my MacBook Air M1 256 8GB at 32ms hits 105 tracks on the stock plugin project. increasing buffer size does not seem to make a difference though?

 

[edit: my 4.2 Quad core i7 iMac with 16GB get's stuck at 66 tracks... wow... I'm impressed by the M1]

MacBook Pro (Retina, 13-inch, Early 2015)

MacOS 10.12.6

LP10.3.2

Apogee Quartet

Link to comment
Share on other sites

  • 2 weeks later...
yes the no fan property is brilliant, the thing is dead quiet. Doesn't get hot either, not even on Teams video calls (my MBP 16" went to frying conditions ) . You can really use it on your lap

MacBook Pro (Retina, 13-inch, Early 2015)

MacOS 10.12.6

LP10.3.2

Apogee Quartet

Link to comment
Share on other sites

  • 7 months later...

My new 16-inch MacBook Pro with the M1 Pro chip arrived today, so why not run the good old multi-track test to see how it performs. I get up to around 156-157 tracks when I start getting interruptions. But I'm most impressed by the complete lack of fan noise. Only if I put my ear close to the keyboard I can hear a distant hum. I've never realised what difference it can make. Astonishing.

 

Edit: Setting the buffer size to 1024 ms and changing the processing threads setting from automatic to 10 cores allowed me to bump the track count up to 175!

16" M1 Pro, Mac OS 12

Logic Pro X 10.7, RME Babyface

Link to comment
Share on other sites

should stay the same on buffer 64, the key to the track bump is changing processing threads.

Generally, with Automatic, Logic leaves efficiency cores alone.

It's even more dramatic on a non-Pro/Max M1 because it has 4 efficiency cores as opposed to two. (you got 20 more tracks, on a 13" M1 you get 40 more.)

| 13" M1 Pro | Big Sur 11.1 | Logic 10.6.1

RME FireFace 800 / UFX+ | ROLI Seaboard RISE 25 | ROLI Blocks | nOb Control | StreamDeck

Link to comment
Share on other sites

  • 3 weeks later...
My New MBP 16" 16/1TB running this test with 128 samples in Threads in Auto=157. Running with threads at 10=186

 

M1 Pro or M1 Max ? :)

Logic Pro 10.5.1 • OS X 10.14.6 • MBP 15" Early 2013 • 2.4 GHz Intel Core i7 • 8GB RAM • iMac 27 Late 2013 • 3.4 GHz Intel Core i5 • 16GB RAM • Focusrite Saffire 6 USB • cheap midi keyboard • Korg NanoKontrol • Roland UM-One mkII • Behringer FCB1010 • Gibson ES335
Link to comment
Share on other sites

M1 Pro or M1 Max ? :)

 

The number of available GPU cores will have no affect on the amount of plugin processing Logic can do, so for the purposes of the benchmark, it's irrelevant... ;)

 

The only real difference between them is more CPU Cores, a second ProRes engine, and the ability to support >32GB of RAM (and the memory bandwidth for that) - the bits that run the plugins are the same in either case...

 

I've not seen anything that suggests the higher memory bandwidth works on lower RAM amounts, or whether it's only for supporting eg >32GB at the same speed as 16GB, so I can't really comment on that bit... If the former, it's possible that the Max might show some improvements with certain plugins due to moving memory faster but again, I've not seen anything to that effect, so...

mu:zines | music magazine archive | difficultAudio | Legacy Logic Project Conversion | Logic 10.7.4, MBP 16" M1pro

Link to comment
Share on other sites

My New MBP 16" 16/1TB running this test with 128 samples in Threads in Auto=157. Running with threads at 10=186

 

M1 Pro or M1 Max ? :)

 

Sorry, this is the M1 Pro. But as des99 said above, I don't think the Max will do much better in audio. But I am certainly happy with these results so far. the only reason I abandoned my MP was software compatibility issues. I was running up against software requiring an OS I couldn't run.

 

But I rarely brought my MP to it's knees with my audio work. Once and a while I would freeze tracks, but not very often .

Kayle Clements

composer

 

clementunes.com | music

MBP 16" 16GB | 1TB

Link to comment
Share on other sites

Thanks guys :) Couldn't it be possible that the Pro would perform even better than the Max, e.g. due to thermal throttling differences ? :)
Logic Pro 10.5.1 • OS X 10.14.6 • MBP 15" Early 2013 • 2.4 GHz Intel Core i7 • 8GB RAM • iMac 27 Late 2013 • 3.4 GHz Intel Core i5 • 16GB RAM • Focusrite Saffire 6 USB • cheap midi keyboard • Korg NanoKontrol • Roland UM-One mkII • Behringer FCB1010 • Gibson ES335
Link to comment
Share on other sites

The Pro is a bit lighter than the Max, and as it's a much smaller chip, generates less heat and uses less power - I consider those advantages... ;)

 

No, it's not going to perform better - honestly, thermal throttling would need some hefty workloads to get to that point, these machines are incredible. I keep touching mine (running clamshell mode) and no matter what I do, it's cold*, silent*, and just feels like it's turned off... (!)

 

(* This makes me very happy!)

mu:zines | music magazine archive | difficultAudio | Legacy Logic Project Conversion | Logic 10.7.4, MBP 16" M1pro

Link to comment
Share on other sites

That sounds great ! Running 150-180 tracks in this test is pretty hefty though, but I guess they don't get especially hot anyway ? Amazing machines it seems.. :)
Logic Pro 10.5.1 • OS X 10.14.6 • MBP 15" Early 2013 • 2.4 GHz Intel Core i7 • 8GB RAM • iMac 27 Late 2013 • 3.4 GHz Intel Core i5 • 16GB RAM • Focusrite Saffire 6 USB • cheap midi keyboard • Korg NanoKontrol • Roland UM-One mkII • Behringer FCB1010 • Gibson ES335
Link to comment
Share on other sites

  • 1 month later...
my MacBook Air M1 256 8GB at 32ms hits 105 tracks on the stock plugin project. increasing buffer size does not seem to make a difference though?

 

[edit: my 4.2 Quad core i7 iMac with 16GB get's stuck at 66 tracks... wow... I'm impressed by the M1]

 

Hmm, are you still getting 105? I'm seeing a lot of results that are 90 and above but my Air doesn't want to go above 82, even with the Processing Threads and Processing Buffer Range settings maxed out, and at any buffer size.

 

Geekbench results seem about on par with what's expected.

 

Is there another setting somewhere I'm overlooking?

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...