Max for Live is full of bugs!!!
I am trying to export all my work from the max environment to max for live, but I am noticing that Max for live is FULL of bugs. If you want to do little things is fine, but if you want to use predominantly max but in the ableton live environment, it is impossible! Unfortunately...the system crashes every 3 secs....
I went for this solution
https://cycling74.com/tutorials/rewire-essentials-1-from-maxmsp-to-your-host/
.
So, basically , rewiring. I think that until the Max for Live will be that unstable, this would be the best option.
What do you think about it?
All the best
elisa
maybe you should describe each bug, see if they are actually bugs or things that are meant not to behave the same way in max/MSP and in M4L. Apart from Rewire, things like SoundFlower or Jack, could try a simple udpsend M4L device to send/receive things to/from Max, etc.
vichug, which is more efficient for sending between the 2, rewire or udp? thx
i'm thinking one obvious advantage of udp is being able to talk to a remote host also? rewire is only on the same machine correct?
Elisa, are you on Max6 or Max5? The devs have been working on the Max 6 stuff for stability in the past several months. I don't have many problems when I run it in Max 5. Are you on the most current version of Max? Can you reproduce the crash? (and if so, please file a bug report! The C'74 folks are pretty responsive when they have actionable information)
Hi !! I have remark one thing about max for live (I'm using it since the beginning). When you do a patch or a project for example in Ableton live 8.3 the patch will not work as well in another version (i.e live 8.4). For example I had a visual show with m4l friday my patch was crashing Ableton a lot... But at home with my old Vista computer where the patch was produce my patch is 99% stable.... So I don't know if i'm right or not but that's a serious limitation....
Ben
If you keep getting these crashes, I'm pretty sure the dev team would appreciate a bug report especially with an attached crash log.
The stability of programs depends on a lot of factors: what your patch is doing, how hard it's hitting the scheduler, etc., and it's pretty rare that you can't do anything about it as the programmer, though it frequently means figuring out a different approach than the one you first had. Not trying to shoot the messenger here, but it's also really difficult to help without any further information or example code. Anything you can post helps.
@leehu : i don't know much about rewire, but it seems it handles both audio and midi messages, along with other things possibily, and this in a kind of closed-source way, and it needs to have one application as "master" and the other as "slaves". It might be like having a vst host and several vst plugins ? and a littel annoying when several applications want to be the master, but i guess in the end it's ok. Anyway, as far as i can tell, udp is more flexible, you can send anything via udp in the way you want, but you can't transmit audio so you'll need soundlower or jack in addition to this, and you need something to receive and decode you udp informations (a m4l patch would do in this case).
I have to say I'm not that happy with M4l either - and I've been spending about 30 hours a week programming Max / M4L / Live over the past 5 months.
When it works it is incredible but I too have a lot of crashes (I got so used to it I forgot I could submit a crashreport - which I did last week)
A lot of what I do is API calls: the core of my project is creating a customised interface into LIve with exactly those controls that I need at my fingertips (and feet) using and Ipad and a softstep. I always assumed that because I access the API a lot it can cause problems. Who knows. All that said, when my patches are finised and I can keep the M4L instruments closed, it works really well: the problem is only when editing, so I'm reasonably OK about gigging with patches that I developed and tested.
What drives me completely nuts (NUTS!) is the fact that the M4L devices behave completely differently when open for editing as opposed to being closed inside live: it's definitely adding 305 - 40% to the time it takes to develop stuff.
All that said, I'm still loving it and am looking forward to a gig next week to roadtest it...
the main problem, imho, is pure Live related.
indeed, rewire in Live sucks terribly.
let's hope for Live 9
haha, glad I am not the only one with M4L issues.
I started in M4L, and have recently moved to Max... it is WAY more stable. I found in M4L I was waiting for the editor to reboot following a crash more often than actually doing any Max-Programmin!
Oh the love/hate relationship I have with Ableton!