gbravetti

By default "live." control objects (i.e. live.slider, live.numbox) are MIDI mappable out of the box.

I tried to MIDI map non "live." control objects (slider) without success.

Is there some way to directly MIDI map non live(dot) control objects?

By default "live." control objects (i.e. live.slider, live.numbox) are MIDI mappable out of the box.
I tried to MIDI map non "live." control objects (slider) without success.

Is there some way to directly MIDI map non live(dot) control objects?


midi-mapping-non-live-objects

I assume that you are trying to midi map non live. UI elements in Live.

One of the unique things about the live. UI things is that they CAN be mapped in Live. Standard max UI elements can not be midi mapped in Live.

I assume that you are trying to midi map non live. UI elements in Live.
One of the unique things about the live. UI things is that they CAN be mapped in Live. Standard max UI elements can not be midi mapped in Live.


you question is possibly related to you other post about changing the live.slider range. I just posted a possible aproach there.

Hi GBRAVETTI,
you question is possibly related to you other post about changing the live.slider range. I just posted a possible aproach there.


Regardless of what the assumptions are about his intentions,

Regardless of what the assumptions are about his intentions,
Is there some way to directly MIDI map non live(dot) control objects?

with the new MIDI map mode inside max and "visible to mapping" parameter there seems to be no reason why standard max objects should not be mappable in live when this is all properly setup in max.

(there is a way to expose non live. objects to appear on the automation lane of a clip in live, but it should not be regarded as the same thing as going into midi map mode)

Also interested in this, I have quite extensive configuration setup on several non live. objects in my patch, including "visible to mapping". However these objects are still not visible in MIDI map mode.

Perhaps there's an auxiliary object that can be connected to the object to allow it to be mapped to MIDI in Live? Something akin to how the pattr object allows saving parameter configuration of non live. objects.

Also interested in this, I have quite extensive configuration setup on several non live. objects in my patch, including "visible to mapping". However these objects are still not visible in MIDI map mode.

Perhaps there's an auxiliary object that can be connected to the object to allow it to be mapped to MIDI in Live? Something akin to how the pattr object allows saving parameter configuration of non live. objects.


Ended up moving forward with a hack that creates "shadow live. objects" for the non live. objects whose UI I want to keep inplace. These shadow objects take in the same range of values as the non live. objects and simply forward the information. They are not visible in the actual UI, just to MIDI mapping.

This works I guess but obviously rather clunky, having mapping support for non live. objects would still be ideal.

Ended up moving forward with a hack that creates "shadow  live. objects" for the non live. objects whose UI I want to keep inplace. These shadow objects take in the same range of values as the non live. objects and simply forward the information. They are not visible in the actual UI, just to MIDI mapping.

This works I guess but obviously rather clunky, having mapping support for non live. objects would still be ideal.


MIDI Mapping non live. objects