Ableton Forum

i dont own a launchpad, but following the live object model you can learn how to listen and send feedback to the LP

then send each row of buttons to the multisliders

tw1nstates wrote:What does a colour synth do?

How do you play them?

I am a bit confused by those videos. .

features explains everything

ayanami wrote:hey glitchrock and zalo, you don't know....

you got angry very fast, over something very silly

did you ever think that maybe i was half joking?

especially since the entire post was quite obviously a joke

probably in person our sarcasm wouldnt clash and we would be the best of friends!!!!!!!

try not using cracked software, it makes your system much more stable. And the award for dummest post of the year goes to... Just got back from my vacation and it's nice to have a good laugh, thanks! trying to get yourself in the running? jkjk seriously though, alex.the.forge, we are on to you, and...

im going out on a limb and saying that the track arm buttons are midi mapped, along with scene up, scene down, and each of the track play buttons

and that blank midi clips are already set up in the tracks to determine record/loop time

you could give the impulse sequencer launchpad support

or at least grab something else with launchpad control and hack it together

www.maxforlive.com is a great learning tool

play in session not arrangement

yeah, there has been talk about it over on the jazzmutant forums for a few weeks, go over and check it out

there is also bigger and better talk of live template editing to over come the memory limits

maybe its just me, but the loop_start seems like a much simpler way of finding out if the clip is looped a loop start point of .000001 doesnt effect anything except knowing whether or not it is looped <pre><code> ----------begin_max5_patcher---------- 454.3ocyU9sSCBCEF+Z3o3jd8bgV2lLuSeMLlkBT2pBsj1yz...

live has been much more stable since i upgraded to SL

i only can crash live now doing very specific, very documented things

but in my normal work flow, no crashes

i havent worked with javascript really, i assumed that the global quantization would effect how it works

time wait doesn't matter (with a i7 + 4Go RAM, w7 64 bits, it takes around only 1 minute for that. but the point is: it is a workaround. and it should be natively implemented. i dont understand how the computer speed changes that since the time it takes is all based around bpm, 35 clips at 140 is a...

it is too much artificial for me ; it is a workaround too. the "less" artificial would be to start all clip one time, grab and store the status, and voilà. (broc suggested it too) i dont know, maybe its me, but the idea of waiting 5 minutes for it to play through all the clips in the live...

the thing with max is that it really is pretty easy, just be patient, look around, learn what things do

with some testing and time you will get it working directly, im sure

sometimes i get to missing that little rainbow pinwheel, when i do i just open up live, throw ultra analog on a track and just keep opening and closing it til my little friend comes back to visit me!!!!!!