New Mac Studio with M1 Max or Ultra

[smashprod]

Just starting this thread early; I know no-one has this in their hands yet, but am looking to find out a few things as soon as someone gets one:
1) Can you roll back the OS on this machine to Big Sur (actually, I know you "can", I guess the question is more "does the Mac Studio have any problems operating under Big Sur?");
2) Does DP11 exhibit the documented MIDI timing bug that it has under many Intel CPUs? See my thread "MIDI recording late";
3) The main question, does DP11 run on this machine (it should, it works fine on the previously released Apple Silicon CPUs)?

[Kurt Cowling]

In regards to question 2. I have a MBP with M1 Max and there is no timing problem with MIDI.

[smashprod]

In regards to question 2. I have a MBP with M1 Max and there is no timing problem with MIDI.

Yes, MoTU has tested this on that machine as well. Are you running Big Sur?

[mikehalloran]

Just starting this thread early; I know no-one has this in their hands yet, but am looking to find out a few things as soon as someone gets one:
1) Can you roll back the OS on this machine to Big Sur (actually, I know you "can", I guess the question is more "does the Mac Studio have any problems operating under Big Sur?");
2) Does DP11 exhibit the documented MIDI timing bug that it has under many Intel CPUs? See my thread "MIDI recording late";
3) The main question, does DP11 run on this machine (it should, it works fine on the previously released Apple Silicon CPUs)?

You know it can be rolled back to Big Sur? Really? Usually, new Macs have it in the firmware that they can’t be rolled back to an OS before the initial release date. Since the first ordered units won’t arrive till next month, we won’t know till we know.

Frankly, Monterey is great except for iZotope not updating Exponential Audio reverbs to run over it. The new Studio should get AVID off their butts and make PT a Native app — which should let the rest of the dominos fall.

[James Steele]

The new Studio should get AVID off their butts and make PT a Native app — which should let the rest of the dominos fall.

I hope they do this fairly soon. Money is tight for me until I get past April when I'm bombarded with taxes. But I want to make a move on a Mac Studio in the coming year so I can take the tax write off. It also happens that my Pro Tools perpetual license support will end in October. So I'd like to have one before then so I can at least get the Pro Tools M1 native version before my license expires. Maybe there's a way to download the installer before my support runs out even if I don't have an M1 by then?

[mikehalloran]

Going out on a limb here but I’m guessing that, if the Studio cannot be rolled back to Big Sur and PT is not yet compatible with Monterey except over Rosetta 2 by the time those new Macs are in the hands of customers, heads are going to roll over at AVID.

You just know that their entire Sales team is in a conference room right now in a building near me screaming at someone, “New Macs are on the way and we’re not ready!!!!!! What the … is going on around here!!!!!!”

I’ve haven’t been in such meetings since Win XP came out but I remember them well. If it sounds like, “We’re all gonna die!!!!!” it’s because bonuses and commissions go down when the customer base isn’t being served.

[smashprod]

How well do PT and DP do under Rosetta 2? BTW, I’m keeping my Intel Mac to run PT until this is resolved. Just want an M1 for DP due to the timing bug.

[dix]

How well do PT and DP do under Rosetta 2? BTW, I’m keeping my Intel Mac to run PT until this is resolved. Just want an M1 for DP due to the timing bug.

Not sure what timing bug you’re referring to. DP is solid on my on my cMP. Anyway, I haven’t tried PT, but DP is pretty clunky in Rosetta. I only use it to open legacy projects when absolutely necessary. …and after installing a new plugin to make sure the AU examination process happens as it should.

[smashprod]

That’s a drag to hear DP doesn’t do well under Rosetta 2. MoTU (and others) give the impression that it’s not much of a hit with the firepower of the Silicon M1.

The timing bug is discussed in my thread “MIDI recording late”. On a number of Intel machines MIDI records late (against click) at high buffer settings and when using a VI. MoTU is very aware of it.

[dix]

That’s a drag to hear DP doesn’t do well under Rosetta 2. MoTU (and others) give the impression that it’s not much of a hit with the firepower of the Silicon M1.

The timing bug is discussed in my thread “MIDI recording late”. On a number of Intel machines MIDI records late (against click) at high buffer settings and when using a VI. MoTU is very aware of it.

YMMV with Rosetta, but I think I've seen others report the same. I've been going through the hassle of retooling VEP projects with the AU version of the VEP plugin because running DP native is so much more efficient.

Re timing. Yes, I saw that thread when it started and thought, 'late notes with high buffer settings is expected, isn't it?' But I guess there's more to it since that thread went on and on. Hopefully MOTU is on it.