stability

[ionone]

Hello
I've purshased Live because i tested a lot of DAW and it was 1) the most innovative 2) the most poweerfull 3) the most stable

the third point is the most important for me as i use it professionnally, so i can't have a crash in the middle of my work. i installed Max for Live yesterday and tested some plugins. Live crashed when i tried to load one of them. So i guess Max has been made by a different team (cyclin74) as is not as stable as Live.

but is there a way to gain the stability of Live within Max ?

thanks

Jeff

[Valiumdupeuple]

Which device crashes Live ?

[ionone]

Which device crashes Live ?

crashes happen when: i load some MAX MSP plugins (only official plugins) or when i load a lot of MAX MSP plugins then save the set and reload it : big crashes. So i cannot use MAX MSP and it's a big deal because i purshases Suite to have the power of MAX MSP.

Live is so stable i can't understand why they let something so unstable in.

edit: oh salut la France

[chapelier fou]

edit: oh salut la France

Salut,

did you make sure that you have the latest versions of both max, m4l and live ?

[ionone]

okay i thought i had the latest i'm on 9.06 and i'm downloading the latest. Max is the latest as i donwloaded it from the site.

i'll try the new version and get back to you

but i've looked the bug fixes and there is nothing about my problem

[re:dream]

Yup, it seems to be different from device to device in Max

For example on my system the Rye delay crashes Live reliably, time after time. No idea why. Other devices never cause any difficulty.

[S4racen]

Always use 64Bit, some m4l devices can be a bit of a RAM hog on start up (with low CPU usage after that) so can give you problems if your running under 32 bit architecture...

Cheers
D

[ionone]

Always use 64Bit, some m4l devices can be a bit of a RAM hog on start up (with low CPU usage after that) so can give you problems if your running under 32 bit architecture...

Cheers
D

i use 32 bits because most of the plugins i use are 32 bits...And i don't want to get rid of them, and there should be a programmatical way to counter this anyhow

Jeff

[S4racen]

Always use 64Bit, some m4l devices can be a bit of a RAM hog on start up (with low CPU usage after that) so can give you problems if your running under 32 bit architecture...

Cheers
D

i use 32 bits because most of the plugins i use are 32 bits...And i don't want to get rid of them, and there should be a programmatical way to counter this anyhow

Jeff

Sorry but no.... MAC 32Bits will address 4GB of RAM the Windows equivalent will address 3GB after that crash....

You'll either need to upgrade or deal with it?

My target for all devices and templates is to work below 3GB.....

Cheers
D

[ionone]

okay updated Live to the latest and i got still crashes with official devices... randomly, one plugin crashes when i load it. (most of the time near the f... when i load alphabetically)

how come it is so unstable???

crap crap crap

can't use Max MSP or only in sound design where i don't care for crashes

EDIT : i'm on windows not mac so i have a 64 bits OS but using 32 bits software.

[S4racen]

You need to register the crashes with Ableton and send them your crash logs.... The forum isn't monitored for that kind of thing...

Cheers
D

[clydesdale]

I occasionally have crashes when I'm trying to both edit and use combinations of devices but nothing consistent where it crashes every time. I'm running 32bit Live on 64bit Win 8.1.

If you post a list of the devices that you're using that cause the crash I'd be happy to at least try them out and give a point of comparison.

[ionone]

I occasionally have crashes when I'm trying to both edit and use combinations of devices but nothing consistent where it crashes every time. I'm running 32bit Live on 64bit Win 8.1.

If you post a list of the devices that you're using that cause the crash I'd be happy to at least try them out and give a point of comparison.

thank you for that

when i test the max plugins, i load from A to Z, and as i said before it's usually arounf the F.. that it crashes. But i tried all F.. plugins independently and they don't crash.

Cycling 74 has to check their pointers because there is something wrong in the programming of MAX MSP 4 Live.

Live doesn't crash AT ALL, even with big configurations where there are multiple plugins and when i duplicate heavy tracks or stuff like that, Reaper that i was using before was crashing, but Live holds still, kudos to the devs! Only MAX MSP i can't use ;-[

Jeff

[clydesdale]

I created a Live Set and loaded every single Max4Live device that I've got, all at the same time (about 40). No crashes but FWIW it showed around 6-10% load on all 8 cores just sitting idle.

[wehkah]

Some of the buffer and sample dragndrop using M4L patches crashes randomly. I think this is caused by a memory/buffer issue when patches not programmed carefully. Same with crappy VSTs. You can use Reaktor for example to crash Live but it's not a Reaktor issue at all, its mostly caused by crappy ensemble programming again. So i think this is a general "quality" related issue of the plugins you use.

PS: I recommend to use Live 32bit which is most stable.

cheers
T