member badge
ultracello
Description
This feature request proposes the implementation of a mechanism within Loopy Pro that allows users to trigger specific actions when faders or knobs reach predefined positions. This functionality would enable more dynamic and responsive control setups, enhancing live performance capabilities and workflow efficiency.
Problems
  • Limited Interactivity
    : Currently, faders and knobs in Loopy Pro adjust parameters but cannot trigger actions based on their position, limiting their utility in complex setups.
  • Workflow Constraints
    : Without the ability to initiate actions at specific control positions, users must rely on additional buttons or external controls, complicating the interface.
  • Reduced Expressiveness
    : The inability to link control positions to actions restricts creative possibilities during live performances and sound design sessions.
Proposed Solution
  • Position-Based Action Triggers
    : Introduce the ability to assign actions that are triggered when a fader or knob reaches a specific value or crosses a threshold.
  • Customizable Thresholds
    : Allow users to define multiple thresholds per control, each linked to different actions, enabling complex interaction schemes.
  • Integration with Existing Systems
    : Ensure compatibility with Loopy Pro's MIDI Learn system, widgets, and automation features for seamless integration.
Examples
  1. Dynamic Effect Activation
    : A performer sets a fader so that increasing the value beyond 75% automatically enables a reverb effect, while decreasing it below 25% disables the effect.
  2. Scene Switching
    : A knob is configured to trigger different scenes or sections in a performance as it passes through defined positions, streamlining live transitions.
  3. Parameter Modulation
    : Crossing a specific threshold on a control could initiate a modulation sequence or trigger a sample, adding expressiveness to performances.
Benefits
  • Enhanced Control Flexibility
    : Users can create more interactive and responsive control setups, reducing the need for multiple dedicated controls.
  • Improved Workflow Efficiency
    : Automating actions based on control positions simplifies complex tasks, making the interface more intuitive.
  • Expanded Creative Possibilities
    : Linking control positions to actions opens new avenues for creative expression in both live and studio environments.
This summary was automatically generated by ChatGPT-4 on 2025-05-17.
Original Post:
Example: you added a fader on canvas – with let's say 16.383 steps (what is the maximum of 14 bit MIDI btw, right? – MIDI 2.0 will give us even finer resolution: 32-bit. Hopefully MIDI 2.0 won't take another decade – those inaccurate 0-127 steps are just not fine resolution enough.)
Let's say (just an example) you can set up two ranges. One range is between 2.000 and 3.999. The second range is between 5.000 and 5.500. When reaching position 2.000 (or dialing from the opposite (downwards), reaching position 3.999) the fader will send an action. Then later at position 5.000 (or dialing from the opposite (downwards), reaching position 5.500) the fader will send another action.
Now another but more very flexible example: let's say you have this said fader on your canvas with all said above BUT now the range between 2.000 and 3.999 is sending constantly values (for instance to MIDI or another already in canvas available fader or to an AUv3 plugin knob/fader parameter).