← back to chapter

warp-math · when the data is messy

Every example up to here has fed the math a tidy marker list. Real beat_this output is noisier: timestamps jitter by milliseconds, the tracker occasionally drops or doubles a beat, and the seconds column can lose monotonicity under careless editing. This chapter sees those problems — it does not fix them. Fixing is a judgement call, which is precisely why warp markers are hand-editable.

beat timestamps (one per line, seconds)
thresholds

paste or load a sample to begin.

Per-segment BPM along the marker list. dots are clean segments; dots are flagged by flagAnomalies. A clean recording is a flat line in this view; spikes and dips are exactly the dropped/doubled beats the chapter is about.

anomalies

Empty when the data is tidy. When it isn't, this is the report flagAnomalies hands back — one row per heuristic hit, with the segment index, the kind, and the detail. None of this is a correction; the math layer trusts you to decide.

segmentkinddetail