Don't be amazed that you find bug reports in the bugs section. That is what it is for. You'd be amazed at how stable M4L actually is. Just some small examples of the types of code people are executing for their projects: JavaScript, processing, Max scripting, C++ and homemade externals.3phase wrote:hoffman2k wrote:Not a specific device, but the one you mentioned would be an example. My Clip Mapper too.glitchrock-buddha wrote:Hey Hoffman, what is the M4L device you are referring to? Is it the one that assigns midi cc's to Live device parameters and records the cc's?
It uses an object called live.remote~ which allows us to control almost any device parameter at audio rates. In other words, faster than MIDI Scripts to update a parameter in Live.
So session automation is half there. They still have to solve the problem about how to handle absolute versus relative envelopes, but the ability to hijack a parameter for that purpose is now there. Brought to you by Cycling 74 and Ableton. I can't wait for Live 9. Fingers crossed!
?? really? and this runs stable? not so long ago, a few weeks or so, L8.1 was crashing all over just without max..
and with max in the backround dealing with this deep inside clipautomation stuff its getting better?
besides... you have to pay 300 euro to get clipautomation than.. might be even worth it :-/
but sorry.. how can such a thing be stable? just have a look in the bug forums... i dont appears to be a stage option wright now.. at least not for the users that have issues with L8..
in case there are really users that have none...
Another reason why you shouldn't discredit M4L. We're doing all sorts of crazy shit to try to make Live crash. If it crashes it needs fixing too.
Some M4L are having issues with Live, but so are you. And you had them before M4L came out. They probably did too. Some things are just more noticeable because of M4L because we can now make built in analysis tools if required. M4L crashes too, but not as frequently as you would hope it to be.