Problem

Currently, MIDI controls appear to be bound to clips or widgets by their index/name (e.g. Clip 15, Slider 7). This works only as long as the page structure remains unchanged.

As soon as a clip or widget is added, removed, or reordered, indices shift and all existing MIDI bindings break or point to the wrong targets.

Impact

• MIDI mappings frequently become unreliable after minor layout edits

• Requires rebuilding MIDI bindings from scratch

• Discourages iterative page design and live set refinement

• High risk of failure in performance contexts

This has happened to me repeatedly and costs significant setup time.

Proposed Solution

Bind MIDI controls to a persistent internal ID for each clip or widget, rather than a positional index or name.

Once a MIDI control is assigned to a specific clip or widget:

• The binding should remain intact regardless of page reordering

• Moving the target on the page should not affect MIDI behavior

• Only explicit deletion of the target should invalidate the binding

Why This Matters

Loopy Pro strongly encourages experimentation and modular page design. Stable, object-based MIDI bindings would:

• Make complex setups far more robust

• Enable confident page iteration

• Greatly improve reliability for live performance use

Summary

Please hard-bind MIDI controls to the actual clip/widget they are assigned to, not to their current index or label. This would eliminate a major source of broken mappings and improve workflow stability.