Assuming is not a complain more a question.
It is not a patch per se, but more an operative mode of criss crossing things and getting out without having a developing team behind.
Let us say in the midst of developing and testing one finds out that a certain standard m4l object will make Live crash if in the set there is X external plugin. Take out that object the set does not crash.
Where should be the problem reported?
Is it a problem?
Where does this category go?
Have a look at this device I posted some time ago, its really basic stuff from signal proz POV.http://www.maxforlive.com/library/device/130/reverser
I got some users reporting the same thing, on site and via PM.
Probably needs a giant upgrade, yes, but I am more curious on how m4l developers will organize from a tool point of view.
luckily there is the community.
Considering the point that one wants to develop on a more complex scale and that m4l is a cross platform thing how do Ableton and cycling refer to this matter?