Jesse Meijer

I'm trying to figure out how to save my last physically touched MIDI values from a MIDI controller and be able to bang it whenever I need it (value/adress/channel). I need this so that for instance i can press record on a DAW and directly overwrite the underlying automation already recorded instead of it not changing until I touch a control and so having to touch every fader, button or knob.

I've managed to get it working, but isn't this a sloppy system?

button

loadbang

unpack

pack

coll

message

route

counter

gate

swap

ctlout

ctlin

Hey guys,
I'm trying to figure out how to save my last physically touched MIDI values from a MIDI controller and be able to bang it whenever

save-all-last-midi-controller-settings-and-bang-values-when-needed

You might want to have a look at the [mtr] object, its touch message, and this video+patch: https://cycling74.com/feature/mtr

wow tnx, this is really nice for other stuff I'm doing. But for this specific question is more that I just need a picture and not so much a sequence.

not even a picture but a list that updates itself as you go. It works with the patch i built, but I was just wondering if this could be done in a better way. cheers!

[pattrstorage] is good to memorize the state of UI objects. I'm not sure it's what you need here. If it works, it's great! (there are certainly some optimizations, for instance the [t b i] after [ctlin] might not be necessary, and your construction with [uzi 8], [counter], [route] could be more simply presented with something like below, but that doesn't really change your patch).

wauw tnx! you're right i see now that the uzi 8, counter and route are unnecessary. took it out ;)

the t b i and swap are to get the cc adres before the parameter value. otherwise the list gets messy.

Save all last MIDI controller settings and bang values when needed