We have been testing a new metronome calibration path built around the Serene timing work.

The process is familiar: the game plays a steady beat, the player taps along, and OutFox measures the difference between the expected beat and the input it received. From that, it can suggest a global offset.

The awkward part is that people do not tap with machine-like consistency.

Even an experienced player will have some variation between taps. A few may land early, a few late, and an otherwise useful test can contain one or two poor inputs. The older calibration logic could treat that spread too harshly and reject the result outright.

We have changed that behaviour; the tool still warns when the taps are inconsistent, but it can now allow the tester to use the median result when the underlying timing remains stable. That keeps obviously noisy data visible without throwing away an otherwise useful measurement.

We also corrected how the suggested offset is applied.

When a tap arrives late, the measured difference is positive. The correction has to move in the opposite direction, so the applied global offset is negative. The previous flow did not make that relationship clear enough and could make a valid result appear backwards.

The new path now shows and applies that correction consistently, calibration also works properly with the normal save and revert controls. A tester can try the suggested value, keep it if the result improves, or leave without the engine retaining a half-applied change.

The aim is not to pretend that every set of human taps is perfect. It is to give the tester enough information to judge the result, while making sure OutFox applies that result correctly.

The Serene metronome now handles variable taps more sensibly, gives clearer offset results, and fits properly into the engine’s existing settings flow.