M4 Mac Issues

[climber]

Originally Posted by marianna

Let me touch base with the engineers and see if there are specifics.....

Stand by.....

Marianna

this would be very useful as I am about to pull the trigger on a new Mac M4 Mini. my venerable 2013 cylinder, which has been great all this time, is starting to have issues.

t/y

[thin ice]

Originally Posted by simonchase

Do you know why some users are using M4 macs without issue? Are there factors that make it more or less likely to fail?

There was an update to iLok and also the problems with Sonnox plugins were solved with new software.

[thebeatless]

Originally Posted by thin ice

There was an update to iLok and also the problems with Sonnox plugins were solved with new software.

Even with these fixes from third parties, the issue remains in pro tools on my aging m4 MacBook. But.... I can’t imagine this is such a difficult issue to fix?! Avid, is instead focusing on Ai transcripts for the post production world. Which is an absolutely useless feature for myself and their rapidly shrinking music user base.

Westlake Pro, one of Avid’s largest dealers, just went out of business. This can’t be a good sign for Avid.

[Darryl Ramm]

Originally Posted by thebeatless

Even with these fixes from third parties, the issue remains in pro tools on my aging m4 MacBook. But.... I can’t imagine this is such a difficult issue to fix?! Avid, is instead focusing on Ai transcripts for the post production world. Which is an absolutely useless feature for myself and their rapidly shrinking music user base.

Westlake Pro, one of Avid’s largest dealers, just went out of business. This can’t be a good sign for Avid.

You have assert errors that seem to me to be different than issues related to iLok caused errors with plugins on m4. My worry would be there are lots of conversations crossing here, and this is your thread and I am not following if Avid is actually looking at your problem *at all*. Do you have a support case open with Avid? Have they given you a bug number and let you know they are working on that bug? What are those case and bug numbers?

In all this chatter I am not noticing Avid talk about any issues on the m4 except the iLok/plugin issue. Maybe I missed it, if so my bad, if Avid are maybe Marianna or Tope could add that info with bug numbers.

I would be paranoid/conservative and assume your specific problem is not actually getting worked on at all unless you have confirmation it is. Maybe you might get lucky, and this will be swept up with other fixes, maybe not.

One useful test seems to be to see if this possibly in any way is third party plugin related or not... can you reproduce these problems on the m4 Mac after moving all plugins out of the plugin folder and trashing prefs? That still leaves Pro Tools core plugins there (they get put back when Pro Tools starts) but I don't think they are potential causes of issues here (if they are suspects there are ways of deleting them as well).

[marianna]

Originally Posted by thebeatless

Even with these fixes from third parties, the issue remains in pro tools on my aging m4 MacBook. But.... I can’t imagine this is such a difficult issue to fix?! Avid, is instead focusing on Ai transcripts for the post production world. Which is an absolutely useless feature for myself and their rapidly shrinking music user base.

Westlake Pro, one of Avid’s largest dealers, just went out of business. This can’t be a good sign for Avid.

the beatless......

You know, these kind of posts really get my dander up...... No proof of anything, no validation, just out and out speculation. Geesh

After a discussion today with PACE - the latest info is........

Pro Tools currently does not support Apple Mac computers with M4 chips due to a compatibility issue with PACE iLok licensing. However, earlier Mac models with M1, M2, and M3 chips remain unaffected. PACE has resolved this issue in their latest SDK, which will be integrated into the next Pro Tools release, targeted for Q2 2025.

Thats the scoop.

Marianna

[marianna]

Originally Posted by Darryl Ramm

You have assert errors that seem to me to be different than issues related to iLok caused errors with plugins on m4. My worry would be there are lots of conversations crossing here, and this is your thread and I am not following if Avid is actually looking at your problem *at all*. Do you have a support case open with Avid? Have they given you a bug number and let you know they are working on that bug? What are those case and bug numbers?

In all this chatter I am not noticing Avid talk about any issues on the m4 except the iLok/plugin issue. Maybe I missed it, if so my bad, if Avid are maybe Marianna or Tope could add that info with bug numbers.

I would be paranoid/conservative and assume your specific problem is not actually getting worked on at all unless you have confirmation it is. Maybe you might get lucky, and this will be swept up with other fixes, maybe not.

One useful test seems to be to see if this possibly in any way is third party plugin related or not... can you reproduce these problems on the m4 Mac after moving all plugins out of the plugin folder and trashing prefs? That still leaves Pro Tools core plugins there (they get put back when Pro Tools starts) but I don't think they are potential causes of issues here (if they are suspects there are ways of deleting them as well).

Thanks Darryl for responding and I agree that something else must be going on here with the system.

Thebeatless - I would like to create a case and focus on the M4 and not your PC or M2

Can you PM me the issues you are seeing and or email me directly so I can get a case going?

Marianna

[thebeatless]

Originally Posted by marianna

the beatless......

You know, these kind of posts really get my dander up...... No proof of anything, no validation, just out and out speculation. Geesh

After a discussion today with PACE - the latest info is........

Pro Tools currently does not support Apple Mac computers with M4 chips due to a compatibility issue with PACE iLok licensing. However, earlier Mac models with M1, M2, and M3 chips remain unaffected. PACE has resolved this issue in their latest SDK, which will be integrated into the next Pro Tools release, targeted for Q2 2025.

Thats the scoop.

Marianna

Sorry it wasn't clear that I was kidding around! I wrote it on my phone before getting any coffee in me this morning. Clearly my 4 month old computer is not "aging", and I'm just poking fun at everyone wanting to get on the Ai hype train. Which unfortunately does nothing useful for my day to day so far.

I haven't bothered opening a support case for this yet. I don't have the time to invest other than a couple of minutes to complain on here.

It is true that Westlake pro has closed its doors though, and it does concern me!

[Eric Lambert]

Just to remind the room that thebeatless has posted many instances of issues, with more than one system, which have been blamed on Avid or PT but have turned out to be something else entirely and there's quite a lot of vitriol from them when anyone suggests otherwise. I don't know what's going on and why problems stretch across multiple systems but there's clearly a deeper problem with the approach to setting up a system and even more so when troubleshooting. These posts aren't requests for help as much as they are complaints, evident by the fact that the help is fully ignored so that the complaints are able to continue. To people new to this and worried about experiencing similar issues, you likely will not.

[thebeatless]

Originally Posted by Eric Lambert

Just to remind the room that thebeatless has posted many instances of issues, with more than one system, which have been blamed on Avid or PT but have turned out to be something else entirely and there's quite a lot of vitriol from them when anyone suggests otherwise. I don't know what's going on and why problems stretch across multiple systems but there's clearly a deeper problem with the approach to setting up a system and even more so when troubleshooting. These posts aren't requests for help as much as they are complaints, evident by the fact that the help is fully ignored so that the complaints are able to continue. To people new to this and worried about experiencing similar issues, you likely will not.

Eric, why do you feel like you always have to chime in? Are you dealing with this issue? Do you have anything actually informative or helpful to say? Simply nothing better to do with your time?

Clearly I'm not the only one experiencing this issue. Read the thread. I posted here in hopes that it would get back to developers, and/or other working professionals that may have encountered the same problem but found a solution? Isn't that the point of this "community"?! That's all I've ever used it for. I don't come here in my spare time just to belittle others that have many more years of experience, knowledge, and success.

[Eric Lambert]

Originally Posted by thebeatless

Eric, why do you feel like you always have to chime in? Are you dealing with this issue? Do you have anything actually informative or helpful to say?

We just bought 3 of these machines so yes I'm quite invested in the M4 conversation, but proving that to you is not a prerequisite for participation. Pay closer attention to what people have been telling you and this will all be less frustrating. That should be helpful.