FA-81482 / MIDI event timing / Member archive

Tick to microsecond conversion through a tempo map: first of duplicate tempo events wins · case 02

When two tempo events share a tick, the earlier-listed one is kept instead of the later override.

Member previewVariant 2 · 3 implementations · 8 checks per implementation

Case contract

Input [ppq, changes, tick] where changes are [tick, microseconds_per_quarter] in any order (a later entry at the same tick overrides an earlier one). Before the first change the tempo is 500000. Each tempo applies from its tick onward. Sum the exact time of each segment and floor once at the end. Invalid ppq or negative tick returns None.

Why this case matters

MIDI sequencers, file readers and synth drivers depend on exact event ordering and tick/time arithmetic.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
oracle 4	`400000`	`350000`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.