Ableton Forum

Hi,
I'm just wondering if anyone else experiences crashes when adding a M4L device. I seem to get random crash when dragging a device into a project. I use allot of 3rd party devices but it doesn't seem specific to an device or device builder.
If you get no issues then still reply to the thread as that will be helpful in addressing the problem thanks.

No particular issue here.
i have the same M4L patch on all my sets and i haven't had a single crash for months.

I am crashing after doing a small hack to GranulatorII in which I only modify some mtof objects. It also seems to slow down my machine drastically when I use more than one of my hacked versions of GranulatorII.

Still on Live 8 32Bit / OS X 4GB, I'm used to sporadic crashes when modifying a Live set with many M4L devices or also memory-intensive devices like Looper. In that case, I tend to be in a "construction mode, precarious, don't worry" state of mind, as Live's after-crash file recovery is quite reliable and with (after loading) structurally unmodified Live Sets, it's rock solid. So to get from construction into that "now make music" state of mind, I usually save and restart Live.

Random crashes with random devices. Sometimes loading device crashes live 9. Start Live 9 again, load same device again and it's loaded - not crashing Live 9. Really weird. Latest live and Max here..

tecolo wrote:Random crashes with random devices. Sometimes loading device crashes live 9. Start Live 9 again, load same device again and it's loaded - not crashing Live 9. Really weird. Latest live and Max here..

This is how i would describe my problem. Interested to know what OS you use?

I'm PC win 7 64, but currently running live x86 & latest max, I've also been using beta of max & live.

Rosko wrote:

tecolo wrote:Random crashes with random devices. Sometimes loading device crashes live 9. Start Live 9 again, load same device again and it's loaded - not crashing Live 9. Really weird. Latest live and Max here..

This is how i would describe my problem. Interested to know what OS you use?

I'm PC win 7 64, but currently running live x86 & latest max, I've also been using beta of max & live.

Not using betas. Currently latest official x64 Live 9.1.3 and Max 6.1.7 - but i had same experience with older versions..

Win 7 64 bit sp1

Not sure what the problem is but i don't like it since i can't trust it. Random crashes, not showstopper but they are most definitely there. Don't have such problem with other 3rd party plugins and i have a lot of them..

Had a crash last night with j74 progressive. Had a clip running and while holding down the mouse button to adjust a knob in progressive my entire box just rebooted on its own. Sent the report to ableton. So this was a bit more than just a crash, it was entire reboot. No blue screen or warning

win8.1 x64, live 9.1.4 x64

Will be filing a report for this one. Twice, convo pro has crashed today loading, but it's not something that happens every time.

Yes that is strange behavior, sometimes it doesn't work you reload it and it's working - like i said not showstopper but definitely not a pro app on which you can rely on stage. Until they resolve such weird behavior.

Well if you're using convolution reverb on stage, you're rolling the dice anyway. Quite the CPU intensive process convolution is.

just had 4x crashes in a row loading polyrhythmus. Was loading fine before & now after.

I usually get weird random crashes with third party devices, sometimes when loading the device, and sometimes if I delete it from the track. Last time it was with K-Devices Ext2, I loaded it onto a track after Sugar Bytes Turnado and it caused a crash. Recovering the set each time would cause the same crash - had to delete the device from its location, reloaded the set and re-save it, then restore the device.

Live 9.1.4, Max 6.1.7 - both x64

MFL will definitely be more stable in 32-bit than 64-bit. 3rd party externals (bits used to make MFL devices) often require a 64-bit updated version.
A lot of MFL devices were created using 32-bit externals. If the externals crap out, it'll be coupled with an error message in the Max window (right-click device title bar). Or in some cases a crash.
Stock devices and devices using only core Max Objects will be more stable in both 32 and 64 bit.

hoffman2k wrote:MFL will definitely be more stable in 32-bit than 64-bit. 3rd party externals (bits used to make MFL devices) often require a 64-bit updated version.
A lot of MFL devices were created using 32-bit externals. If the externals crap out, it'll be coupled with an error message in the Max window (right-click device title bar). Or in some cases a crash.
Stock devices and devices using only core Max Objects will be more stable in both 32 and 64 bit.

Can you be a bit more specific? It seems you know a bit more on max devices then us. If everything you said is true then it's just not fair especially for 64 bit users. And it is not nice that we can't enjoy max stability.

Is there any official info on this? Are they working to resolve these issues?