Ableton Forum

Hi Ableton Live users! Has anyone have this happen to them? I'm trying to run Ableton Live 9 (still need to use it for certain plug-ins that are 32 bit), and all of a sudden I'm getting this message:

Live cannot be opened because of a problem.
Check with the developer to make sure Live works with this version of macOS. You may need to reinstall the application. Be sure to install any available updates for the application and macOS.

I changed nothing, didn't add any new plug ins or anything. This literally happened out of the blue.

Details: I'm using a mid-2010 MacBook Pro 13-inch with an SSD drive. After this happened, I swiped the hard drive clean, reinstalled High Sierrra and a Time Machine back up. I was able to open Live 9 once after that, but now always getting this error message again. I tried disabling plug-in scan on start up. No dice.

I reinstalled Live 9, the latest version and an older one and it happens with both.

UPDATE: I just tried a 64 bit version of Live 9 and it opened! This still doesn't solve my problem though, as the plug ins I need to use are 32 bit.

I also have Live 10 on this very laptop and there's no problem there. And Live 9 has always worked fine on this computer and I have no idea why this is happening now.

Any help greatly appreciated!!

SOLUTION!!

Turns out Mac once again did something shady and made my laptop only use 64 bit apps. Thanks Mac for another cluster fuck.

Anyone else with the same issue, go here for reason and solution:

https://developer.apple.com/forums/thre ... #639998022

Happened to me too. I am on OSX Mojave 10.14.6 using Live 10 mainly, but I also have some projects in Live 9 32 bit.

Thanks for the link to the fix. Hope Apple fixes this in a future update for Mojave.

Lemmike wrote: ↑

Mon Oct 12, 2020 3:13 pm

Happened to me too. I am on OSX Mojave 10.14.6 using Live 10 mainly, but I also have some projects in Live 9 32 bit.

Thanks for the link to the fix. Hope Apple fixes this in a future update for Mojave.

Glad I could help! I wouldn't count on Mac fixing anything though. Seems that they, and pretty much all software companies, want to force 64 bit down people's throats.

BerlinGoodMan wrote: ↑

Mon Oct 12, 2020 5:48 pm

Glad I could help! I wouldn't count on Mac fixing anything though. Seems that they, and pretty much all software companies, want to force 64 bit down people's throats.

For good reason. 32bit is has been on the way out for 15 years and has been mostly dropped by devs and users in the last 8 years. 32bit is limited in memory and architecture so it’s time to update your softwares and plugins and cull all the ones that do not have a 64bit option which apart from a few freebies should be almost none.

jestermgee wrote: ↑

Mon Oct 12, 2020 9:15 pm

BerlinGoodMan wrote: ↑

Mon Oct 12, 2020 5:48 pm

Glad I could help! I wouldn't count on Mac fixing anything though. Seems that they, and pretty much all software companies, want to force 64 bit down people's throats.

For good reason. 32bit is has been on the way out for 15 years and has been mostly dropped by devs and users in the last 8 years. 32bit is limited in memory and architecture so it’s time to update your softwares and plugins and cull all the ones that do not have a 64bit option which apart from a few freebies should be almost none.

I see your point. I just don’t appreciate a mysterious update being the reason that I’m forced to figure out why plug-ins mysteriously stop working, and thus requiring me to update.

Mac asked me to update software for my mobile devices after I reinstalled my system software. Unbeknownst to me, this copied over an old 32 bit MobileDevice.framework file with a 64 bit one. Somehow that rendered all 32 bit software unusable. Thank you, Apple.

The link I provided above provides more detail..