RaceSplitter 1.5 — Auto-split mode and rapid-fire timing

RaceSplitter 1.5—presently awaiting approval at Apple—addresses two of our most common feature requests — the ability to disable RaceSplitter's auto-split mode, thereby preventing splits from being added to the race when the timer accidentally times the same bib number twice, and the ability to quickly create bib-less timing entries.

Ability to disable auto-split mode

Each time that a given bib number is timed, RaceSplitter will add an additional split (lap) on the race. This ability to "auto-split" is a key benefit of RaceSplitter for coaches of sports like nordic skiing, where the race course consists of multiple laps.

For organizers of simple mass start races, however, this feature can present difficulties. Here's why.

The problem

Imagine a trail running race with 300 competitors. At some point, racer 123 comes across the finish line and the timer accidentally mistypes the bib, recording an entry for bib number 132.

Half an hour later, the real racer 132 comes across the line, and the timer records an entry for 132. Since this is the second time RaceSplitter has recorded bib 132, it assumes we have a multi-lap race and creates a second split/lap on the race.

When the last racer crosses the line, the RaceSplitter clock is stopped. The race organizer looks at the result, and is surprised to see only one finisher—racer 132—and all other participants listed as DNF (Did Not Finish)!

How did this happen? Since RaceSplitter only timed one person in Lap 2, it has to assume that nobody else finished the race.

The solution: disable auto-split mode

To help organizers of mass-start races avoid this problem, RaceSplitter‘s auto-split mode setting can be disabled, thereby disallowing additional splits to be automatically created while timing the race.

When a given bib number is recorded multiple times while auto-split mode is disabled, RaceSplitter will assign subsequent timing entries according to a particular number scheme that allows the organizer to later identify and correct them.

Example: multiple timing of the bib 132

  • First: 132 Matt Henderson
  • Second: 10132 Unnamed
  • Third: 20132 Unnamed

As you can see, RaceSplitter will assign subsequent timings of a given bib to a five-digit number, in which the entered bib can be identified by the last digits (132, in this case).

After the race, the organizer still has to identify these entries, and correct the bib numbers, but at least he doesn‘t face the potentially confusing situation of multiple (unintentional) splits.

Important note: Disabling auto-split mode doesn't prevent the race from having multiple splits! It just disallows a given device to time multiple splits. So if a trail running organizer has three people timing the race at different locations, all with auto-split mode disabled, each will be able to time a single split.

When the results are published to RaceSplitter.com, however, the website will automatically correctly create additional splits on the race.

Rapid-fire bib-less timing

Sometimes racers are passing by so quickly, that you need to record a timing entry without having seen the participant's bib number. In mass-start races, when auto-split mode is disabled, the "Record" button will remain permanently highlighted, allowing the recording of bib-less timing entries—or rapid fire timing.

Whenever a bib-less timing entry is recorded, RaceSplitter will create an entry assigned to a five-digit number beginning with 90001, e.g.:

  • 90001
  • 90002
  • 90003
  • etc.

In this way, rapid-fire entries can easily be identified and corrected after the race.

Of course, to correct the entries later would require that you've had someone manually writing down bib numbers to capture the finish order, so be sure to plan for this if you intend to use this feature.