Was thinking about exactly that.What do you mean you "cranked up the samples to 1024" in the Logic Pro test?
If you mean you set the I/O Buffer Size to 1024, this would actually *decrease* the load on the CPU. A larger buffer size means that the computer has to process fewer buffers in the same time frame, at the cost of higher latency.
Setting the buffer size as small as possible would get the most stress on the system. That decreases the latency in the processing chain, which means the computer deals with more overhead, and has a tighter window to complete the processing of each buffer.
The situation sucks, but it's always been the case that most pro-audio software lags the latest releases (OS and hardware) by a year or more - and this is a big transition!I just wish that (most) music software companies would update their software to M1 native. Most are still saying that their software is “compatible” with Rosetta on M1 Macs. Izotope. Native instruments. Arturia. All these major plug-in developers are suggesting that we run Logic in Rosetta. I believe that they would have had the dev kit 18 months ago, July 2020? Izotope is saying that their developers are hard at work with Mac Silicon, and expect to have native versions some time in 2022. Thats helpful. Funny thing though, thats a subscription service. So people like me are paying monthly for something we can’t even use (I paid a year in advance). I’m not going to run Logic in intel emulation. Native Instruments is basically saying that they’ll have it when they have it.
But the kicker is that Waves, of all companies, is now native with their new V 13. Hey NI, Izotope, and Arturia, Waves beat you to it! So did Serum, Valhalla, and several more. Those are on our machines, and I’m not sure we need anything else.
I find myself also mildly disappointed in the iPad's progress, but I think that the M1 switch is only the beginning.Nope, decided to switch it up and give macOS and these new MacBook Pro's a try. For now. I'm disappointed in the progress that iPadOS hasn't made the last 2 years and I was expecting a lot more at this point. I know Apple's game here - straddle the line and don't give the iPad too much capability and cannibalize Mac sales, but I was hopeful we would be further ahead than we are today. My workflow is very simple - Outlook, Teams, Safari, and Remote Desktop, so I can use almost anything, but there are still some things that still feel too complicated on an iPad, and I missed the Mac a bit. My ideal set up is a dual boot 11 inch iPad Pro, but I am not sure that will ever happen.
You’re lucky, here is one that was uploaded 10 minutes agoIt would be nice to see 14" M1 Pro vs 14" M1 Max comparisons. While the M1 Pro/Max specs are the same across sizes (whether it be 14" or 16"), the thermals and cooling performance aren't, which makes comparisons like this one less than perfect.
Yea I am with you there, these new machines really are that great, but for my needs - a dual boot option on an M2 iPad Pro would be all I need. I like to pay around with both.I find myself also mildly disappointed in the iPad's progress, but I think that the M1 switch is only the beginning.
I honestly think Apple is busy with the transition, and given the brain-detonating performance of these new chips it gives me that much more hope.
Thankfully, all my Mac use was basically home-only, so an iPad Pro is the perfect device for me still. I don't have to output to monitors, or do any kind of consistent file transfer other than what the Photos, Files and iCloud can already handle. And I can live with some of the Safari "jank" that persists. I am excited to come home to my iPad, like I used to be for my Macs.
But man, the old me wishes these Macs where here 5 years ago. I wish I could put them to good use now. I'm really happy for (and jealous of) all of you that will get to enjoy these machines.
Apple has made me a fanboy again.
These are the standard conditions under which this test is performed (i.e. 1024 samples), given that the lowest latency is dependent on a number of other things - most notably the drivers for any particular audio interface. So the test demonstrated is a 'mixing' test. It's just one way of comparing systems. It doesn't even translate particularly well to other DAWs.Was thinking about exactly that.
That samples setting is one of the setting types where less is actually better in that it generates lower latency but at the cost of CPU load.
I'm in somewhat the same boat with iPadOS. I had high hopes for iOS 15 and after WWDC, I was very deflated. I love the form factor and I'm not sure I want macOS on an iPad, but iPadOS is holding back a whole lot of horsepower for specious reasons. I don't want a retread of every macOS feature, but I do want better audio handling, better integration between macOS and iOS for the Pro Apps (Logic Remote is pretty much it). I agree there are workflows that are simply too difficult on the iPad, or simply require too many steps.Nope, decided to switch it up and give macOS and these new MacBook Pro's a try. For now. I'm disappointed in the progress that iPadOS hasn't made the last 2 years and I was expecting a lot more at this point. I know Apple's game here - straddle the line and don't give the iPad too much capability and cannibalize Mac sales, but I was hopeful we would be further ahead than we are today. My workflow is very simple - Outlook, Teams, Safari, and Remote Desktop, so I can use almost anything, but there are still some things that still feel too complicated on an iPad, and I missed the Mac a bit. My ideal set up is a dual boot 11 inch iPad Pro, but I am not sure that will ever happen.
I know Apple's game here - straddle the line and don't give the iPad too much capability and cannibalize Mac sales,
that's for the 16" not the 14" ?You’re lucky, here is one that was uploaded 10 minutes ago
I also purchased an M1 Air a few days ago. It was an Apple Refurb model with 16GB of RAM and 1TB SSD for $1399. A great little machine and I will wait to update my Pro machine when then M2 Pro/Max comes out.Glad I went with the Air I bought a few days ago. My M1 Air just scored 1743 in Single Core in Geekbench 5. In other words, it's faster than the (base) M1 Pro for my daily office tasks, and even faster than my 5900x.
I think the more important difference between 14" and 16" is the screen size. That extra 500 pixels (1000 in retina) is a major difference in the usability of the machine. Working on the small Air screen coming from 27" iMac is something to get used to.In logic you don't want to "crank the samples" you want the exact opposite. the 32 or 64 would have been much better to see how the session deals with low latency. way more intensive.
This is actually what I want to see on the 14 pro vs 16 pro. can the 14 hold max power without throttling even though it's slightly smaller (specifically for music which is CPU NOT GPU intensive? That's the last puzzle piece I need to know before I buy. if it throttles at all I'll get the 16.
Ok, I didn’t hear anything about a benchmark just midi.The Logic Benchmark test loads a virtual instrument into every channel along with 4 or 5 plugins also on every channel. It's quite heavyweight. The original benchmark test from years ago was producing results of 1000+ tracks, so the new benchmark is much harder work. My Mac Pro 7.1 16-core runs about 160-180 tracks depending what mood it's in. My 15" 2015 MBP runs less than 30. My new 16" MBP M1 Max is on a par with the 7.1 16-core, as per this video.
Fair enough, I really don't get why they are holding back iPadOS then.Apple's profit margin on iPad Pro / Macbooks are generally the same. And nowadays the pricing is the same as well. In fact, And iPad Pro 12.9" is more expensive than a Macbook Pro 13" when you add the keyboard. So Apple doesn't care what you buy, as long as it has an Apple logo on it
This is exactly why I got the 16”. I haven’t had a MacBook screen the size of the 14” since 2009 with the Black MacBook I had before I upgraded to the Pro, and I’m not sure I want to lose the screen real estate. I have my phone for ultra portability- I love my 16” space.I think the more important difference between 14" and 16" is the screen size. That extra 500 pixels (1000 in retina) is a major difference in the usability of the machine. Working on the small Air screen coming from 27" iMac is something to get used to.
yup. i'm considering 4tb also, but it's sooo expensive...Also sticking with entry M1 pro 14, base ram, and putting the money in 2TB SSD in AppleCare+
It is indeed good to know that the high end is great for certain tasks but not necessarily faster for others. I do a lot Final Cut work, but not huge, long projects with heavy rendering demands, and I'm usually billing clients T&M so, shaving a minute or so here-and-there is not super critical. But money toward a larger SSD … that makes my life easier. I might just go base model 16", add some storage, and enjoy the ride!This is great to know, and a good article by MacRumors. My workflow revolves around working in large 3d files in Vectorworks and auto cad. Rendering can be part of my workflow, but mostly it's navigating large 3D spaces with complicated geometry. The M1 Max seems to be great for this. As a lifetime Mac user, I've only recently hit the point in my career where I honestly need high performance machines. Its kind of nice to get the reassurance that the extra price was worth it.
Btw this was the first post on Mac rumors on my new MBP 14".