Help with M4L - color the pads on push 3 using coll

zzz900's icon

Hello, please help me with my patch :)

I can put custom colors on the push 3 pads, but after restarting live it doesn´t remember all the custom colors.

I am using coll with @embed 1 to store the custom colors and dump them upon loading.

Can´t figure it out why it won´t work.

Thanks for the help!

push pad colors5.amxd
amxd 30.50 KB

Source Audio's icon

coll is editable only in max, not in live.

means only when you load that device into max editor and save it,

it will remember the colors.

you need dict or pattr, something that can be stored within live set.

zzz900's icon

Thanks a lot! I´ve tried using pattr, but somehow it still doesn´t work correctly. Push pad colors aren´t remembered the way I leave it when I save the live set.

Also GUI is very sluggish when I send data into the table, when pattr is bound to it. Did I do something wrong with the pattr?

Thanks for the help!

Max Patch
Copy patch and select New From Clipboard in Max.

Source Audio's icon

try this:

I replaced all live gui objects which don't have to be automated.

Max Patch
Copy patch and select New From Clipboard in Max.

P.S:

I am not live user so can't test anything that has to do with push and the rest.

but that 128 color values should be remembered.

zzz900's icon

Thank you, I´ve learned a lot from your patch! I had to add a midiparse instead of the route 144 object, and replaced the few gui elements so I can use them on the push.

Tethered it works great, standalone as well. Remembers everything after a power cycle. Nice!

Max Patch
Copy patch and select New From Clipboard in Max.

Source Audio's icon

live passes note off as 128 nn nn - true note off with release velocity.

but 144 nn nn passes note on which you use to select notes.

no need to react to note on and off, or ?

zzz900's icon

If I connect the route 144 to outlet of midiin, all I get is a bang. But I need the note number.

Maybe I am missing something?


Source Audio's icon

no, you are right, route alone does bang.

midiin input is itered

one needs match 144 nn , then $2

zzz900's icon

Didn´t know match, good to learn about it!

Roman Thilenius's icon

your route bangs because midin transports the midi input still bytewise and not as "144 60 100".

the often underrated match fits perfectly for that task (and was once probably made first in line for midi streams), it should be the most elegant solution.