member badge
ultracello
Description
Currently, Button and Stepper Dial Widgets can trigger specific values on an XY Pad widget (e.g. X: 55%, Y: 80%). This is useful for recalling XY positions but lacks the precision required when the XY Pad controls specific AUv3 parameters or internal Loopy Pro parameters.
Problem
The current percentage-based control is not ideal when an XY Pad axis is mapped to multiple parameters. For example, if both “Reverb Decay” and “Delay Time” are mapped to the Y axis, setting “Y = 80%” affects both — without the ability to precisely target one of them. Furthermore, users can't define explicit parameter values like “1.2s Delay Time” or “50% Reverb”.
Proposed Solution
Allow both
Button Widgets
and
Stepper Dial Widgets
to target specific parameters controlled by the XY Pad.
  • Instead of assigning “X = 55%” or “Y = 80%”, users should be able to select a concrete parameter (e.g. “Delay Time”) and set its precise value.
  • If multiple parameters are mapped to the same axis, users should choose the exact parameter to target.
  • Setting one parameter will internally adjust the XY Pad position accordingly, and co-mapped parameters will update as a result — which is expected behavior.
Benefits
  • Enables precise, intentional parameter control via Button and Stepper Dial Widgets
  • Better support for performance setups involving AUv3 plugins
  • More predictable and accurate interaction between widgets and XY Pad mappings
  • Unlocks the full potential of parameter-based modulation without needing to rely on percentage estimates
Examples
  • Button A: Set “Delay Time” (mapped to X-axis of XY Pad 1) to
    0.5s
  • Stepper Dial: Adjust “Reverb Decay” (mapped to Y-axis of XY Pad 1) between
    0.3–1.2s
    in steps
→ Loopy Pro internally calculates the XY Pad position and applies the new values, including updating any linked parameters.
This summary was automatically generated by ChatGPT-4 on 2025-06-05.