Loop Phase from Ticks

Locate a signed musical tick in a repeating loop, retaining cycle carry and normalized phase.

Description

Locate a signed musical tick in a repeating loop, retaining cycle carry and normalized phase.

Loop position should remain nonnegative even for a negative absolute tick. The cycle count uses mathematical floor.

When to use this tool

Locate a signed musical tick in a repeating loop, retaining cycle carry and normalized phase.

  • Prepare the supplied tick, loopTicks fields for this operation.
  • Compare the complete example with the representation used by your own input before carrying the result into another step.

How to use the tool and how it works

  1. Enter tick, loopTicks. Use the exact text syntax, units and index conventions explained below.
  2. Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
  3. Read result.position, result.cycle, result.phase. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.

Require positive loopTicks. position is nonnegative tick modulo loopTicks, cycle is floor(tick/loopTicks) and phase is position/loopTicks.1

Input fieldMeaning and representationAccepted input
ticktick.Integer from -1e9 to 1e9 inclusive
loopTicksloop ticks.Integer from 1 to 1e9 inclusive
Output fieldInterpretation
resultObject containing the named outputs below.
result.positionZero-based matching position, or null when the requested match is absent.
result.cycleThe cycle value under the stated formula or text convention.
result.phaseThe phase value under the stated formula or text convention.
json
{
  "input": {
    "tick": -1,
    "loopTicks": 8
  },
  "output": {
    "result": {
      "position": 7,
      "cycle": -1,
      "phase": 0.875
    }
  }
}

Limitations and assumptions

  • phase is a fraction in [0,1). No tempo, playback or wall-clock conversion is included.
  • Every declared top-level field is required and unexpected fields are rejected. Numeric inputs must be finite; ordinary text fields are bounded to 8,192 UTF-16 code units, with tighter operation-specific limits where stated.
  • Lists are limited to 128 entries. JSON text must meet bounded size and depth checks, and numeric outputs beyond the safe finite magnitude are rejected. Exact large integers use decimal strings.
  • Indexes are zero-based and spans have an exclusive end unless explicitly stated otherwise. A valid false, null or empty-list result is distinct from malformed input.

Alternative or Complementary methods

Retain the tick unit, channel numbering and event-pairing policy with the result. Use a MIDI-file parser or audio analysis when the task requires actual messages, playback behavior or recorded sound.

References

  1. Tool behavior and example: Loop Phase from Ticks — tool.io

Similar or alternative tools

Don't forget to set a bookmark for tool.io!
Privacy | Imprint | Cookies