MIDI Kinetics Forum

No worries,
Have a look at the LeLearn stuff above, it shows one way to do it ...
Pretty sure this can be modified to deal with sysex ...
Though ultimately wouldn't you only need to do it once?
It may be easier to just capture the data once and then code it as needed...

Maybe something along this line, adjusted as needed as per other objects...
Note: The data length and variable position will need to be set up to match your device
cheers

Macciza wrote:Traxus - LeLearn https://forum.liine.net/viewtopic.php?f ... arn#p16331

Ah cool, same thing i had in mind but without the abstraction; i was thinking just one midi listen and assignment script rather than putting on on each object might be cheaper to on a larger project but managing the 4 vectors (object pointer, channel, cc, val) seemed latency prone...

Macciza wrote:Maybe something along this line, adjusted as needed as per other objects...

test.jzml

Note: The data length and variable position will need to be set up to match your device
cheers

Thank you very much.
I'll give this a try.

Will the captured data persist after Lemur is closed?

you would simply need to save the project (to a new file perhaps) on your Lemur first before closing ...

Sounds good. Thank you.

Working hard to understand how this design works. Looks very slick.
I must learn more about and practice some Lemur programming.