Ableton Forum

I open any device Max and Ableton closes unexpectedly.
I insatlled Java (http://www.macupdate.com/app/mac/39490/ ... a/download) I uninstalled and installed by resetting the preferences, I made sure to install Max dismantling the .dmg installer of Ableton for not create errors.....nothing.
I do not know what to do, please help....

tnx

What kind of computer are you using?

I am currently experiencing this exact issue on the 2015 Macbook Pro (The "Force Touch" one).

I was assuming it might be a compatibility issue with the 2015 MBP since it was just released, but if you're experiencing this issue on other hardware then maybe there's something else afoot.

I already contacted Ableton with my crash logs, so I'll make sure to post up any information I get back from them.

exactly!
I have a brand new mac 13 " with the new trackpad .
Also I have contacted support ... hopefully solve it soon.

Jiack Skipper wrote:exactly!
I have a brand new mac 13 " with the new trackpad .
Also I have contacted support ... hopefully solve it soon.

Interesting...

It seems like the newest MBPs just can't run M4L at all in its current state.


Hopefully they'll get it taken care of soon.

I noticed another thread in this forum that seemed to indicate that M4L is having a lot of stability issues. That thread was mostly talking about Windows instability but I would imagine that it's all sort-of related.

Appreciate you making this thread, I'll be sure to keep it updated if I find out anything.

Jiack Skipper wrote:I open any device Max and Ableton closes unexpectedly.
I installed Java (http://www.macupdate.com/app/mac/39490/ ... a/download) I uninstalled and installed by resetting the preferences, I made sure to install Max dismantling the .dmg installer of Ableton for not create errors.....nothing.
I do not know what to do, please help...

That's the correct version of Java and is the one I use on OS X 10.9 Mavericks, though I also have Oracle jre 1.7 installed (so far no max devices use that AFAIK).

Hmmmm, Interestingly I have Max 6.1.9 installed on Windows 7 where I only have jre 1.7 and 1.8 installed. No complaints from Max For Live when I added the Max Audio Effect Magnetic of the Dub Machines package. AFAIK none of my max devices use the java virtual machine in any way.

When I previously had only jre 1.7 on OS X 10.9 Mavericks I also didn't get the prompt to install a java virtual machine. That was M4L 6.0 though and I've been told from Cycling74 that for a while java dependency was removed from M4L, then put back because some users had some issues. On OS X 10.10 Yosemite I did get this prompt with Max 6.1.9, also after I installed jre 1.7.

I'm hoping for a 6.2 version that solves this java mess. Only when a device is installed that does use java should you be prompted to install a specific version of it. But it might be that it's only in MFL 7 they can do away with this. Currently java dependency is still there in Max 7 so could be years before this is improved.

There are Java specific objects in Max that let you code internally so that's why it's needed as far as I know.

stringtapper wrote:There are Java specific objects in Max that let you code internally so that's why it's needed as far as I know.

It's true that some max devices use java - the Max user could program such a personal device too - and therefore are dependent on it. But far from all devices use it or depend on it. According to Cycling74 support for a while java dependency was absent from M4L at the request from Ableton. This dependency is back however as there were some issues and that's what we have to work with until they improve the situation. I find easier to accept when I know why.

I'm not talking about Max For Live devices. Talking about the Java specific objects that have been in Max for years that allow one to essentially code their own externals using Java. That's a part of Max's set of functions. There are also JavaScript specific objects that let you roll your own objects with that language.

What I'm saying is that those objects are part of Max so their existence itself is what requires Java, not whether they have been implemented in a specific M4L device.

btw: none of the Ableton M4L devices use java externals (mxj / mxj~).

Best,
Christian

stringtapper wrote:I'm not talking about Max For Live devices. Talking about the Java specific objects that have been in Max for years that allow one to essentially code their own externals using Java. That's a part of Max's set of functions. There are also JavaScript specific objects that let you roll your own objects with that language.

What I'm saying is that those objects are part of Max so their existence itself is what requires Java, not whether they have been implemented in a specific M4L device.

Well, the fact remains that according to Cycling74 support java dependency was removed in M4L during a period. I assume it was deemed feasible to not require java for running Max For Live as long as those objects weren't called.

I just hope that Cycling74 is able to improve the situation when they have the chance. At the very least they could explicitly list java as a requirement as long as it is. It's still not listed for Max 7 nor Max 6.

I wouldn't say this is the most important issue, but this is likely bewildering for new users, at least on OS X.

Same thing happening here, 1 week old Macbook Pro 13" 2015 - Ableton crashing when I open any Max 4 Live device.

Isn't it more likely to be some issue with OS X Yosemite rather than some hardware issue? Yosemite being what new fresh Macbooks are running on.

So what versions of OS X Yosemite, java (all of them as they can be side by side), Live and Max For live do you guys with constant crashes use?

What does Crash reporter logs in Console say? (Please post extensive log files to pastebin.com or similar and link to these)

This is my crash report:

https://dl.dropboxusercontent.com/u/214 ... 09.1.7.alp

Jiack Skipper wrote:This is my crash report:

https://dl.dropboxusercontent.com/u/214 ... 09.1.7.alp

Thanks. However, I meant the OS X crash report that you'll find in the Console application in Utilities. Look under Crash Reporter and Ableton Live.

These bug report packs of the type that you linked to are for Ableton only I think. At least I don't know how to decode these binary files.

maybe this ?
https://dl.dropboxusercontent.com/u/214 ... -Pro.crash