Ross Erik Turner
Description:
Add multiplicative operators to parameters and actions so you can change a value
relative to its current value
(×, ÷) instead of only setting an absolute number—perfect for tempo (BPM), rates, grid lengths, delays, and other musical ratios.
Problem:
Many musical changes are
proportional
(double-time/half-time, dotted = ×1.5, triplet = ×2/3). Today this usually requires manual math, separate presets, or multiple actions. There’s no single, reusable way to say “multiply the current value by N”—especially across multiple targets at once.
Proposed Solution:
  • New math modes in “Adjust Parameter / Set Value”:
    Set / Add / Subtract / Multiply / Divide
    .
  • Factor input:
    number, percentage, or expression (e.g.,
    × 2
    ,
    × 1.5
    ,
    ÷ 3
    ,
    × (swingEnabled ? 1.5 : 1.0)
    ).
  • Musical helpers:
    quick chips for
    ×2 (double)
    ,
    ÷2 (half)
    ,
    ×1.5 (dotted)
    ,
    ×2/3 (triplet)
    ,
    ×4/3
    ,
    ×3/2
    , etc.
  • Scope:
    works for
    BPM
    ,
    grid/subdivision
    ,
    quantize interval
    ,
    LFO/rate
    ,
    delay time
    ,
    envelope times
    ,
    loop length (musical units)
    ,
    metronome/groove cycle
    , and any parameter with numeric/tempo timebase.
  • Constraints & safety:
    min/max clamps, unit rounding (e.g., BPM to 0.1), optional snap to musical steps; preview of
    resolved value
    before commit.
  • Batch apply:
    select multiple targets (e.g., BPM + delay + LFO rate) and apply one ratio; optional
    link
    so future changes propagate.
  • Actions & mappings:
    new actions
    Multiply Parameter by …
    and
    Divide Parameter by …
    ; MIDI bindings can call them directly.
  • Variables:
    prevValue
    ,
    newValue
    ,
    appliedFactor
    ,
    clamped
    exposed for labels/logic.
Benefits:
  • One-tap
    double/half-time
    and dotted/triplet conversions—no calculator, no duplicate presets.
  • Consistent musical transformations across different parameters and devices.
  • Faster experimentation and live morphs with safe limits and clear feedback.
Examples:
  • Tempo:
    BPM × 2
    to jump into double-time; later
    BPM ÷ 2
    to return.
  • Rhythmic FX:
    Delay Time × 1.5
    to toggle dotted echoes;
    LFO Rate × 2/3
    for triplet modulation.
  • Grid/Quantize:
    Grid Length × 2
    for halftime editing;
    Quantize Interval × 3/2
    for swingy grids.
  • Macro morph:
    One button applies
    ×0.5
    to envelope attack/decay while
    ×2
    to arpeggiator rate for a tighter feel, all in sync.
  • Expression-driven:
    parameter × (transport.isPlaying ? 1.5 : 1.0)
    —only dotted while playing.
This summary was automatically generated by GPT-5 Thinking on 2025-09-16.
```
Original Post:
Multiply Values(I.e. BPM)
Specifically, I use ClyphX Pro in Ableton to multiply the current bpm(with variable ramping, but that’s already implemented globally in LP) to allow for transposing keys alongside tempo by varispeed loopers, it’s about the only thing I can’t do in loopy to transfer my workflow
I.e.
a perfect fifth up with equal temperament would be
Bpm *1.498299124718113
Chromatic bpm modulation would do me but I imagine versus the present nudge value (addition), multipliers all round has broad use cases others could think of, I know nothing of the implementation but would hope it’s relatively similar to nudge being basic maths applied to a value
I’ve attached my bpm transpose scripts but yeah they’re literally just dividing one note Hz by another to determine intervals