Updated MonoAbleMe so that it has diffrent "grids", or what you may call
them.

Press buttons on the last row and you get a diffrent midi-channel and
new buttons to assign.

If you press and hold a button on the last row and then press another
button this fires of another note. This can be nice to use on mlr-like
loops. I split loops on up to 16 buttons. Then I use the
press-and-hold-feature on the first of thoose buttons to stop the loop.

With this new MonoAbleMe you have 448 buttons and then 448 more buttons
when holding down one of the lower buttons.

Dammit I'm tired does this even make sense?

There seem to be some kind of out of bounds array problem but can't
figure out when it happens.

And som late night show off over at youtube:
http://www.youtube.com/watch?v=5IZXwSt7Njc

ahlstrominfo wrote:
> Updated MonoAbleMe so that it has diffrent "grids", or what you may call
> them.

Really cool ahlstrominfo! The idea of firing off secondary notes when 
holding the grid select buttons is *great*. Gonna try out the chuck code 
as soon as possible :)

looks great, cant wait to try it out tonight!!!!!

wow, spent hours with it last night. worked flawlessly. 8 pages worth of 
triggers, soooo good!

actually not flawlessly, there was one small situation i ran into with 
MonoAbleMe, that i forgot to mention to you before.

i use another controller for midi remote stuff in live. if i already 
have stuff mapped to it when i open a live set, or try to map to it, 
chuck kills the shred saying it was "out of bounds or something".

i would think that if you limit which midi channels your are monitoring 
in chuck it would get around it. then i could just be sure to use a 
different channel on my other controller, i think.

i know that live is going to send the remote info to everything setup as 
remote devices, hopefully it at least keeps the channel info straight.

using the base midi max/msp patch it works fine with both controllers 
and clips mapped on the 40h, then sliders and such mapped on the remote 
sl 0.

ejectorset wrote:
> i use another controller for midi remote stuff in live. if i already 
> have stuff mapped to it when i open a live set, or try to map to it, 
> chuck kills the shred saying it was "out of bounds or something".

Thanks for telling me this. I plugged in a midi-interface in the 
computer and the problem occured right away. So it fixed in this 
version.

Also I fixed a bug when using MonoGrid with Live 5.2.X. The app sends 
diffrent midi on sync.

Also I noticed that you need Options.txt for Ableton Live 5.2.X and 
lower to get this to work.

awesome!

Just wondering if anyone has managed to get the 40h working in a Live 
set already mapped to another controller.I would like to use the 40h 
alongside my two faderfoxes but any attempt to do so kills the monogrid 
shred with an "arrayoutofbounds" alert same as ejectorset below.Mattias 
says he has fixed this in the latest code but I am still unable to get 
it to work...thanks








ejectorset wrote:
> wow, spent hours with it last night. worked flawlessly. 8 pages worth of 
> triggers, soooo good!
> 
> actually not flawlessly, there was one small situation i ran into with 
> MonoAbleMe, that i forgot to mention to you before.
> 
> i use another controller for midi remote stuff in live. if i already 
> have stuff mapped to it when i open a live set, or try to map to it, 
> chuck kills the shred saying it was "out of bounds or something".
> 
> i would think that if you limit which midi channels your are monitoring 
> in chuck it would get around it. then i could just be sure to use a 
> different channel on my other controller, i think.
> 
> i know that live is going to send the remote info to everything setup as 
> remote devices, hopefully it at least keeps the channel info straight.
> 
> using the base midi max/msp patch it works fine with both controllers 
> and clips mapped on the 40h, then sliders and such mapped on the remote 
> sl 0.

Is it possible to have a release that has sliders on one of the grids? 
(say the last slot so there's 8 sliders)?

Joelb wrote:
> Is it possible to have a release that has sliders on one of the grids? 
> (say the last slot so there's 8 sliders)?

I agree... this would kick ass.  Or if you could have an X-Y sort of 
slider as well, like in the Mapd examples, for controlling FX.  I'm 
trying to learn how to code with ChucK, and if I could do it, I would. 
Hopefully eventually...

In regards to using other midi controllers - I have been doing that with 
Monogrid, no problem.  I'm not sure what I'm doing right (or wrong), but 
I just plugged in my midi keyboard (via USB) and it worked.  Knobs, 
sliders and all.

Joelb wrote:
> Is it possible to have a release that has sliders on one of the grids? 
> (say the last slot so there's 8 sliders)?

I've been thinking about this one and I cant decide how I want the 
sliders to work. If they should fade up or simply go straight to that 
position. Probably I would do it fading atleast for a short period.
And one more thing I'm thinking about is if the sliders should go all 
the way to value 127 or stop short at lets say 115 since you almost 
never turn up the volume straight to eleven(geekish reference, sorry 
:-).

ahlstrominfo wrote:
> I've been thinking about this one and I cant decide how I want the 
> sliders to work. If they should fade up or simply go straight to that 
> position. Probably I would do it fading atleast for a short period.
> And one more thing I'm thinking about is if the sliders should go all 
> the way to value 127 or stop short at lets say 115 since you almost 
> never turn up the volume straight to eleven(geekish reference, sorry 
> :-).

Maybe make 2 grids straight fade and another 2 slow fade. (if that makes 
sense or is even possible)
ie:

Grids
1 - triggers
2 - triggers
3 - triggers
4 - triggers
5 - fast fade (straight)
6 - fast fade (straight)
7 - slow fade
8 - slow fade

n.b. 127 is too loud! :P

> Maybe make 2 grids straight fade and another 2 slow fade. (if that makes 
> sense or is even possible)
> ie:
> 
> Grids
> 1 - triggers
> 2 - triggers
> 3 - triggers
> 4 - triggers
> 5 - fast fade (straight)
> 6 - fast fade (straight)
> 7 - slow fade
> 8 - slow fade
> 
> n.b. 127 is too loud! :P

I like this idea.  I was also thinking about how you would set up some 
sort an x-y thing to control fx, too.  I don't know if that would even 
work, since you essentially would have to control two knobs 
simultaneously...

And yes, all the way to 127 would be a bit excessive.

but since this is for interfacing with live and ableton will let you 
scale the values on their end, it might as well send 0-127

hi,

Wicked application! Actually I got it working perfectly with Ableton 
except for one thing: I cannot get the monome LEDs lighting. I think 
I've set it everything properly (IAC in/out ports and Ableton MIDI 
preferences) but monome refuses to light any LED, apart from the lower 
midi channel row. I'm using it with Live 5.0, should I try to upgrade to 
Live 6.0?

Thanks!

Inigo,
i believe from some of the other threads that live 5 needs the 
midifeedback turned on in options.txt

i think this page has the info on how to do it:
http://www.vjforums.com/showthread.php?t=12568

> Also I fixed a bug when using MonoGrid with Live 5.2.X. The app sends 
> diffrent midi on sync.
> 
> Also I noticed that you need Options.txt for Ableton Live 5.2.X and 
> lower to get this to work.

sorry for my post above, I didn't read this. In any case which 
Options.txt do you refer to?

Thnks.

> sorry for my post above, I didn't read this. In any case which 
> Options.txt do you refer to?
> 
> Thnks.

http://forum.monome.org/topic/613

leds are working for me in the last version of live 5.2, had to use the 
options.txt thing even though i read it should be on (im on PC, dont 
know about mac).

> 
> http://forum.monome.org/topic/613

Thanks. I realised you talk about this before, sorry. Anyway I tried 
that but leds refuse to light. I'm using Ableton 5.0.1 (I don't know if 
that trick is just for versions 5.2 onwards).

Thanks again

its supposed to be from 4.x onwards, i dont know if things changed 
though.  makw sure you have your MIDI out setup correctly.  if i make 
the same channel on midi yoke input and output midi i get a crazy 
feedback loop in my max patch, instead i use a differant midi yoke 
output port than for input, and set that up accordingly in my max patch, 
i think in ableton you set the out and in connections for "remote" on.

FYI:
i'm running 5.0.1 with the options.txt hack and the LEDs light.

kid-sputnik wrote:
> its supposed to be from 4.x onwards, i dont know if things changed 
> though.  makw sure you have your MIDI out setup correctly.  if i make 
> the same channel on midi yoke input and output midi i get a crazy 
> feedback loop in my max patch, instead i use a differant midi yoke 
> output port than for input, and set that up accordingly in my max patch, 
> i think in ableton you set the out and in connections for "remote" on.

> output port than for input, and set that up accordingly in my max patch, 
> i think in ableton you set the out and in connections for "remote" on.

Hi, I don't understand this, wich max patch are you talking about? 
Should I have the max OSC/midi patch running at the same time as well? 
At the moment I got the serialIO working together with 
miniAudicle/Monogrid.ck. Do I have to activate the OSC max patch too? 
Where can I check my MIDI out setup? Thanks.

Hi,

I've just followed every step in the tutorial, and also added the 
Options.txt file with the right -MIDINoteFeedback
command on it, but I cannot get the lights on the Monome working. What 
am I doing wrong?

I think Ableton 5.0.2 is sending back the data through another MIDI 
channel, but how can I check this? Is there any way I can check wichi 
MIDI channels are being used? And how can I change this to the right 
channels?

Thanks

try this free program to monitor midi messages in os x:

http://www.snoize.com/MIDIMonitor/

for the chuck/ableton patches to work, you have to set up IAC ports as 
described in the tutorial, then actiavte them in Live preferences...make 
sure they look like the screenshot in the tutorial.

it works GREAT for me, using two 40hs at once (assigning each their own 
prefix in the new serialio), each with their own banks of grids.

a fader bank would really be over the top!  i agree, 115 would be a 
great 'top volume', slow fade (otherwise why not use a mute button 
toggle)

cheers
dp

d-p wrote:
> try this free program to monitor midi messages in os x:
> 
> http://www.snoize.com/MIDIMonitor/
> 

hi, thanks for the tip. Well, I actually upgrade to Live 6.0.5 and the 
monome keeps refusing to light up. Aparently everything is set as said 
in the tutorials. Life 6 is sending midi data to the 'out' through the 
right channel. I paste you below the trace data from the MIDIMonitor:

---------
*** ZERO ***  From in  Note On  1  C-2  127
20:54:01.848  To out  Note On  1  C-2  126
*** ZERO ***  From in  Note Off  1  C-2  0
20:54:03.798  To out  Note On  1  C-2  127
20:54:07.804  To out  Note On  1  C-2  1
20:54:11.810  To out  Note On  1  C-2  1
------------

Here I'm hitting one of the monome pads and it sends de midi in to the 
Life 6, who receives it perfectly and triggers the clip. Life 6 is then 
sendinb back the midi out everytime the loop is played in a bar, so the 
midi data is actually being sent to the midi out through channel 1. I 
don't know what happens but this data doesn't light up the pad in the 
monome.

I'm using os X 10.3.9, so maybe the MonoGrid.ck doesn't work properly 
there. Any tip? Thanks alot everyone

d-p wrote:
> try this free program to monitor midi messages in os x:
> 
> http://www.snoize.com/MIDIMonitor/
> 

hi, thanks for the tip. Well, I actually upgrade to Live 6.0.5 and the 
monome keeps refusing to light up. Aparently everything is set as said 
in the tutorials. Life 6 is sending midi data to the 'out' through the 
right channel. I paste you below the trace data from the MIDIMonitor:

---------
*** ZERO ***  From in  Note On  1  C-2  127
20:54:01.848  To out  Note On  1  C-2  126
*** ZERO ***  From in  Note Off  1  C-2  0
20:54:03.798  To out  Note On  1  C-2  127
20:54:07.804  To out  Note On  1  C-2  1
20:54:11.810  To out  Note On  1  C-2  1
------------

Here I'm hitting one of the monome pads and it sends de midi in to the 
Life 6, who receives it perfectly and triggers the clip. Life 6 is then 
sendinb back the midi out everytime the loop is played in a bar, so the 
midi data is actually being sent to the midi out through channel 1. I 
don't know what happens but this data doesn't light up the pad in the 
monome.

I'm using os X 10.3.9, so maybe the MonoGrid.ck doesn't work properly 
there. Any tip? Thanks alot everyone

did you setup the IAC channels in audio midi setup?

for some reason i thought iac was new to tiger.

ejectorset wrote:
> did you setup the IAC channels in audio midi setup?
> 

yes I did exactly as depicted in the tutorial. I sincerely cannot 
understand why it isn't working, or maybe I'm missing something

Ahlstrom: I'm doing some 2-way interfacing with Live and hit a wall with 
just using the 40h_midi since I can't get visual feedback on things like 
toggles (arming tracks, overdub. etc.) I could do it in Mapd except that 
Mapd doesn't yet support incoming messages.

So my question: could you explain how I might build my own custom grids 
with Chuck? Would this be too complicated? Like you could perhaps 
explain the code for Presses versus Toggles. I'm going to jump into the 
Chuck documentation, but any help you could give would be most 
appreciated.

Thanks!

momo_the_monster wrote:
> Ahlstrom: I'm doing some 2-way interfacing with Live and hit a wall with 
> just using the 40h_midi since I can't get visual feedback on things like 
> toggles (arming tracks, overdub. etc.) I could do it in Mapd except that 
> Mapd doesn't yet support incoming messages.
> 

Hi. I also use (new)monoableme.ck with live written by Alstrom and i 
think is brilliant. I wonder if you could add toggles to receive visual 
feedback from rest functions in live it would be much, much helpful.
for example: buttons whose are not mapped in live/clips could work as a 
toggle and show which mapped button is on/off (effects, tracks etc.)
I would be gratefull if someone could help or add those changes to the 
code.

Best

I have found a workaround! Make a MIDI track with a bunch of Pitch 
Shifters in it, all set to shift by 0 (ie do nothing). Assign the Power 
Toggles on these to the buttons you want to show your current state. 
Also assign whatever you actually want to toggle (arming, OVR, etc). 
Since Power Toggles send MIDI and hold state, you'll now be able to see 
what you're doing! You can see a video and article that covers this at 
http://vjkungfu.tv/archive/av-sequencing-with-live-vdmx-monome/

Guest wrote:
> 
> Hi. I also use (new)monoableme.ck with live written by Alstrom and i 
> think is brilliant. I wonder if you could add toggles to receive visual 
> feedback from rest functions in live it would be much, much helpful.
> for example: buttons whose are not mapped in live/clips could work as a 
> toggle and show which mapped button is on/off (effects, tracks etc.)
> I would be gratefull if someone could help or add those changes to the 
> code.
> 
> Best

momo_the_monster wrote:
> I have found a workaround! Make a MIDI track with a bunch of Pitch 
> Shifters in it, all set to shift by 0 (ie do nothing). Assign the Power 
> Toggles on these to the buttons you want to show your current state. 
> Also assign whatever you actually want to toggle (arming, OVR, etc). 
> Since Power Toggles send MIDI and hold state, you'll now be able to see 
> what you're doing! You can see a video and article that covers this at 
> http://vjkungfu.tv/archive/av-sequencing-with-live-vdmx-monome/
> 

How do you assign it to 2 things at once?
I can't assign a single button to "pitch power button" and "track arm".
I viewed the video a few times and still couldn't figure it out.

Guest wrote:
> 
> How do you assign it to 2 things at once?
> I can't assign a single button to "pitch power button" and "track arm".
> I viewed the video a few times and still couldn't figure it out.

Hm - I just tried it again and had no problem on my end. Enter MIDI 
mapping mode and click on the 'power' button in the upper-left corner of 
the Pitch effect, then hit your note. Click on the arm button, and hit 
the note again.

I used this in conjunction with the 40h_midi patch, if that makes a 
difference.

Guest wrote:
> momo_the_monster wrote:
>> Ahlstrom: I'm doing some 2-way interfacing with Live and hit a wall with 
>> just using the 40h_midi since I can't get visual feedback on things like 
>> toggles (arming tracks, overdub. etc.) I could do it in Mapd except that 
>> Mapd doesn't yet support incoming messages.
>> 
> 
> Hi. I also use (new)monoableme.ck with live written by Alstrom and i 
> think is brilliant. I wonder if you could add toggles to receive visual 
> feedback from rest functions in live it would be much, much helpful.
> for example: buttons whose are not mapped in live/clips could work as a 
> toggle and show which mapped button is on/off (effects, tracks etc.)
> I would be gratefull if someone could help or add those changes to the 
> code.
> 
> Best

I've forgotten to log-on..


> momo_the_monster wrote:
>I have found a workaround! Make a MIDI track with a bunch of Pitch 
>Shifters in it, all set to shift by 0 (ie do nothing). >Assign the Power 
>Toggles on these to the buttons you want to show your current state. 
>Also assign whatever you actually want to toggle (arming, OVR, etc). 
>Since Power Toggles send MIDI and hold state, you'll now be >able to see 
>what you're doing! You can see a video and article that >covers this at 
>http://vjkungfu.tv/archive/av-sequencing-with-live-vdmx-monome/


It's very nice video but i wonder if is possible to add toggle to 
monoGrind.ck code?? then you could have permanent control in live 
(clips, buttons, arming, etc.)
cheers

hhat wrote:
> It's very nice video but i wonder if is possible to add toggle to 
> monoGrind.ck code?? then you could have permanent control in live 
> (clips, buttons, arming, etc.)
> cheers

Probably - I've written some code in ChucK to do just this - check it 
out at http://forum.monome.org/topic/699#4326

momo_the_monster wrote:
> hhat wrote:
>> It's very nice video but i wonder if is possible to add toggle to 
>> monoGrind.ck code?? then you could have permanent control in live 
>> (clips, buttons, arming, etc.)
>> cheers
> 
> Probably - I've written some code in ChucK to do just this - check it 
> out at http://forum.monome.org/topic/699#4326

thankyou, i saw this code but i don't know how to programing in chuck 
and i couldn't do it myself:(

hhat wrote:
> momo_the_monster wrote:
>> hhat wrote:
>>> It's very nice video but i wonder if is possible to add toggle to 
>>> monoGrind.ck code?? then you could have permanent control in live 
>>> (clips, buttons, arming, etc.)
>>> cheers
>> 
>> Probably - I've written some code in ChucK to do just this - check it 
>> out at http://forum.monome.org/topic/699#4326
> 
> thankyou, i saw this code but i don't know how to programing in chuck 
> and i couldn't do it myself:(

No time like the present to learn, right? I finished that piece of code 
within a day of downloading the ChucK manual.

momo_the_monster wrote:
> hhat wrote:
>> momo_the_monster wrote:
>>> hhat wrote:
>>>> It's very nice video but i wonder if is possible to add toggle to 
>>>> monoGrind.ck code?? then you could have permanent control in live 
>>>> (clips, buttons, arming, etc.)
>>>> cheers
>>> 
>>> Probably - I've written some code in ChucK to do just this - check it 
>>> out at http://forum.monome.org/topic/699#4326
>> 
>> thankyou, i saw this code but i don't know how to programing in chuck 
>> and i couldn't do it myself:(
> 
> No time like the present to learn, right? I finished that piece of code 
> within a day of downloading the ChucK manual.

you have right, there is plenty of information in internet how to learn 
it. I've already done some my patches with simple oscillators sounds in 
chuck but there is still a lot of thinks witch i can't figured out

Hi guys -

I'm having an issue with MonoGrid where lights that should be on 
(according to ableton 6.0.7's clip status) suddenly turn off, only to 
come back on a few seconds later if ever.  Then also, sometimes when I 
switch 'pages' (via the bottom row of buttons) and come back to the 
original page, there will be a bunch of lights on that shouldn't be. 
Hitting Ctrl-M (midi assign mode in Ableton) and then exiting makes 
everything right, but obviously that's not kosher during a live set.

I have tried both serialXP and the new MonomeSerial for XP, with the 
same behavior for both.  I use Midi Yoke 1 for my midiout and Midi Yoke 
2 for my midiin in monogrid.ck.

Any suggestions?

thanks,

- Mark

Are you using the monome with a Live set with functions already mapped
to another controller?

I get the same problem.

I noticed it more before I assigned most of the buttons on the monome. 
is still occurs occasionally but it used to be if I had a "grid set up 
and only had a few button assigned to do anything in Live that problem 
would pop up.  Now that I have almost all the buttons assigned I only 
occasionally get get that.  I'm starting another set from scratch we'll 
see if the frequency of occurance increases.

I think it happens more often when I trigger the stop and switch grids 
before the clip actually stops.

oh yeah and zeropoint the answer for my setup is no.

could somebody post up a complete description of how midi works in the 
newest ableton?

i'd like to put together something that works for everyone, and i'll 
probably do it in max/msp so that midi port selection isn't such a drag.

zeropoint -

yes, I also have a uc-33 midi-mapped to a few parameters like faders and 
eq.

tehn -

not sure if this will tell you everything you need, but here is Robert 
Henke's post about the change made in Live 6.0.6

"Dear Users,
in the new beta version ( Live 606b1 ) we changed the behaviour of the 
MIDI feedback for clips lauched in session view. Let me first explain 
the problem and later tell you how you can solve it in this beta.

The Problem:
When a clip is launched via MIDI it sends back messages that can be used 
e.g. for to drive a status LED on a hardware controler. A note with 
velocity of 126 indicates that a clip is launched, a note with velocity 
127 indicates it starts playing and veloctiy 0 means it stopped. So far 
so cool. But unfortunately if you launch a second clip in the same track 
while the first one is playing the order of execusion in Live leads to a 
very confusing output: first the new clip is launched, and afterwards 
the old clip is stopped, means the last MIDI info you get is the Note 
Off from the old clip. This behaviour makes it very hard to derive 
usefull information for display purposes.

One workaround (which I used for the MonodeckII control) is to delay all 
Note On messages a bit so they certainly will arrive after the Note Off. 
This is relatively easy to do in MAX but tricky elsewise.

The Solution
We decided to change this behaviour for the current beta. We now send 
the Note Off first and then the other feedback data. But this change is 
very tricky, it might break things on places which we do not expect. 
Therefore we decided to make it optional for this beta. You need to turn 
it on explicitely if you want it.

You need to create a textfile called Options.txt and place it in the 
.../Preferences/Ableton/Live606b1 folder. This file needs to contain 
this line of text:

-_SwitchOrderOfSuccessiveClipStartStop

If there is allready an Options.txt file simply add this line.

As we said before, we are not 100% sure if this is working under all 
circumstances correctly. This mean we would appriciate if a lot of you 
try it out. Even if you are not using the feedback yourself. It should 
in no case cause other oddities, like changing how follow actions work 
or looping. If you experience problems try removing the options entry to 
figure out if this is the cause.

Thanx for the support.

Robert Henke
Ableton"

I've updated MonoAbleMe for the latest versions of Live. I haven't 
updated MonoGrid and MonoGrid2 yet.

Should probably have time to do it this comming week, until then I think 
you can use the options.txt setting to fix it.

ahlstrom -

do you think that is what's causing our issue?  if so, what is needed to 
fix it?

I know it is :). I noticed the same problem with MonoAbleMe and fixed 
it, didn't think about fixing it in the other scripts.

I can't think of any other thing that would give the same problems.

mattias -

any word on a fix yet?  :D

I can't figure out how to disable the new clip status behavior.

I've been trying to replicate the problem with my MonoGrid 2 code but I 
can't seem to do it.
So please try the latest version of that.
It can be download over at: http://ahlstrom.info/ChucK/

Hi Mattias

I cannot get this file to run.....either from the terminal command line 
or in miniaudicle. Anyone else got this working?

Thanks

>I cannot get this file to run.....either from the terminal command line 
or in miniaudicle.

What does this mean? What happens? Nothing? What have you tried so far? 
More info please. OSX or Windows?

Ok sorry. I'm on a macbook pro running OSX 10.4.9 and Live 6.07. When I 
try to run the file nothing happens....i.e there is no response 
whatsoever from the monome...I tried with the Monogrid 2 beta as well 
and I get the same result....it just stays locked in it's start up 
state. This happens whether I attempt to launch it from the terminal 
command line or miniaudicle. I pasted your Ahlstrom Rules....text into 
the Monogrid 2 file just to see if the file was opening at all and that 
text now comes up in the command line but the monome stays locked with 
no response at all.

I can run the original Monogrid file fine except that I am still having 
problems running my faderfoxes at the same time...buttons lighting up 
and going off that shouldn't and array out of bounds messages whenever I 
come out of midi map mode in Live.

Faderfoxes are on channels are on channels 1,13.14 and 15. I don't use 
the first grid in the monome as a result but I was hoping the other 
grids would not be affected by controls mapped to the same notes on 
channels outside the Monogrid channel range...

If you need any more info let me know

thanks

Do you use serialIO or MonomeSerial?

If you use the first you probably need to modify this row:

"40h" => string boxname;

to:

"box" => string boxname;

Also you need to make sure you use ChucK version 1.2.0.8 (dracula). This 
you can do by writing:

chuck --version

in a terminal window and press enter.

Thank you and thank you again......after months of trying to get my rig 
properly working together, that has finally sorted it. Nice one 
Mattias........

My lights dont work with Live and Monogrid..(exept on the last row)
so...
Where do I do this?:
------------------------------
If you use the first you probably need to modify this row:

"40h" => string boxname;

to:

"box" => string boxname;
-------------------------------
thank you
arne

> Where do I do this?:

First, make sure you've downloaded the latest version of ChucK.
Second, make sure you've downloaded the latest version of monogrid at h
http://ahlstrom.info/ChucK/
Third, open the downloaded file in a texteditor and search and replace. 
It is near the top.

Hi
I am afraid this is not working either..
I am using Osx 10.3.9 with SerialIO and Ableton Live 6.0.5.by the way.

arne

By the way. What do you mean that they don't work?
Have you've setup the midi ports and changed the midichannels in the 
chuck-code?

PC user here, I get an LED along the bottom row of the monome to light 
up and the rest play my OS's piano sound, is this all setup to work in 
Mac only?

btw there's no need to do a text replacement in the chuck patch, just 
change the prefix to 40h in monome serial as it is in the code.

how do I change the port this thing squirts out of?  thanks for any tips 
because that'll be a good chuck thing to know in general.

I'm not seeing how to run the command Chuck --probe in miniAudicle, if I 
make a short program (file-new) I get an error.

If the rest play the pianosound the setup is correct. To have a clip 
turned on the midi message to be sent from 40h have to be a note.
Probably you need to turn of some of the track,remote,sync stuff in the 
setup of Ableton Live.

The chuck program send out of every port. The first grid from port 1 
when selected and port 9 when holding down the button. The second from 
port 2 when selected and port 10 when holding down. And so on.

I think you can only run "chuck --probe" in command, cmd.exe. But then 
you need to install ChucK on the computer. I've only used miniAudicle 
once, so I really don't know how to make it work in it.

"By the way. What do you mean that they don't work?
Have you've setup the midi ports and changed the midichannels in the
chuck-code?"

Hi
I mean that only the lights on the bottom row is working. I have 
followed youre instructions on the midiports and made the Ableton setup 
like like you have described it. It is playing but there is no light in 
reponse to the file playing.
What do you mean by "changing the midichannels in the chuck code"?
thank you
arne

Hey Tonedeft some questions:

do you have MIDIyoke installed?
are you using MIDI or OSC in monome serial or serialXP or what ever 
program you are using to talk to the monome?

monomeserial in OSC mode, been using midi yoke for years, no problems. 
I'll try it again tonight.

"Have you've setup the midi ports and changed the midichannels in the
chuck-code?"

Yes I am using the IAC midichannels. Do I have to change something in
the Chuck code?
a

...that was me by the way.
Arne

...so I bought the OSX update from 10.3.9 to 10.4.10 and now it works.
At it is great! Thank you!!

Okay, I'm having the same problem as previously mentioned when using 
monogrid with any faderfox live set. Works great on any other set, but 
launching any faderfox set kills the shred and gives me 
"ArrayOutofBounds: in shred[id=1:MonoGrid 2.1.ck], PC=[2],index=[66]" If 
I launch monogrid after starting live, I can assign buttons to clips, 
but it kills the shred when I exit out of midi assign mode.

I've tried all the fixes listed here and on some other forums, with no 
luck. Here's what I'm running:

OSX 10.4.10

IAC ports
  in (Connectors for in: Midi in - 1, Midi Out - 1)
  out
  device is online checked

MonomeSerial 0.17
  I/O:  OSC
  Host Address:  127.0.0.1
  Host Port:  8000
  Listen Port:  8080
  Device: m40h0127
  Cable: Top
  Address Prefix: /40h

miniAudicle 0.1.3.7c (ChucK 1.2.0.8)

Live 6.0.9
  Input: IAC Driver (in) - track: on - sync: off - remote: on
  Input: IAC Driver (out) - track: off - sync: off - remote: off
  Output: IAC Driver (in) - track: off - sync: off - remote: off
  Output: IAC Driver (out) - track: on - sync: off - remote: on
  Input: from MonomeSerial 1 - track: on - sync: off - remote: on
  Output: to MonomeSerial 1 - track: on - sync: on - remote: on

Live set in question is attached. Any ideas? I've been troubleshooting 
for many hours on this one...

Have you tried the latest version of MonoGrid?

http://ahlstrom.info/ChucK/

Yeah, MonoGrid 2.1.ck is what I've got. I downloaded again to try but no 
luck.

I know the faderfox live sets use extensive midi mapping on channels 13, 
14, and 15, so maybe there's something about the sets themselves and not 
any of my other settings that keep killing the shred.

Any other ideas? Thanks in advance!

Okay, so I made some progress. I can get it to work like this:

1. Launch MonomeSerial
2. Launch Live and open faderfox set
3. Launch miniAudicle and open Monogrid 2.1
4. Start virtual machine and make new shred
5. Go back into Live and assign buttons in midi map mode
6. Exit midi map mode, thus killing the shred
7. Stop virtual machine, restart virtual machine, run a new shred
8. Go back into Live, where everything works. If I go into midi map mode 
again, the shred is killed upon exit.

I guess as long as I restart virtual machine and make a new shred each 
time I change midi mapping, I'll be okay :D

Work arounds just make me nervous...

Thanks!

I still can't get off the ground with this app

Live sees midi input, so serial i/o is OK and the app is running, 
max/msp is shut down, just Live and midiAudicle.

"chuck --probe" - chuck isn't recognised as a command even when I run it 
in the chuck directory.

what to assign to midi isn't all that clear, I think once I clear up the 
"chuck --probe" problem I can play with it and learn, but any tips?


using mlr has opened my ears as to how my loops can be mangled but it's 
still a bit touchy and tehn is quite busy.  with the options available 
in the chuck code tweaks this app could be cool, I just don't totally 
get it.

Hey Toney,
What are you trying to do here.
Are you able to assign any buttons to anything in Live?
If so, thats it.
Now just assign any page/button you want to anything in live.

If you want to mlr-ise it, just use clip follow actions (in Live.)

Chuck--probe doesnt appear to work in miniaudicle.  Its useful for 
seeing what ports your internal midibus is using for in/out.  For macs, 
they can be seen from the IAC driver page.

K.

Hey Tone - Let's try to work out your issues.  First thing I would do is 
uninstall miniaudicle and download Chuck.  I had problems with 
miniAudicle when I first started trying this thing out.

Per the chuck install readme, after you have unzipped .zip file, "On 
win32: put bin\chuck.exe in c:\windows\system32\".  You could either do 
that or put it somewhere else (i.e. C:\Chuck\chuck.exe) and edit your 
PATH variable by right-clicking My Computer, going to the advanced tab, 
then clicking the Environment Variables button at the bottom.  Then add 
";C:\Chuck\" to the end of the string labled PATH.

If you still can't run chuck --probe after that let me know.

Thanks for this. The Block Rockin' Beats video was what finally made me 
get the 40h.

What I'd love to be able to do is have the grid select buttons also 
switch to a new bank of assignments on another control. For example, if 
I set the control knob on my Audio Kontrol 1 to send MIDI, then it'd 
change the level for track one when grid one was selected for the 40h, 
for track two when grid two was selected, for track three when...

Would it be possible to feed MIDI from other controllers through 
MonoGrid to get such an effect?

Right, first off, big thankyous to ahlstrominfo for monogrid. jamming 
with the monome + AL through monogrid is too much fun, not to mention 
inspiring, and to be honest has me looking at AL in a fresh way.
What I was wondering was what I would have to add to the monogrid Chuck 
code to enable the adc ports for use. I am not by any means an expert 
programmer, but could probably find my way if someone pointed me in the 
right direction...? Alternatively would there be a way of using monogrid 
in chuck + _40h_midi in MaxMSP for the adc channels? I've tried various 
things but have yet to find a solution. Any ideas much appreciated...

mipmip

Hello everyone. I've been so damn busy last few week an has not been 
able to answer anything about the MonoGrid code.
I've been thinking about a new version of MonoGrid but it's an hell-ish 
code to work with. For every version so far I've re-written most of the 
codes, cause I can't remember why I built it that way.

Anyway, the limitations of chuck is very evident and I thinking of going 
to java or some other fine language. Atleast for the MonoGrid thingi.

However ChucK is brilliant for smaller funner apps such as those 
tenori-on is showing, with built-in sounds. So I'll probably release 
some of that code in the next weeks or so.

i agree, about chuck.

i've been seriously considering python-- the serial-pyio is coming along 
very well and it seems like an elegant environment to work in.

Sorry if this has been covered elsewhere, but do you have any particular 
recommendations for a starting point for non-programmers who want to 
start exploring? I'd been thinking about Chuck, but now I'm wondering if 
it wouldn't be something of a dead end.

keep up the good work ahlstrominfo i can only say how much i have 
enjoyed monogrid and i cant imagine the good things you're capable of. 
thanks!

Any way to adapt the AblemonoMe chuck script or use chuck at all, to 
generate MIDI information from a generic OSC signal? Maybe I'm not clear 
but I'd like to use it for this project:

http://forum.monome.org/topic/1203#new

Basically what I'm trying to do is use the iPod touch to activate a 
webscript on my local network that generates OSC information.  I'm not 
very familiar with OSC and am trying to translate the OSC information to 
basic MIDI terms that I could use to map to Ableton.  In the end I'd 
like to be able to use the iPod touch to trigger clips from Ableton. 
Any help would be much appreciated.

Cheers,
Andrew