Allow Time-Based (ms/sec) Delay for Actions
planned
AJ Kerezy
Description:
Currently, Loopy Pro allows actions to have a "delay" in execution, but this delay can only be expressed in beats or bars. Some actions also include a "RAMP" time setting, which provides a UI display to set time in milliseconds (ms) or seconds. This feature could be extended to cover all actions that require a delay.
Problem:
When users are not using the metronome or LP clock, it can be challenging to calculate delays solely in terms of beats or bars. This limitation makes it difficult to time actions precisely, especially when a non-musical or time-based reference is needed.
Proposed Solution:
Allow the delay for actions to be set in either:
- Beats/Bars (existing functionality)
- Milliseconds (ms) or seconds (new option)
Reuse the existing "RAMP" interface to implement this feature. This will make it easier to set precise time-based delays without relying on the metronome or BPM-based calculations.
Benefits:
- More flexibility when using Loopy Pro without a metronome or clock reference.
- Enables precise timing for actions not tied to musical beats.
- Simplifies the process of setting delays for users who prefer direct time input.
This summary was automatically generated by ChatGPT-4 on 2025-05-07.
David Gill
104ms, 208ms, 416ms sit snugly with 4 beats (and multiples) to the bar. Perhaps just a toggle for on/off and a tap to cycle those three. A slider option that allows for 'volume' of this would rock because an expression pedal doing the same on a Katana definitely works and allows one to understate, turn off or space out on delay.
Michael Tyson
planned
ultracello
under review