M4 Mac Issues

[thebeatless]

I like to punish myself and stay on the bleeding edge with new computers, so I got an M4 Max MacBook Pro. I know it's not officially supported, but I assume/hope it will be shortly. Since setting up this system, I'm having constant issues when creating new and/or duplicating tracks. It also happens if I bounce and import to a new track. Sometimes I get a beachball, sometimes I get one of those long error messages (which I will add to this thread next time it happens with the error). Google shows zero results when I copy and search for it. I have to quit and relaunch Pro Tools to get back to work.

Also, occasionally sessions aren't allowing bounce to disk. The keyboard shortcut does nothing and the menu item is greyed out.

I have a feeling this is somehow related to having Oxford drum gate in the session. This plugin often crashes pro tools and shows an authorization error. But... the new track thing happens with or without this plugin inserted. If I try enough times, it will happen in a new and empty session.

Anyone else make this move too soon and seeing the same things?

I first tried the computer with a full migration from my M2 Max, but when these issues happened, I foolishly wiped it and did a clean install. Same issues after a miserable Sunday!

Sequoia 15.1.1, 2024.10.1, HD Native, MTRX

[tope d]

I dont have enough courage yet to bite the bullet
At least not for now as a lot of testings and adjustments still need to be done

[thebeatless]

Well, I cracked the screen on my old couch surfing laptop and needed a new one. I'm too old to be able to do everything on my phone. haha I figured I'd get the latest and greatest for the studio and make the "old" studio M2 Max MacBook my day to day laptop. It can also serve as a better 2nd rig for soundflow stem bouncing while working on the main rig. Looks like the M4 just has to sit and wait for some updates.

[smurfyou]

In another thread it was pointed out that Sonnox advises to avoid M4 machines completely. So it's likely your Oxford Drum Gate is part of the problem.

[aaronjproducer]

Maybe you can help me...

I also decided to jump without looking and got an M4 Mini. I am having the hardest time getting my HD Native Thunderbolt to come up in the playback engine. Did yours just pop up from the start, or did you have to jump through any hoops to see it? I can see in my system profiler that the mac is recognizing that it is connected... and yes I have the latest HD driver etc. etc.

Thanks for any help!

[BScout]

Originally Posted by aaronjproducer

Maybe you can help me...

I also decided to jump without looking and got an M4 Mini. I am having the hardest time getting my HD Native Thunderbolt to come up in the playback engine. Did yours just pop up from the start, or did you have to jump through any hoops to see it? I can see in my system profiler that the mac is recognizing that it is connected... and yes I have the latest HD driver etc. etc.

Thanks for any help!

You've got to do this (reduce security)
https://support.apple.com/guide/mac-...hl768f7291/mac

(it's in the installation instructions)
After you do this, then you need to authourize the Avid driver in Security/Privacy. But you have to do the first thing first before you can do the second thing. Otherwise the HD driver isn't loading.

[aaronjproducer]

Originally Posted by BScout

You've got to do this (reduce security)
https://support.apple.com/guide/mac-...hl768f7291/mac

(it's in the installation instructions)
After you do this, then you need to authourize the Avid driver in Security/Privacy. But you have to do the first thing first before you can do the second thing. Otherwise the HD driver isn't loading.

Thank you, I obviously missed that. Appreciate it!!

[thebeatless]

I do have problems with hd native disappearing occasionally. I’ll have to reselect hd native as my playback engine when launching pro tools. It got much better with the latest driver. Luckily it doesn’t happen while pro tools is open.

Also when I have to use logic, sometimes logic doesn’t see the hd native device. I have to trick the audio server app to open by trying to open the audio server launcher and audio server app repeatedly until one of them actually brings the window up. Then logic will see hd native. I think this issue has been around for a while though?

Both do happen on my m2, just less frequently.

[thebeatless]

Here's the error I get when duplicating a track:

Could not complete the Duplicate Track command because Assertion in "/Users/autobld/gitlabci/PT_COLOR/ProTools/App/Tracks/UTrackList.cpp", line 1551.

After I get this error once, I can't do anything that creates a new track. Including bouncing and importing to a new track in the session. The bounced file ends up getting deleted.

Could not complete the New Track command because Assertion in "/Users/autobld/gitlabci/PT_COLOR/ProTools/App/Tracks/UTrackList.cpp", line 1551.

Happening with or without sonnox plugins, so I think this is a pro tools issue.

[ashmatthews]

Originally Posted by thebeatless

Here's the error I get when duplicating a track:

Could not complete the Duplicate Track command because Assertion in "/Users/autobld/gitlabci/PT_COLOR/ProTools/App/Tracks/UTrackList.cpp", line 1551.

After I get this error once, I can't do anything that creates a new track. Including bouncing and importing to a new track in the session. The bounced file ends up getting deleted.

Could not complete the New Track command because Assertion in "/Users/autobld/gitlabci/PT_COLOR/ProTools/App/Tracks/UTrackList.cpp", line 1551.

Happening with or without sonnox plugins, so I think this is a pro tools issue.

I have this same error frequently. Sometimes when opening a session and sometimes even when making a new session (from a template). The only way for me to get around it is a complete restart of the Mac and waiting a couple minutes then retrying the task.