Cédric Vosgien
Description:
Allow users to defer project tempo detection to a loop other than the first — enabling Loopy Pro to set the project tempo based on a later, user-selected loop.
Problem:
Currently, Loopy Pro determines and locks the project tempo based on the very first recorded loop. This limits flexibility in sessions where the first loop is not rhythmically relevant or is intended to be free-tempo (e.g. ambient texture, drone, or vocal swell). Users have no option to tell Loopy Pro to wait and derive the tempo from a different, later loop that better represents the intended timing.
Proposed Solution:
Add a feature that allows users to:
  • Bypass tempo detection from the first loop
  • Optionally choose which loop (e.g. second, third, or any later one) should define the project tempo
  • Or let Loopy Pro auto-detect tempo from the first
    rhythmically meaningful
    loop
This could be implemented as a toggle or dropdown in the project/session settings.
Benefits:
  • Greater control over when and how project tempo is set
  • Enables free-form intros and ambient starts without locking the grid too early
  • Better suited for complex arrangements and live workflows where rhythm develops gradually
  • Improves compatibility with creative, non-linear loop layering
Examples:
  • First loop: ambient pad (no timing) → ignored
  • Second loop: rhythmic guitar riff → sets tempo
  • Third loop: beatbox loop → sets tempo while earlier ones remain unquantized
This summary was automatically generated by ChatGPT-4 on 2025-05-17.
Original Post:
Currently, LP fix the project tempo thanks to the first loop recorded. The aim of this new feature is for LP to fix the project tempo thanks to the detection of the tempo of a loop other than the first one (or first ones pre-chosen).