A big issue: Solved!

Throughout the programming process we’ve only managed to actually trigger the loops that we have set up in Ableton Live a couple times from Maxmsp. We’ve almost always managed to midi map the loops but when we’ve banged it in Maxmsp, the loops haven’t triggered. This had made us sceptical about the reliability of the ‘ctlouts’ and midi communication between the 2 softwares, but this didn’t appear to be where the problem lied.

While fiddling around today with a number (integer) object in Maxmsp, we found that the number 64 triggers things, and then any number below that will trigger it off (63 – 0). We only want to trigger them, so a message with the number 64 in it has been added to every instance of code that is assigned to Ableton’s clip slots. This is yet another trial and error finding that has been central to this process, that we weren’t able to find on the cycling74 forums or from any other external help.