FA-81720 / MIDI event timing / Member archive

Active sensing timeout detection: exact 300 ms gap reported as timeout · case 05

A gap of exactly 300 ms triggers a timeout although only gaps longer than 300 ms should.

Member previewVariant 5 · 3 implementations · 8 checks per implementation

Case contract

Input [messages, end_time] where messages are time-ordered [ms, kind]. Monitoring is armed by a "sense" message. While armed, if more than 300 ms pass between any two consecutive messages (of any kind), a timeout is reported at previous message time + 300 and monitoring disarms until the next sense message. At end_time the same check applies to the last message. Return the list of timeout times.

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 1	`[300]`	`[]`	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.