Shakeeb Alireza

In my modular looper project (https://github.com/shakfu/groovin), I have umenu dropdowns on the main page which load different 'modules' into bpatcher box using scripting "sprintf script sendbox channel1 replace grv_chan_%s_bp.maxpat" where %s is set by the umenu choice.

When I try to midi map some of the controls inside a bpatchers to say a MIDI Twister, it works well if I don't change the bpatcher module. If map everything and save, and then reload the project, even though all the midi mappings are captured in the mappings page, I cannot control any the ui controls with the midi controller.

So I am presuming that this is a limitation of the current system. Are there any ways to solve this use case?

Otherwise, I guess I have to have a static system in order to retain mappings...

In my modular looper project (https://github.com/shakfu/groovin), I have  umenu dropdowns on the main page which load different 'modules' into bpatcher box using scripting "sprintf script sendbox channel1 replace grv_chan_%s_bp.maxpat" where %s is set by the umenu choice.

So I am presuming that this is a limitation of the current system. Are there any ways to solve this use case? 

Hi,
In my modular looper project (https://github.com/shakfu/groovin), I have  umenu dropdowns on the main page which load different 'modules

midi-mapping-issue-with-dynamically-loaded-bpatchers

Answering my own question: looks like one has to use `live.` objects for the case of midi mapping objects inside bpatchers.

MIDI mapping issue with dynamically-loaded bpatchers