SonOfAGlitch

I'm having a problem with the Max4Live version of a patch made in Max/Msp. As a matter of fact, the two patches behave differently when opened in Max or in M4L.

In particular, some steps of the sequencer that I programmed turn on automatically whenever I open the device in Ableton - it doesn't do it in the Max/Msp patch. Each step is a toggle (0 = off; non zero = on)

My initial solution was to "loadbang / loadmess bang" a 0 in a message box to each step of the sequence, but the device doesn't seem to respond how it should. Despite the loadbang produces the bang, the steps don't turn off.

Since the patch is too big, it would be counter productive to post it here; let me know if there is some other way to share the info that you need.

Hey all,
I'm having a problem with the Max4Live version of a patch made in Max/Msp. As a matter of fact, the two patches behave differently when opened in Max or in M4L.
In particular, some steps of the sequencer that I programmed turn on automatically whenever I open the device in Ableton - it doesn't do it in the Max/Msp patch. Each step is a toggle (0 = off; non zero = on)
My initial solution was to "loadbang / loadmess bang" a 0 in a message box to each step of the sequence, but the device doesn't seem to respond how it should. Despite the loadbang produces the bang, the steps don't turn off.

Since the patch is too big, it would be counter productive to post it here; let me know if there is some other way to share the info that you need.
Thanks :)


Hey all,
I'm having a problem with the Max4Live version of a patch made in Max/Msp. As a matter of fact, the two patches behave differently 

Problems with loadbang - the patch behaves differently in Max/Msp and M4L