Max 7 Mojave Compatibility (Mac OS 10.14 )

Ben Bracken's icon

Max 7 is not fully compatible with Mojave, and as such we recommend that users wait to upgrade to the latest Mac OS (10.14) until we are able to fix the issues we are seeing.

Thanks for your patience while we work on this!

yaniki's icon

Thanks. Will Max 8 be "Mojave-proof"?

animatek's icon

ouch late!

I updated and take the opportunity to make a Clean installation formatting the drive, now I can not authorize max :(

Now, patience is the key, thanks for the future update

Arabrab's icon

Thanks. Will Max 7 be "Mojave-proof"?

Tj Shredder's icon

Who needs Mojave? Wasn't High Sierra disaster enough...;-)
Old time experience: Never upgrade earlier than 3-6 months after release - and only if you cannot live without some of the new features. As long older versions are supported you are safe to stay with them.... El Capitan is stable and supported...;-)
Mostly its the other way around! You cannot live with your working tools... Think twice before you upgrade, never upgrade without having a time machine backup!

animatek's icon

Exact STEFANTIEDJE ! I just format again and went back to High Sierra, at least i had the time machine backup!

Arabrab's icon

After downgrade ..

"El Capitan" is Apple's "Windows 7".

Stability without frustration and frights.

balam's icon

Mojave fresh install + new max 8 fresh install
so far working fine. fast loading and jitter is a bit more easy on the cpu.

bt.soundmaker's icon

TY for notice.

Dalmazzo's icon

ok too late for me... no idea why I decided to upgrade.
Any suggestion of what is not compatible. I would need to downgrade depending on this.

Joshua Kit Clayton's icon


So far our major compatibility problems relate only to TouchBar MacBookPros. On these systems, when running Max 7, the embedded web browser is unable to run, which means no authorization window, package manager, file browser, or reference viewer.

If you don't have a TouchBar MacBookPro, you might be fine, but we can't guarantee it.

I'd recommend using Max 8 if you have Mojave, which in our tests so far, have uncovered no major OS specific issues.

Good luck!

Paollo Locatelli's icon

Does it mean that there will be no update?

This is not marketing, it's a blow and a scam for all those who trusted Cycling74 and bought Max 7.

Paolo

Joshua Kit Clayton's icon


@Paolo We are sympathetic to your frustration.

We actually see this as Apple's bug. Perhaps Apple will solve this crash in their supporting libraries related to the TouchBar and legacy software, and perhaps it may be included in a forthcoming Mojave update. We will be following up with Apple with a clear and isolated bug report in the near future.

To give you greater context, we have put some effort to see if the problem is easily solvable on our end, and so far it is not. Any fixes imagined on our end so far require modernizing the Chromium Embedded Framework and the application interaction with it. That option isn't even possible for 32bit binaries any more as the last version of a 32bit supported Chromium Embedded Framework was 3-4 years ago. This is to say, if we did do the work to update a 64-bit only version of Max 7, it would not solve one of the main advantages of using Max 7 over Max 8 which is it being the last 32-bit version of Max.

In the meantime, I would like to point out that you do have the option of running older versions of the Macintosh operating system with older versions of Max software, rather than using Apple's Mojave. You may also have success running Max 7 or other legacy software inside a VM like Parallels, VMWare, or VirtualBox(free), though that route may face other issues.

Arabrab's icon

"if we did do the work to update a 64-bit only version of Max 7, it would not solve one of the main advantages of using Max 7 over Max 8 which is it being the last 32-bit version of Max."

Software legacy, we are talking about software that came out weeks ago... and the beta was available when even Max 7 was in force, things should have been done there.
The argument of the advantage of the 32 bits could be resolved by allowing version 7.3.5 to be 32 bits and the next one that solves these problems for the user should be only and with a notice that indicates only 64 bits.

Then the user decides.

This would be to respect their users and not treat them like fools who manipulate according to their needs.

Joshua Kit Clayton's icon

Just to clarify, Max 7.3.5 was released over 6 months ago, and as far as we know it still works great on all systems except TouchBar MacBookPros running Mojave.

All customers who have purchased Max 7 in the past 10 months, receive an update to Max 8 for free, which is pretty reasonable from our standpoint.

Sorry for the hassle to those users who have upgraded to Mojave on TouchBar MBPs and have to deal with this inconvenience.

Tj Shredder's icon

Just as a side note, I am happily running Max 4.6.3 on Sierra!
A general note again: I f you want to run old software you should run an older OS...
I haven't read about important changes for musical applications in Mojave. What does Mojave promise for making people upgrade? Is it important at all? I have no idea...
I am afraid of the next version which will kill all 32-bit apps for no good reason...
As with Lion they just threw out Rosetta, keeping those who cared on Snow Leopard for a very long time. And it was a lot of hassle for those who didn't know that a good part of programs that used to work just stop working. Though Snow Leopard server does run fine and efficient in VMware or Parallels and probably will do so for some more deacdes...
I once set up a brand new Mac with Parallels going into full screen mode on start. It was booting faster two operating systems than any Mac from 2011 would be able to boot into Snow Leopard alone...; - )
Now of course most programs require at least El Capitan, a few Sierra... To be on either OS X would be save for some years at least I guess... And after that, depending on your use of older software you would have to switch to virtual machines (which are up 95% as efficient as the native versions on then probably much faster hardware...)

Arabrab's icon
Tj Shredder's icon

<it is well known that apple offer a free update regularly>
It is well known for ages that Apple doesn't care a shit if a "free" update breaks working setups, the first versions of OS X are more like public betas...
<and now we could be left without update>
Well, you have at least the option for an upgrade and Joshua explained why an update cannot be done easily. It seems its Apples fault, which is extremely likely, and we do not know if this will be addressed by Apple ever...
If you upgraded too early, I hope you learned a lesson... Obviously you bought Max 7 more than 10 months ago and don't care about the additional features and overall enhanced stability of Max 8. Why do you care about the enhancements of OS X more than those of Max? Just because they are "free"? There ain't no such thing as a free lunch...
Btw. If you made a Timemachine Backup, which is one genius technology of Apple, Windows users can only dream of, you can easily go back! If you didn't, another lesson learned...

Roman Thilenius's icon

Why do you care about the enhancements of OS X more than those of Max?

i bet most people who already upgraded to 10.14 do not even care about its "enhancements", they have other reasons to do something that unprovoked. :)

10.14´s main features seem to be a dark color scheme, the option to separately select an accent color, and that screenshots now can go/stay in RAM/clippoard.

i have all of that since MacOS 7.6 - or in other words: since 22 years.

most other new things are releated to "iphone", "stock exchange" or "apple store" which do not exsist in my household, or are simply a reintroduction of features which were already present in lion and mountain lion but then were stolen from us with 10.9.

the usefulness of metal 2 for composing music has yet to be proven, and while it might theoretically be great for video people, it is probably not so great for GL programmers atm.

when 10.15 comes out, which will ban 32 bit code, 10.14 might have a point, but compared to 10.6 it does not.

-110

Tj Shredder's icon

<when 10.15 comes out, which will ban 32 bit code, 10.14 might have a point, but compared to 10.6 it does not.>
Well, with 10.6 I would ban the internet, but as Max 8 has a minimum requirement of 10.11 and needs a connection every 6 month to check if the authorization is valid it might be a bit too dated...
I know you still run 4.6...;-)
At the moment 10.11 and 10.12 have a good point. 10.13 brought the introduction of APFS (For quite a while we can happily live without) and might be even less stable than 10.14.... I will wait quite a while before I even would start to test it. Too much precious software running here...

Roman Thilenius's icon

yes of course, if you always want to the latest software, you can not use an OS (and hardware!) which is 10 years old. it is more clever to combine things the other way round .

but when talking max, max7 for example - which was the newest version until last week - works just fine on 10.7 (and i think it should on 10.6 too, which is far more lightweight)

I know you still run 4.6...;-)

actually i develop mostly on 410, and a bit of 633.

these are the only versions i legally own - and OSX PPC was completely unusable for multimedia anyway IMO.

sometimes i am amazed how most max4 things still work in later versions. and i really hope it stays like that with max 8 (which i cant really test right now because i dont have the OS for it)

Ben Bracken's icon

We've released Max 7.3.6 for Mac only:
https://cycling74.com/downloads/older

This should fix the authorization/CEF-related issues on TouchBar MacBook Pro running Mojave. All other Mac users can remain using Max 7.3.5, as there are no other changes.

Arabrab's icon

Nice gesture.

Dimitri Sijperda's icon

Upgraded to Mojave.. started Max8. Crashes. Checked the internet, and now I know why. I guess I'll just have to wait.

Joshua Kit Clayton's icon

Actually, we currently have no open issues with Mojave and Max 8. Could you please contact support with your crashlog and support info. Thanks!

Dimitri Sijperda's icon

hi! Ik checked again, now it works... Mojave & MAx8... Maybe it was a Reboot I did, or a glitch in the Matrix. ☺

Dimitri Sijperda's icon

Got it, it's when my AirPods are connected! I'll send you the debug info.

Tj Shredder's icon

Air Pods? That expensive toy you'll definitely loose while running? (My ears have a form which spits out any Apple ear plug always...; - )

Annette Brosin's icon

Any chance my Max 5.1.9 will work with Mojave?

zzz900's icon

to everybody telling people that it´s their own fault if they upgrade the OS early - my story: macbook pro late 2012 not working anymore. repair not cost effective. had to get a new macbook pro - it comes with Mojave. checked if I could downgrade but if it works, it looks like a hassle and time consuming, time that I don´t have in the middle of a production.
so am I stupid for upgrading to mojave that I didn´t want in the first place? el capitan was running bomb proof since years for me.

zzz900's icon

I´ve installed max/msp 7.3.6: max authorization window opens, but at first couldn´t type my username and password or click, no effect. clicking on "Continue" did work with an error statint that the username is not correct or something like that.
BUT: then typing worked, entered my data, logging is fine, max 7 authorized on my new laptop.
thanks to cycling for fixing it!

Daniel Martinho's icon

Hello,

Max 7 is not running on my iMac 2014 with 10.14.6. Already tried Max 7.3.5 and 7.3.6. Thanks for the help!

Klangschmied's icon

Same problem here.
I am in contact with cycling support, they try to find a solution. If you need v7 64 bit, you can strip the 32 bit code with this command (if you have installed Max v8, rename the Max v7 to Max7 and you get a Max7-64bit version, this will start, at least on my computer.
ditto --arch x86_64 /Applications/Max7.app /Applications/Max7b64.app

But the 32bit version still crashes, but I needed it for 32bit externals.
Anybody have a solution?

Daniel Martinho's icon

Thanks, KLANGSCHMIED!

Changing the name file did not work (I don't have Max8, but I do have Ableton Live 10 with Max4Live). The command to change to 64-bit worked. Thanks!

Klangschmied's icon

good. The renaming of Max to Max 8 (or Max 7) is only needed when you install Max v8 and Max v7 in your application-folder....because installing Max v7 is installed as "Max" and Max v8 is installed" as "Max". If you don´t rename one Max app you will overwrite it...

Jorge Sad's icon

I' ve read the first comment in this thread

" Max 7 is not fully compatible with Mojave, and as such we recommend that users wait to upgrade to the latest Mac OS (10.14) until we are able to fix the issues we are seeing.

Thanks for your patience while we work on this!"

from september 2018 , Now almost two years later max 7 is not working with Mojave at all.
crashing all the time.
Do I have other solution than buy Max8 ?

Source Audio's icon

Max 7.3.6 came out long before apple updated mojave to 10.14.6
Max 7.3.6 is I believe last version of Max 7 that we are going to see.
There was enough time between 7.3.6 release and 10.14.6 update
to read what apple is planning to do to OS, and to decide
if one wants to keep using max 7 and so stop updating the system.

FR's icon

Hello,

I'm having to juggle between old and new software and need to update to Mojave (10.14.6) - can anyone confirm if they have managed to get Max 7.3.6 to work with this OS? I've read conflicting accounts in different places and it would be great to clarify before doing the update.

Thanks so much!