Julien-Robert

I noticed that when a M4L object is MIDI mapped and receive the same data as it's set, it doesn't output that signal. Maybe this option is there to avoid unwanted duplicated signals. Anyway, how can I bypass that?

For example, I have a live.numbox showing 0 and is mapped to a midi controller. If I send 0 with my midi controller, that 0 won't pass through...

mapped-objects-always-outputting-data

it seems logical that doubles are filtered out... in most cases everything you want to change by midi controller input is an active parameter - and those would normally be initialized, when not by a preset, then at least by a loadbang.

yes it might be logical but I need to find a way around. My MIDI controller (switch 0-127) changes of channel while I'm playing, so when I come back to the mapped channel, the controller might be at the wrong state and sending the same midi ctrl twice... but I want the data to get through anyway.

The idea is simple: when any data is coming in, I want to perform an action.

yes it might be logical but I need to find a way around. My MIDI controller (switch 0-127) changes of channel while I'm playing, so when I come back to the mapped channel, the controller might be at the wrong state and sending the same midi ctrl twice... but I want the data to get through anyway.
The idea is simple: when any data is coming in, I want to perform an action.


mapped objects always outputting data