FA-81748 / MIDI event timing / Member archive

Same-pitch and monophonic overlap truncation: overlaps resolved in input order · case 03

When notes are listed out of time order, the later-listed earlier note is never truncated by the note that follows it in time.

Member previewVariant 3 · 3 implementations · 8 checks per implementation

Case contract

Input [notes, mode] where notes are [start, end, pitch] in any order and mode is poly or mono. Sort by start then pitch. Each note ends no later than the start of the next note that starts strictly later and has the same pitch (poly) or any pitch (mono). Notes whose length becomes zero or negative are removed. Return the notes in sorted order; unknown mode 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 0	`[[5, 15, 60], [0, 10, 60]]`	`[[0, 5, 60], [5, 15, 60]]`	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.