So I've spent this evening coding a thing in ChucK for talking with
Ableton Live. And I think it's pretty cool.
I will clean up the code tomorrow and you all can play around with it.

For now you can just watch me play with it:
http://www.youtube.com/watch?v=dPKY5-pLKVU

BTW: sorry for my late night bad english :D


Update: latest version(2007-06-21) later in this thread 
(http://forum.monome.org/topic/570#6472)

looks awesome.


please share, i've been looking into chuck to build something very 
similar.

excellent performance/demo.

ableton lovers will praise your name! it's the one thing we've been 
really missing all this time.

and yeah, don't hold back sloppy code. let someone else clean it up ;)

excellent work ahlstrominfo! watching this video & seeing brians (chuck) 
life i've decided to delve into chuck.

looking forward to this...

tehn wrote:
> and yeah, don't hold back sloppy code. let someone else clean it up ;)

Just had to sleep for a few hours :D
Please feel free to modify the code and make it more beautiful than it 
is. It would be cool to be mentioned in your modification also, but not 
needed.

For this to work on OSX I had to use separate midi-ports on in and out, 
otherwise I get some kind of feedback-loop of midi messages going 
berserk.

If you want Ableton to work somewhat like mlr, but not like mlr, you can 
do it like this.
1. Add a loop and turn off looping on it (loop-switch).
2. Copy the loop 3 times in the same track.
3. Set start and end position in the clips. Like every fourth.
4. Set Follow action on the clips to "next".
5. You may also need to fiddle with "Follow action time" and 
"Quantisation".
6. Connect monome-buttons to clips via midi. Press first button and se 
the magic.

do you used the options.txt to get midi feedback from ableton? i not 
really tried to work wth the options.txt and is wonder where these midi 
feedback notes are going(on wich midi port) where can i set this up?
a tutorial how to setup mdidfeedback in ableton would be cool.

cheers
malte

Since Live 5.x midi-feedback is turned on by default. Atleast that what 
they are telling me.
The feedback info is sent to the selected midi-outputs in Ableton Live.

To get MonoAbleMe to work you need a couple of internal midi channels.
In OSX you use "IAC Driver" which is built-in. If I remember it 
correctly theres and app for Windows called midi Yoke or something 
similar.

> The feedback info is sent to the selected midi-outputs in Ableton Live.

but an audio track has no midi out to select. where do i select these 
outs? lets say i have an 1 bar audioclip on channel 1 in live. when i 
trigger these clip i want feedback when the clip starts on midi yoke 
1(PC) how...

cheers
malte

malte wrote:
> 
>> The feedback info is sent to the selected midi-outputs in Ableton Live.
> 
> but an audio track has no midi out to select. where do i select these 
> outs? lets say i have an 1 bar audioclip on channel 1 in live. when i 
> trigger these clip i want feedback when the clip starts on midi yoke 
> 1(PC) how...
> 
> cheers
> malte

You don't select the midi out on the track. You select it under 
preferences.
Ableton send feedback only on clips that have midi connected to them.

> 
> You don't select the midi out on the track. You select it under 
> preferences.

ok, i did that i select yoke1 as remote(?) out

> Ableton send feedback only on clips that have midi connected to them.

connected in terms of "learned a midi cc" or do you mean only on midi 
clips?

malte

is that documented somewhere?

malte

Cool, ahlstrominfo!

I've not managed to get it to work on my computer. I dont know how to 
set up midi ports in chuck. From looking at the code I suspect it works 
a bit like my max/msp patch:

- osc messages from monome (button press/release) are converted to midi 
note messages to ableton live
- midi notes from ableton live are converted to osc messages to monome 
(to set lights)

You can download a beta of my patch here:
http://hornquist.se/monome/lio_beta.pat

I'm very new to max/msp, bought it some days ago, so sloppy code 
warning! :)
lio = live input output. or something. I use midi yoke on my pc to 
bridge between the two programs.

A max/msp-related question: what is the difference between .pat and 
.mxb?

malte wrote:
> 
> 
>> 
>> You don't select the midi out on the track. You select it under 
>> preferences.
> 
> ok, i did that i select yoke1 as remote(?) out
> 
>> Ableton send feedback only on clips that have midi connected to them.
> 
> connected in terms of "learned a midi cc" or do you mean only on midi 
> clips?
> 
> malte

Live only sends back midi on things that been learned in Live, in 
midi-learn-mode.
Don't know if it's documentet but its what I figured out when coding 
this app.

A somewhat dizzy video about the MonoAbleMe setup:
http://youtube.com/watch?v=RIQeM6pOmXU

At the end of the video I made a demo playing a few samples. If you only 
want to view the demo you can do that here:
http://youtube.com/watch?v=awMgevUjx8g

this is great!

with the follow actions its like mlr.

fun stuff. good job. thanks.

yea, i got it now(it was to simple :)). even with the normal max midi 
patch its great to have that visual feedback.
thanks for the tips.

cheers
malte

thx for putting the time into both programming and the video tutorial 
ahlstrominfo.

/a

actuel wrote:
> thx for putting the time into both programming and the video tutorial 
> ahlstrominfo.
> 
> /a

Your welcome, it was great fun doing them both :D
Hopefully someone else but me will have need for them, I know I have and 
I'm enjoying every second using it now.

There's no serialio for xp, how do I get this to work? Everything else 
seems doable, I got chuck running, midi yoke and all seems to work fine.

dogblessyou wrote:
> There's no serialio for xp, how do I get this to work? Everything else 
> seems doable, I got chuck running, midi yoke and all seems to work fine.

serialio and _40h_serial.mxb are interchangeable.

dogblessyou wrote:
> There's no serialio for xp, how do I get this to work? Everything else 
> seems doable, I got chuck running, midi yoke and all seems to work fine.

Hi, could you tell me how you set your midi ports in xp?? I have open 
Ableton, max/msp with 40h_serial.mxb and chuck with monoableme.ch and 
doesn't work. I am trying through midi yoke as well and i hearing a 
piano?? weird

tehn wrote:
> serialio and _40h_serial.mxb are interchangeable.

Aha, I run ChucK AND max/msp :)

I don't get the lights to work. Otherwise it works fine, like 
lio_beta.pat also does. Can anyone spot the error in the attached pic?

hhat wrote:
> Hi, could you tell me how you set your midi ports in xp?? I have open 
> Ableton, max/msp with 40h_serial.mxb and chuck with monoableme.ch and 
> doesn't work. I am trying through midi yoke as well and i hearing a 
> piano?? weird

If you're hearing a piano the signal must have reached Live...

You can see my setup in the attachment of my post above... maybe of some 
help. Or try the lio_beta patch by jah, it's a bit easier to set up the 
midi ports right.

dogblessyou wrote:
> tehn wrote:
>> serialio and _40h_serial.mxb are interchangeable.
> 
> Aha, I run ChucK AND max/msp :)
> 
> I don't get the lights to work. Otherwise it works fine, like 
> lio_beta.pat also does. Can anyone spot the error in the attached pic?

barf. we really need an xp version of serialio.

maybe chuck will have an rx/tx lib soon? that'd solve the problem 
slightly.

i honestly can't spot a problem.

have you tried running the 40h_life.ck patch with _40h_serial.mxb? 
wondering if it's a communication problem between max and chuck?

tehn wrote:
> barf. we really need an xp version of serialio.
> 
> maybe chuck will have an rx/tx lib soon? that'd solve the problem 
> slightly.
> 
> i honestly can't spot a problem.
> 
> have you tried running the 40h_life.ck patch with _40h_serial.mxb? 
> wondering if it's a communication problem between max and chuck?

mang... I had my hesitation being on xp when I bought the monome. :(
...don't regret it tho ;)

I'm off now, but maybe I can try 40h_life.ck later tonight, at the 
latest on sunday.

tehn wrote:
> have you tried running the 40h_life.ck patch with _40h_serial.mxb? 
> wondering if it's a communication problem between max and chuck?

I haven't noticed any problems using 40h_life.ck or follow with 
_40h_serial.mxb


many thanx for all help

> mang... I had my hesitation being on xp when I bought the monome. :(
> ...don't regret it tho ;)

actually don't worry, everything works fine on xp.

it's just more complicated to support two different setups. ;)

thanks for the ChucK solution.. happily triggering clips in Ableton 
Live.. great for when you don't need the complexity of mapd!

filarion wrote:
> thanks for the ChucK solution.. happily triggering clips in Ableton 
> Live.. great for when you don't need the complexity of mapd!

Glad people like it, and glad it could help. Have recived many mails and 
comments about it.

there is a person on this forum who speak french
because tech english is too hard for me
thank

tehn wrote:
> have you tried running the 40h_life.ck patch with _40h_serial.mxb? 
> wondering if it's a communication problem between max and chuck?

I can't add _40h_life.ck...

[_40h_life.ck]:line(2): ugen's of type 'DAC' have no input - cannot => 
from another ugen...

...is the message I get when I click Add Shred.

follow40h.ck works fine though.

> [_40h_life.ck]:line(2): ugen's of type 'DAC' have no input - cannot => 
> from another ugen...
> 
> ...is the message I get when I click Add Shred.

what os and miniaudicle version are you using?

tehn wrote:
> what os and miniaudicle version are you using?

XP SP2 and 0.1.3.6c

the above guest was me.

dogblessyou wrote:
> I don't get the lights to work. Otherwise it works fine, like 
> lio_beta.pat also does.

I just noticed that the midi feedback to control the lights work for 
some functions, like generic sliders, pan, track activator... but not 
solo, arm session rec... and clip launch as reported before... the midi 
out indicator remains dark, so it seems like Live doesn't send any 
feedback for those functions... maybe it would help to update Live? 
...got 5.0.2 running I think.

jah wrote:

> A max/msp-related question: what is the difference between
>.pat and 
> .mxb?

.mxb is a binary file, this means that the patch itself is saved in a 
binary format, like most save-patches in other programs (including 
Reaktor).  I *belive* .pat is a text-based file, where the patcher is 
saved in terms of a textfile showing what objects are used, how they are 
interconnected, and others.  if you view a .pat in textmode, you can 
actually modify the patcher in text-mode, although its pretty rough, its 
not exactly turning max/msp into a text-based programming language or 
anything!

i tend to just use .pat files.

kid-sputnik wrote:
> .mxb is a binary file, this means that the patch itself is saved in a 
> binary format, like most save-patches in other programs (including 
> Reaktor).  I *belive* .pat is a text-based file, where the patcher is 
> saved in terms of a textfile showing what objects are used, how they are 
> interconnected, and others.  if you view a .pat in textmode, you can 
> actually modify the patcher in text-mode, although its pretty rough, its 
> not exactly turning max/msp into a text-based programming language or 
> anything!
> 
> i tend to just use .pat files.

I see. This was not clear in the Max/MSP documentation. I guess this 
could make the binary files smaller. Thank you very much for your 
explanation!

hey--- i started a wiki entry for this project.

http://wiki.monome.org/view/AppChuckMonoableme

if anyone has a minute to share their setup steps and tack it on (and os 
x and xp version separately) that'd be rad. even the fastest sloppiest 
post is appreciated, i'll reformat if needed.

cheers!

tehn wrote:
> hey--- i started a wiki entry for this project.
> 
> http://wiki.monome.org/view/AppChuckMonoableme
> 
> if anyone has a minute to share their setup steps and tack it on (and os 
> x and xp version separately) that'd be rad. even the fastest sloppiest 
> post is appreciated, i'll reformat if needed.
> 
> cheers!

I'd be really interested to hear if anyone managed to get this to work 
on XP... and how.

> I'd be really interested to hear if anyone managed to get this to work 
> on XP... and how.


I've try everything and still i can't use monoableme.ck and lio_beta in 
xp. It sends signals to ableton but don't receive and light doesn't 
show:(

hhat wrote:
> 
>> I'd be really interested to hear if anyone managed to get this to work 
>> on XP... and how.
> 
> 
> I've try everything and still i can't use monoableme.ck and lio_beta in 
> xp. It sends signals to ableton but don't receive and light doesn't 
> show:(

Have you turned on midi-out in preferences in Live?
It's explained in http://youtube.com/watch?v=RIQeM6pOmXU , somewhat 
anyway.

For monoableme to work under OSX I need two midi-ports, possibly you 
need the same in XP.
Also on midi-out, in ableton, you need to activate all three buttons 
clip,sync,remote.

I'm working from memory here so it can be somewhat wrong. But it's 
explained in the video and in the top of the monoableme code.

Hi ahlstrominfo,

Great piece of code, actually your contributions (video, code and posts) 
made me decide to go for it, and get a monome.It sits right in front of 
me (arrived today), and it is happily running for hours now...

Your chuck code helps me to integrate with ableton live, and I must say, 
runs smooth.

My Mac OS X settup has a lot of virtual MIDI stuff going (and sometimes 
not), so the MIDI config (using 'chuck --probe') is different over time.

I modified your code so it helps me re-running it without checking the 
probe over and over again.

Here it is, it center around the MIDI opening sequence:

MidiOut mout;
MidiIn midin;

for(0 => int i; true ; i++){
  if (!midin.open(i)) me.exit();
  if (midin.name() == "Intern in") break;
}

for(0 => int i; true ; i++){
  if (!mout.open(i)) me.exit();
  if (mout.name() == "Intern out") break;
}


It assumes that you renamed the 'IAC Driver' to 'Intern', and that you 
named the two ports 'in' and 'out'.

I hope that the also brilliant mapd tool will, in a future version, be 
able to function as serialio (why not?) so that mapd and chuck can run 
together.

Cheers and keep up the good work.

JJupiter

dogblessyou wrote:
> tehn wrote:
>> serialio and _40h_serial.mxb are interchangeable.
> 
> Aha, I run ChucK AND max/msp :)
> 
> I don't get the lights to work. Otherwise it works fine, like 
> lio_beta.pat also does. Can anyone spot the error in the attached pic?

ok, loooking at the pic, why is there a cmd.exe open? it's like you're 
running two instances of chuck. command-line chuck, and then also 
miniaudicle??

i got 40h_life.ck to work on xp no problem.

from clean boot:

1. open max, _40h_serial.mxb
2. open miniaudicle, _40h_life.ck, start virtual machine, add shred

done. works great.

ok, i'm off to test this ableton ish now, still downloading the demo.

ok, the ableton download is taking forever.

i modified the monoableme.ck code a little bit for xp users.

it auto-searches and selects the first midi-yoke ports. that's why it's 
not working at the moment.

however, upon looking at the code, isn't this pretty much just a 40h osc 
to midi converter?

yo, we already made this patch in max/msp. get in the base package, and 
run _40h_midi.mxb --- it's super graphical, has preset saving, and midi 
port selection, etc. it should serve your bi-directional midi needs. 
you'll still need midi yoke in xp. in os x you can use the IAC system or 
(much easier) the to/from max/msp ports.

there is a picture of the patch here, along with the file:
http://wiki.monome.org/view/AppMaxMspBasePatches

go get it! remember to run serialio or _40h_serial.mxb at the same time.

tehn wrote:

> however, upon looking at the code, isn't this pretty much just a 40h osc 
> to midi converter?

That is absolutely right. I'm not at all that graphical like Max/MSP is. 
And also ChucK is free :D

ok, i just tested ableton with the 40h_midi.mxb file, and it works 
really well. tested with ableton 6.

on xp it requires midi-yoke.

i'll put together a tutorial and post it up.

tehn wrote:
> ok, loooking at the pic, why is there a cmd.exe open? it's like you're 
> running two instances of chuck. command-line chuck, and then also 
> miniaudicle??

I only used cmd to check the midi yoke ports, didn't know how to do this 
in miniaudicle.

>ok, i just tested ableton with the 40h_midi.mxb file, and it >works 
>really well. tested with ableton 6.

I also did some testing today. Checking the midi messages with 
midi-ox... Seems my version of ableton isn't sending any note on/off to 
the midi out port when launching clips, only sync. But some functions 
like mute and others works like a charm.

Downloaded ableton 6 demo and the LEDs work with clips. :)
But somehow it doesn't send feedback for mute anymore. :S ...but that's 
not as big of a deal.

Thanks for the help.

i still dosent get it to work as you show on the instruction film.
it dosent slices it. I haven´t used the monome so i might sell it.
I get the monome  to talk with ableton and i can assign buttons but not 
more then that. and other scripts you have, the just don´t work.
I use live 6.05 on intel mac.....


ayhan

Ayhan, well you need multiple clips of the same sample to do what he's 
doing in that vid. Read the tutorial that ejectorset put up for us. 
It'll explain it very throughly.

I tried both, the chuck approach (monogrid) and simply _40_midi.mxb to 
let the monome talk to ableton live 6. i totally liked the idea of using 
several clips with follow actions.

there are just two things i came across:

1. when using _40_midi.mxb while having clips joining each other thru 
follow actions, there are always two leds on the monome lid up. also, if 
i do some fast and wild tapping on the pads, they start hanging here and 
there

2. using the monogrid appraoch, i have another problem: i cannot combine 
my monome with other midi gear then. whenever i touch for example a midi 
slider i assigned to a fader in live, the shred gets kicked out of mini 
audicle's VM

somebody else encountered these things?

best,
christophe

I wish I could remember exactaly what caused it. . . but I had a similar 
problem when trying to sync Ableton to a hardware sequencer. (problem 
#2)  I don't remember if I took care of the problem in the preferences 
MIDI/Sync section of Live or just by not sending out MIDI Note data from 
the sequencer.  I think it was a fix in Live. But I think the problem 
was the note dat coming from the sequencer.  So. . . .

Is the other piece of gear sending MIDI CC data for the fader movement 
or something else (like MIDI note info)?

I currentlly am using a Behringer BCF2000 along with my Monome (using 
chuck or actually Miniaudicle).  I haven't had any problems. (well the 
order you start things seems important but that's not a problem just a 
minor issue)  When I'm home tonight I'll check what settings I have in 
Live.

Have you tried the latest version of MonoGrid, think I've fixed the 
problem with that one, download over at: 
http://forum.monome.org/topic/786#5049

Read more about it at the top of that thread.

So I've updated the code so that it works with lates ableton 6.0.7 and 
it's way of handling the clip-off midi-notes.

If you still get the problems with leds and/or sliders not working 
please tell me exactly how you setup your system and how you do to not 
make it work. Since I can't seem to reproduce the error with the either 
the Edirol PCR-M1 or the UC-33.

Now I will get some sleep again.

Since I haven't got any version for the previous ones this one is called 
2007-06-21 :D

thank you, mr. ahlstrominfo :-)

i used an "old" version of MonoGrid, going to try the new one when I'm 
at home tonight. I'll let you know if and how it works.

Even more updated:

now i'm sort of confused. i thought the update relevant for me was 
"MonoGrid_2_beta.ck". is it possible that i'm missing a very basic point 
here? :-)

for example not understanding the exact difference between MonoAbleMe 
and MonoGrid?

know what? going to simply check out both of em. it's amazing how 
inspiring the monome and especially your approach of combining it with 
Live actually is. i started thinking about Live and my personal liveset 
in a completely different way, longing for new things in Live i couldn't 
even think of a month ago, hehe

that's great. the downside is that i absolutely want to incorporate some 
of these new ideas for a set i'm going to play this saturday. these sets 
are always the most fun: trying new things, fucking up situations, 
solving them ... means consuming less alcohol, though.

yeah I'm not sure which is the most recent either.

I'm still using the original monogrid.ck

There is three different version:

MonoAbleMe which is the first is only 64 different notes.

MonoGrid is 8x7 notes on 8 separate notes.

MonoGrid2 is 8 different grids that can be used for different stuff, you 
modify it by altering the chuck-code.

What I did now is that I updated the original MonoAbleMe-code so that it 
works with the latest version of Live.

thanks for clearing this up! everything works fine for me now. no 
conflicts with other controllers anymore. going to check out the 
customization capabilities of MonoGrid2 now :-)

damn, this is so great. no chance for sleep tonight!

Then my work here is done... atleast for today :D

Hmmmz apologies, but I think I'm gonna have more work for you.  I've 
tried all the 3 patches you have, only MonoAbleMe works perfectly, 
Monogrid dies everytime I hit stop in Live or when I send external midi 
controller msg (UC33), and MonoGrid Part II does nothing, it doesn't 
even light up or send any message to Live.  Am I doing something wrong 
here, I'm using Monome Serial (OSC mode, edited to /box), Chuck/Mini 
Aud, Live 6.05.  I should be doing something right since MonoAbleMe 
works fine...  Help this ignorant fool!

M

Ok stupid me, sorted it out and it works great!

i just finished my kit, and am trying to connect to ableton live 6 with 
monogrid.ck    here's the issue: when i first opened my IAC driver setup 
there was a default port called Bus 1.  i added two ports, "in" and 
"out" like it showed here: 
http://wiki.monome.org/view/ChuckMonoablemeAndLive6SetupOsX  i ran all 
programs in order (with monomeserial prefix /box) and set my ableton 
live to track and remote enable the two ports i added.  for some reason, 
i could only get the midi signal to show in the already existing 'Bus 1' 
port - but as reported in the text of monogrid.ck, i got weird feedback 
loops.  i then tried to fix this problem by removing the port 'Bus 1', 
and nothing worked.  i tried to re-create 'Bus 1' in my IAC setup, and 
am nervous now that i removed the one port that showed any signs of 
working.

there is a picture attached that represents my current setup.  right now 
i'm going to restart my comp and test again.


onemannation: what was it exactly that you 'sorted out'?  maybe i am 
having the same issue.

to  rawray7.

I changed the prefix to /40h.  I use Mini-Audicle, Monogrid2, and Monome
Serial.  Try to change around the Monome serial selector to midi then
back to OSC, when I don't do that, it doesn't work.

Hope this helps.

First, you should download the latest MonoGrid over at 
http://ahlstrom.info/ChucK/

Second, make sure you have the latest version of chuck installed, 
1.2.0.8.

Third, you need to modify the chuck code, downloaded above, So that the 
midi ins and outs correspond to what you get when running "chuck 
--probe" in an terminal window.

By the way, I will update the code anyday now so that it looks for the 
in an out ports and set them by itself.

thanks - i've got things working now.  your method for doing 'mlr style' 
in Live is very original - i just wish it didn't take so much sample 
preparation time.

couple of things:

with the 7X8 grid system, is there any way to map one(or more) of those 
grids to mlr, and the others to live?  i was thinking that this would 
enable a couple of things: first, you could fake mlr into thinking you 
had a 8x16 (i.e. one grid would be first 8, the second 9-16).  also - 
you could have mlr as a track in live (using rewire) and still have your 
monome control live.

this is slightly off the topic of this thread, but had anyone 
successfully synced the tempo clock from live to the tempo control in 
mlr?  i've just got started with both msp and chuck in the last couple 
of weeks, so i'm not really sure how difficult that kind of thing is to 
code.

EDIT: okay, so i didn't realize how easy it was to sync the tempo clock. 
in mlr options just choose a source that you have set to 'sync' in live.

thanks for your help everyone.

Guys, I'm interested in what rawray7 describes too, using MonoGrid as a 
kind of master controller.  Having different "pages" for different apps, 
but all running in sync at the same time.  Especially mlr and live.
Anyone managed to implement anything like this yet?

I guess I'm jumping ahead of the game here, as my kit has only just been 
shipped!

:D

I just started working with the mlr-style live setup, and it's awesome. 
I don't see why you'd need mlr if you've got live and you've got this 
all working (with much respect to tehn for conceptualizing/coding mlr)

because Live doesn't beat slice on the fly.

I like mlr
i like its simplicity, but you can do awesome things with it. i use it a
lot
thanks tehn!

wow cool stuff. just out of curiosity does it only work with live 6 for 
some reason? i get the midi presses fine but for whatever reason my 
lights don't light up on press. I'm using the first example in the 
readme.

NEVER MIND

got it going.

tonedeft: true, but you still have to slice up your loops before you 
import them into mlr, right? I look at the slicing-in-live as just part 
of my loop prep. It probably takes about 30 seconds per loop. And then 
the advantages of Live over mlr:

proper midi syncing (mlr drifts)
variable-length sequences (ie 4 or 6 boxes rather than 8)
key-locked pitch shifting (mlr is often slightly out of tune for two 
loops from the same song)
More loops at once (56 8-box loops or 112 4-box loops as opposed to 4 
8-boxers)

Again - much love to tehn for creating mlr, but if you own Live and can 
get this setup going, it's much more powerful. Isn't this one of the big 
advantages of having an open system like this? You build something, and 
someone else takes the idea and improves it...

> Isn't this one of the big 
> advantages of having an open system like this? You build something, and 
> someone else takes the idea and improves it...

definately.   i prefer mlr, but for people who need more options 
(especially in the studio), ableton does make sense.

btw, the grid of 16 boxes in mlr lets you change how many steps the loop 
is sliced by (so you can use less than 8 slices, or up to 16 if you have 
2 units).

> You build something, and someone else takes the idea and improves it...

Thanks for the remark, but I don't know if I improved it very much.:)

Improvement will come once they release the ruby-live-api on the mac, 
then I hopefully can code something that will split the sample mlr-style 
without all the chopping and follow-actions.

has anyone gotten this to work with live 5? or is 6 the only way to go 
here? i got the lights to light up finally on the key presses using 
balron_40h , but not as a sequence rolls along. any ideas?

yeah i should have mentioned above i only have this going in a live 6 
demo… man i really cant afford live yet either.

it works in osx 10.4.10 and Live 6.0.9

so i assume it ONLY works it works in osx 10.4.10 and Live 6.0.9?

ok after some extensive searching i figured out that you simply need an 
options.txt file (which you create) in the preferences folder.
/user/library/prefrences/abelton/5.xx/options.txt

i have attached the options text im using. everything work pretty well 
occasionally light turn off for no reason. but better than paying for 
live 6 just to use it with the 40h.

hmm the attach didnt work.

I'm a complete Terminal noob... but whenever I run the 'Chuck --probe" 
command, i get a "Command not found" message.


I'm running :
OS X 10.4.10
MiniAudicle 0.1.3.7c
Monogrid 2.1
Monoserial 0.13
Live 5 (with the 'Options.txt trick' to allow midifeedbacks, which works 
when using with 40h's base patch _40_midi.mxb)

why are you using terminal at all again? for me all i need is 
miniaudicle and the monogrid.ck file.

i never managed to make that command work, and according to this video 
http://youtube.com/watch?v=RIQeM6pOmXU , i have to if i want to use 
Monogrid.