Ability to Set Precise Custom Min/Max Values for Plugin Parameters (Instead of Approximate “0%–100%” Ranges)
under review
ultracello
Description:
Enable users to define
precise custom minimum and maximum values
for plugin parameters (e.g. MIDI knob control ranges), instead of relying solely on the current vague and limited “0%” to “100%” range. This would allow for fine-tuned control over parameter ranges and improve accuracy when using external MIDI controllers.Problem:
Currently, Loopy Pro does
not provide direct access to the actual numerical values
of plugin parameters. Users are limited to using 0% and 100% as vague placeholders, which often results in non-precise control
, especially for plugins with many discrete values. For example, you might want to set a range from
200 to 220
, but due to rounding, Loopy Pro might only let you jump to 200, 205, 210, 215, or 220. This makes fine-grained automation or modulation impossible
. In contrast, other apps like
AUM
allow precise mapping of plugin parameter ranges to controller inputs.Proposed Solution:
– Allow setting
absolute numeric min and max values
for plugin parameter controls – Permit entering exact numbers (e.g., min: 202, max: 209) instead of relying on percentages
– Provide a
dropdown or direct entry field
for manual values, snapping to the nearest available plugin step if needed – Display plugin’s available parameter steps or ranges clearly
– Fall back to rounding only when absolutely required
– Optional: Show parameter values dynamically in the UI for feedback
Benefits:
✅ Improved precision when controlling plugin parameters
✅ Much more useful for high-resolution controls and MIDI hardware
✅ Consistent with other pro-grade apps (e.g., AUM)
✅ Prevents misalignment of parameter control and intended ranges
✅ Supports creative workflows where exact control over filter cutoffs, resonance, pitch shifts, etc. is needed
This summary was automatically generated by ChatGPT-4 on April 30, 2025.
Videos:
<- I could imagine that in this particular case the plugin parameter itself is filled with rounded numbers, something like
200, 205, 210, 215, 220 etc. and not 200, 201, 202, 203, 204, etc. In this case I would expect a drop-down menu with all the numbers of the plugin parameter but I think even then you should be able to enter manually a wished number and then the next-possible number will be rounded. Let's say, in this case you enter "202", this will make jump to "200". Or if you enter "209", this will make jump to "210".
Anyway, in LP this "%" thing is too limited and not precise:
https://files.slack.com/files-pri/T022K0Z9A5T-F08HDBHGQUQ/bildschirmfoto_2025-03-07_um_16.49.17.jpeg
Slack-Thread:
ultracello
under review