Mapping problems w/ M4L
I am a lay man when it comes to max. I just downloaded the 30 day trial to try it out and see if its worth buying. So far it seems like there is tons of potential and I’m very excited about delving into the world of m4l.
However, I’ve been having a lot of trouble with many of the patches i’ve been downloading. Some of the plugins are unresponsive and difficult to make sense of and others use 97% cpu power when I simply try to automate a paremeter. Things of this nature… I am using Live 8.2.1 I believe. Is there a reason why I am experience such difficulties?
One major concern I’m having is that I can’t seem to map many max devices. IF they contain the drop down box lists than I can do it. I can always find the parameters that I want to assign, it recognizes them and its fine. But many plugins like mapulator don’t have the drop down boxes and just have a "learn" or "map" function. What i read about them just tells me to select the paremeter I want to assign in ableton and then click learn or map. But when I do that nothing happens for me. Am I missing something here?
Hi, I’m not sure about the 97%cpu business but I’m pretty sure your trouble with the mapping is because you need to give the UI objects that you want to map an individual scripting name. If you look at the inspector for each dial, slider etc… you will be able to give them a long and a short scripting name. So far as I can recall you only need to provide a short scripting name. You can name them anything you want but it’s best to use something meaningful like ‘cutoff’ rather than ‘dial1′ for example. Having said all of this it seems odd that you are downloading M4L patches which don’t already have scripting names for the UI objects hmmmmm…
I do not know what a scripting name is and I have never heard of UI objects.
Mapulator seems to be a well-known device and is released by DJ tech tools. I’m pretty sure they intended this plugin for ordinary people and not people who know how to program max devices. They say that all you have to do is click on the parameter you want to map (so its "the last parameter highlighted in live") and then click the map button and it should appear in the list as mapped properly. I figured this was the way most m4l devices with a map feature worked. I don’t understand why I have to understand esoteric terms just to get a very popular plugin to function as they say it does.
Why can’t anyone help me with this??? I mean this seems like one of the most fundamental possible things to have a problem with. Is my computer broken or something.
one of the problems is you are using live 8.2.1. it clearly states that current M4L must use Live 8.2.2 or higher. i thoroughly recommend using 8.2.8 or 8.3.
this will solve the mapping issue (as it was not available in this manner before 8.2.2), providing your max version is based on 5.1.8 or 5.1.9. (note, do not use max6 demo yet – this will not be used by live until live9 i guess).
Mapulator requires these updates. remember though, it is a third party device, so if you have specific issues with it you should ask via their forum.
and you have correctly chosen to demo maxforlive in live after installing all this?
hope that helps.
Wow.. I mean that explains it. I thought it might be something to do with the version of live.
but what do you mean "it clearly states"? what clearly states.. I’m using 8.2.1, and the trial of max (including max for live) that I downloaded stated that it requires "Ableton Suite 8 or Live 8".
There have been a lot of Live updates since 8.2.1. Do yourself a favor and update.
Also, there is a forum for Max For Live-specific topics on this board.
Forums > MaxMSP