Right then, i’ve tried most things, and probably a few i shouldn’t….
I now desperately need to disable the scene launch buttons, the 9 stop button (which doesn’t seem to group together with the other and the cue level knob….. I wouldn’t mid disabling the master volume control but i don’t seem to be able to observe it value for some reason, which is annoying as i’ve created a neat little internal pick up mode for it…..
Next thing is to be able to seperate the different banks of the Track control (Pan and Send knobs) so that i can access the pan bank and leave the rest as they are… but that’s for another day…
Any help greatfully received!
FIrst part sorted, couple of days work left…
head over to max4live.info to see how it’s done, props to MC again!!
I got the zip from max4live.info.
Is that all there is at the moment? It says lesson 1, but there is no tutorial? yet???
Or did I miss something?
Have you seen the video….?
No where is it???
For whatever reason it was not showing up on my desktop computer where I have been for the last few days.
Anyone figured out how to disable the scene launch buttons permanently yet without it effecting the button matrix?
And any idea Cycling people when the control_surfaces will be updated in the manual to have some form (any form) of documentation?
ps no word from Akai on any of this considering they sold the unit off the back of that it’s easily editable with Max4Live!!
Hey I work for Akai and I’m the max guy there. Control Surface stuff is handled by the Live API, all out controllers do is send midi notes. We have no special knowledge of the Live API. Where did you get told that it’s "easily editable?". It’s easily editable in MAX, but the Live API stuff is not easy, especially if you only know max as a programming language. It’s basically the lack of documentation that is the real issue, and like I said, that’s up to Ableton and Cycling, not Akai.
Interesting, i thought it was a joint project between the two companies? Obviously the extend video promoting it and how it could be edited with Max4Live (i may have misheard "easily") were put together with the best intentions…
Anyways enough of the semantics, if that;s Akai’s answer i await eagerly the Ableton and Cycling answer….
In the meantime i’ll work on making my patch midi mappable and ignore the apc control surface stuff, pity as i’ve invested hours of time into it so far….
Yeah when I made that video I did it in MAX, not MFL. I thought it would be better and indeed it is I’m right now doing something I could not do. The LIve API handles the control surface stuff, and that’s all Ableton, and from there what they share with Cycling. But it’s worth it! Dive in, I had about 40 hours invested in just the max patch and I’m about 30 Hours in on the MFL now. Just go through the CS Step and try to understand it. From there you can get help on the forums.
Hmm.. as far as midi only goes though if it’s not audio stuff that you’d have to do in MAX 4, as a vst, you may be better off sticking to just Max as MFL isn’t nescessary. MFL is def better for elegance and I think stability (for example if max crashes live still sees your apc40)
The controller was a joint project between the two companies, but the LIVE API is not. The live API handles the Launchpad too, which you can be sure was NOT a joint venture between Akai and NOvation :)
Yeah, thanks but I’m not about to shell out more money for max now on top of what ive already paid out and invested time wise, having beta tEsted from the start I don’t think it’s unreasonable to actually have documentation by now! This isn’t me being hissy, I’m delighted with what I’ve done so far, I just need more information before i can go much further in the direction I planned….. Back to bomes for the meantime!
Forums > Max For Live