Filming Darts in Slow Motion: Camera, Frame Rate and Review

Why the movement reveals more than the result

A dart throw is one of the fastest movements in precision sport. From the pull back to the release, most players take between 300 and 600 milliseconds. The human eye takes in roughly ten to twenty separate impressions in that window, and during the throw your brain is busy aiming on top of that.

This is why the scoreboard helps so little with technical questions. It shows where the dart landed, not what happened on the way there. Dart motion analysis turns that around: it stops the movement, breaks it into individual frames and makes visible what is impossible to observe in real time.

What a dart motion app actually does

The core of any motion analysis is simple to describe: the camera records many frames per second, the app processes each one of them and assembles the results into a sequence. A fluid movement becomes a chain of snapshots you can examine one by one.

Beyond that, good apps place an overlay on the image. It shows the detected joint points, the connecting lines between them and often a trail tracing the path of the hand across recent frames. This overlay is more than decoration: it lets you check whether the detection sits correctly before you trust the numbers.

The third component is evaluation over time. A single throw in slow motion is interesting, but the actual insight only appears when thirty throws are laid on top of each other. That is when you see whether an irregularity was a one off or a pattern.

Frame rate: why 30 frames per second is often too few

At 30 frames per second there are 33 milliseconds between two captures. Applied to a throw lasting 400 milliseconds, that gives you roughly twelve frames for the whole movement. Enough for the rough structure, not enough for the moment of release.

The release itself takes a few milliseconds. At 30 frames per second it very likely falls between two captures and simply is not recorded. At 60 frames the gap halves, at 120 frames the moment can be pinned down usefully. If your device offers a higher frame rate, that is the parameter that decides accuracy most.

A higher frame rate does need more light, though. The shorter the exposure per frame, the darker each individual frame becomes. In a poorly lit basement, 120 frames per second ends up producing worse detection than 60 frames in decent light.

What you can actually see in slow motion

Not everything that happens in a throw is visible on video. What you can make out depends directly on how many frames fall on the movement in question.

Clearly visible at 30 frames per second are things that persist across the whole throw: the stance, whether the upper body tips during the motion, whether the shoulder travels along and whether the arm swings out at the end or gets stopped. These features last long enough to appear on several frames.

Only assessable from 120 frames per second are questions of timing: the exact moment of release, whether all fingers open simultaneously and how the transition from backward to forward motion runs. At lower frame rates there are simply too many milliseconds between two frames.

Not visible at all are grip pressure and muscle tension. They clearly affect the throw but leave only indirect traces on video, such as an abruptly stopped arm.

This split avoids the most common disappointment in video review, which is hunting for release timing with an ordinary recording. Which phases the throw has at all and what happens in each is described in the article on the five phases of a dart throw.

Motion app or just filming with your phone

An honest answer: for a start, an ordinary video recording is enough. Set the phone up to the side, film ten throws and watch them in slow motion. Obvious irregularities like a wandering front foot or a cut short follow-through are visible immediately, without any app.

There are two points where this stops working. First, anything you would have to count or measure. Whether your elbow angle varies by two or by eight degrees across thirty throws cannot be judged by eye, and nobody measures thirty still frames with a protractor. Second, comparison across weeks. Putting videos from a month ago next to today's and drawing a conclusion from them is barely possible without numbers.

This is exactly where mydart comes in. The movement is captured, translated into values and stored across sessions, so that comparing training sessions works without any evaluation work of your own.

A workable routine

For a session with motion analysis, this sequence has proven itself:

• Fix the camera position. To the side of the throwing arm, roughly at shoulder height, three to four steps away. What matters most is that the position stays the same across sessions.
• Warm up before recording. The first ten to fifteen throws are rarely representative and drag the evaluation down.
• Record at least thirty throws. Anything below that produces impressions, not patterns.
• Only review after the session. Checking values in between changes your movement unconsciously, and you end up measuring something different from before.
• Pick one irregularity. Take the clearest deviation and work only on that one for the next few sessions.

What most players notice first in slow motion

Three observations come up for almost everyone seeing their movement slowed down for the first time. The first concerns the head: many move it slightly during the throw, which shifts the view of the target mid movement. The second concerns the back leg, which for many players lifts at the moment of acceleration and changes the stability of the stance.

The third is the most surprising: your own throw almost never looks in slow motion the way it feels. Movements that feel fluid often show a small stop at the turning point on screen. This gap between sensation and actual movement is the real reason the outside view is worth having.