Your launch monitor measures the ball.We measure you.
If you run a studio, you've already got the cameras, the PC and the launch monitor — so the outcome of every shot is no mystery. What's missing is what your body actually did to produce it, and whether you're really making the moves your coach asked for. That's the gap PinPoint Studio fills — and why it's named for the room it's built for.
Beta 1 — September 2026 First beta out now · still validating · 1.0 targeted late 2026
From the author of GoldenCheetah.
Illustrative — peak values are indicative; the kinematic sequence chart is in development.
Inside the studio.
A first look at the desktop app as it stands today — from setting up your kit, through replaying a swing beside its numbers and reading those numbers against a codified diagnostic model, to marking swings up by hand for validation.
Screens from the current pre-release build — the interface is still evolving.
Peer-reviewed science, in your hands.
PinPoint Studio exists to put the measurements the research actually supports into the hands of coaches, players and enthusiasts — methods drawn from the published literature, kept open for anyone to check, and led by the science rather than private interests.
We won't publish until the numbers can be trusted.
PinPoint Studio is an early prototype under active validation. Every measurement is being checked against a hand-annotated corpus of real swings before it goes anywhere near a release — because results you can't rely on are no use to anyone. There's a beta to try if you want to follow along, but nothing to depend on yet — and there won't be until we're confident the figures hold up. That bar is deliberate, and getting the science right is the whole point.
Three deep dives into that science in practice — written in plain English, not academic jargon:
How it works (for the nerds)
The full tour of the machine — devices, calibration, capture, inference, fusion, segmentation, metrics and diagnosis, stage by stage.
Read the whole pipeline ↗The science behind the score
How a captured swing becomes an honest number — the movements we measure, and the maths that stops one number hiding a real fault.
Read how scoring works ↗Finding the shaft in the blur
How we track a thin shaft moving past 100 mph — leaning on the golfer's anatomy and swing physics rather than fighting the blur, and how a bare club becomes its own ruler.
Read how tracking works ↗How we earn the numbers.
Trustworthy measurement isn't a claim, it's a process. We're building a hand-annotated corpus of real swings and testing every algorithm against it — so a figure only ships once we can show it agrees with the ground truth.
A corpus of swings
A growing library of captured swings — multiple cameras, IMUs and players, recorded under real studio conditions. The dataset every measurement is held against, kept varied enough to show where a method breaks.
A markup tool to annotate
A purpose-built tool to mark up each swing by hand — swing events, key positions and joint motion — turning raw captures into labelled ground truth a person has actually checked.
SwingLab holds them to it
SwingLab, our validation harness, replays the exact production pipeline over the corpus and scores it against physics invariants and the hand-labelled truth — with byte-identical regression gates, so a change that shifts a single number can't slip through unnoticed.
Ordinary kit, measured carefully.
PinPoint Studio reads the swing from hardware you can buy off the shelf — there's no sealed rig and no per-shot cloud round-trip. Five signals capture today — cameras, the phone in your pocket, wrist sensors of two kinds and, if you have one, your launch monitor; force estimation is on the way.
USB webcams or GenICam / FLIR industrial cameras — face-on and down-the-line. Every live feed carries an on-device pose skeleton. And one industrial camera can now take the impact view: cropped to a strip at the ball, a Chameleon3 runs at 591 fps on a 70 µs exposure, keeps just the frames around the strike, and loops them picture-in-picture beside the swing. The cameras you choose, not a locked box.
An iPhone running PinPoint Capture is a camera in the session, not a file you import afterwards — paired by scanning a QR code off the Studio screen, armed by the session's own Capture button, recording at 120–240 fps and delivering the clip to the swing library over WiFi or a cable. High-speed capture without high-speed cameras.
Off-the-shelf BLE IMUs (Witmotion WT901BLE67) at up to 200 Hz capture the wrist flexion, deviation and rotation a camera can't see cleanly — fused into joint angles on-device.
The HackMotion wG3 is supported as the criterion instrument for the wrist — its own calibration ceremony, a check-sensors page that speaks the device's reference frame, and forearm rotation reported under the vendor's own name. Angles are published in ISB convention, and its readings sit beside our strap-on IMU estimates rather than in place of them.
Studio plays the GSPro Connect server, so any monitor with an Open Connect bridge — a Garmin R10, Rapsodo MLM2PRO, SkyTrak+, PiTrac — connects straight to it; a Foresight GCQuad is read the other way, out of FSX2020. Either route, the readings are treated as a reference instrument: ball speed, spin, face and path recorded beside our own estimates, never replacing them. The Open Connect link is new, and so far proven against a simulator built from sixteen real clients rather than a device on a mat.
Ground reaction force, estimated from motion, so you can see how the swing loads, shifts and unloads through the strike. The science here is still young, so it's one we'll follow the research on rather than rush.
Your phone is a camera.
High-speed cameras are the biggest cost barrier to swing analysis — and most golfers already carry a device that shoots 1080p at 240 fps. PinPoint Capture, our iPhone companion app, makes that phone a first-class capture source: not a clip you film and import afterwards, but a device the session drives.
Pair it once
Press Pair to my phone and Studio puts a QR code on screen; scan it with the phone and you're paired. Scan again to add another — a down-the-line and a face-on — and a paired phone is remembered, on Windows and Linux as well as macOS.
It behaves like a camera
A paired phone appears in the device list beside every other camera, with its own live preview. The session's Capture button arms it along with the rest, and each phone reports its battery, its thermal state, whether it's on WiFi or a cable, and how well its clock agrees with Studio's — agreement now converges in 1–8 seconds.
The swing comes back
The clip the phone recorded is asked for, transferred over WiFi or a USB cable, and filed against the swing it belongs to in the library — replaying at the file's own frame rate, for as long as it actually is.
iPhone, while we build it
NowDuring initial development PinPoint Capture targets the iPhone — iOS 18 or later, on a phone that records 1080p at 120 fps or better. Its first screen checks the camera and tells you plainly whether it's good for capture. Development and hardware testing run on an iPhone 16. It goes to the App Store with the first release, at the end of 2026; until then it builds from source with Xcode.
Android, in time — not soon
LaterAndroid is coming, but it won't be quick. Its high-speed camera hands frames over in batches rather than one at a time, its camera and microphone don't always share a clock, and rolling-shutter timing has to be profiled model by model — each of which matters when the point is a millisecond you can trust. So the app is built for the port from day one: the core logic holds no iPhone code, device timing is data rather than code, and the protocol is the same on both. That makes Android a port rather than a rewrite — but it is still a port.
It talks to Studio over PPCP, the PinPoint Capture Protocol — an open specification with an MIT-licensed reference implementation, so any device can implement it and any host can read it. The spec and the library are public alongside the app, and the app's own source is MIT-licensed too.
Four ways to see a swing.
PinPoint Studio is built around four analysis modes. Wrist Motion and full Swing Analysis both produce real output today — under validation, not yet released; Ground Force and the AI Coach follow on the same capture pipeline.
Swing Analysis
Full-body kinematics from the captured frames — a 133-keypoint whole-body pose, shaft, club-head and ball tracking, and 52 swing metrics extracted today from a 95-metric catalogue: X-factor, club-head speed, lag, hip and shoulder rotation, tempo and more. Swing timing now speaks in P-positions: P1–P8 and P10 are resolved from the club track itself, arbitrated on what a reading is rather than which producer got there first. The whole-swing score is the piece still being built.
Wrist Motion
Lead-arm flexion/extension, radial/ulnar deviation and rotation read straight from the sensors, segmented across the swing and scored against coaching bands — the cupping, cocking and flipping a coach watches for. Works from our strap-on IMUs or from a HackMotion wG3, whose readings are kept beside ours rather than replacing them. The first full analyzer; its results are in validation now, not yet released.
Ground Force
Loading, weight shift and ground reaction force through the downswing — where the power comes from, not just where it ends up. The approach is scoped and the research reviewed, but it's gated on force-plate ground truth we don't yet have — so we'll let the science lead rather than rush. Realistically, something meaningful here is a late-2027 job.
AI Coach
Ask about your swing out loud and get answers spoken back — all on-device. The local language model (Phi-4-mini), speech in and out, and the conversation loop are already built and running; grounding it in your own session findings is the work in progress.
From numbers to a diagnosis.
Measurements alone don't coach. PinPoint Studio codifies the swing-fault literature into a causal model, then reads every session against it — so a number out of range becomes a named fault, a likely cause and a drill to work on.
157 swing conditions linked by 365 causal edges, 134 measures, 131 detection signals and 178 reference corridors, plus 17 physical screens and a drill library — drawn from a 40-source bibliography, every claim carrying its provenance. Browsable and editable inside the app, causal graph and all.
A shot fires findings; only a session diagnoses. Evidence accumulates shot by shot into a session ledger, patterns that recur are held to honest statistics — within a club, and counting only the shots that could actually be assessed — and causes are ranked along the model's authored chains. Because it is cumulative by construction, the ledger is the session summary at close: a finished session can be reviewed shot by shot in its own right without rewinding the live one, and the live panel casts to a second screen for the athlete.
Every verdict carries its receipt — the measurement behind it and the corridor it broke — and a finding with no number behind it says so rather than passing as fact. A reading outside its corridor says so, and never claims it is fine; where something can't be read, the panel says exactly why. Today's corridors are literature-seeded; re-seating them from measured swings is what the validation corpus is for.
Where it is, and where it's going.
PinPoint Studio reached its first beta in September 2026. Capture — cameras, phones, wrist sensors and a launch monitor — full-swing metric extraction, the diagnostic model and session diagnostics are all working; the whole-swing score, ball flight and the depth axis come next. It is still a beta, and we're still proving the numbers.
Working
- Multi-camera capture with live on-device pose overlay
- Impact camera — an industrial camera cropped to a strip at the ball at 591 fps, the frames around the strike looped picture-in-picture
- iPhone as a capture camera via the PinPoint Capture companion app, over WiFi or USB
- Post-shot analysis — 133-keypoint whole-body pose, shaft, club-head & ball tracking
- Markerless club tracking — a bare steel shaft read as its own ruler, so irons need no tape (graphite woods & hybrids still do)
- 52 swing metrics extracted today — X-factor, club-head speed, lag, rotation, tempo
- P-position timeline — P1–P8 and P10 resolved from the club track
- Live lead-arm wrist analysis, scored against coaching bands
- HackMotion wG3 wrist sensor as the criterion instrument, published in ISB convention
- Diagnostic model — 157 conditions, 365 causal edges, 178 cited corridors — editable in-app
- Session diagnostics — a cumulative evidence ledger, ranked causes, cast to a second display
- Session review — a finished session read back shot by shot, without rewinding the live one
- Launch monitors — GSPro Open Connect (R10, MLM2PRO, SkyTrak+, PiTrac…) and the Foresight GCQuad — measured values beside our estimates
- Shot detection — manual, IMU-impact and acoustic — with per-shot capture, replay & export
- Swing corpus, in-app markup tool & the SwingLab validation harness
- Local speech in & out (Whisper + Kokoro) and a local coaching LLM (Phi-4-mini)
In development
- Whole-swing 0–100 score — the scorer & uncertainty maths are built; full-swing bands being seated
- True kinematic-sequence chart from angular-velocity series
- P9 — the one rung of the P1–P10 ladder still deferred
- Club data from the impact camera — club speed, ball speed, angle of attack & low point, read at the ball
- Ball-flight tracking — ball speed, launch angle & direction
- Corpus v1 — re-seating the literature-seeded norms from measured swings
- AI coach grounded in your session findings (chat, voice & local LLM already built)
- Offline catch-up for the capture companion when the phone loses the host
On the roadmap
- Down-the-line camera & two-camera 3D — unlocks the depth-axis metrics (swing plane, club path)
- Ground reaction force — gated on force-plate ground truth (likely late 2027)
- Launch monitors that don't speak Open Connect (Uneekor, Bushnell) and more wrist sensors, on the same beside-not-instead-of contract
- PinPoint Capture on Android — designed for from the start, but a real port, and not a quick one
Built like an instrument.
Made for the people in the bay.
Teaching pros
Objective numbers to set beside what you already see — an evidence layer for a lesson, on hardware that fits a studio bay or a garage.
Serious amateurs
The wrist and sequencing measurements you've read about for tour players, applied to your own swing and the kit you choose.
Coaches & researchers
An open, inspectable platform for understanding golf movement — every metric traceable to the source, the source in the open.
You install it, you use it. That's the whole deal.
There is no registration, no account, no licence key and no trial. We don't ask for your name, your email or your club. There's no mailing list to join and no third-party processor in the loop — nothing to unsubscribe from, because there's nothing to subscribe to. It's free as in freedom and free as in beer, it is open source, and it will stay that way. Download the build, run it, and your swings stay on your own machine.
No account, no key, no activation, no “request access”. Download it and it runs.
Free as in freedom and free as in beer. GPL v2, source in the open — no paid tier, no pro edition, no upsell.
No mailing list, no analytics, no tracking, no third-party processors. We hold no details about you because we never collect any.
Swings, video and sessions are files on your own machine. Local by default — nothing goes to a cloud unless you set one up yourself.
Open in every way. PinPoint Studio itself is GPL v2. And when we write something another project could use, we don't leave it buried inside the app — we package it up as a standalone, MIT-licensed library, specifically so others can benefit from it. Talking to a HackMotion wrist sensor became libwrist; speaking GSPro Open Connect to a launch monitor became libgspro; the phone protocol is a published spec. We will always be open source, and we will always back the organisations and standards that are open too.
It's in beta — and it's yours.
PinPoint Studio reached its first beta in September 2026, with a 1.0 targeted for late in the year — once we're confident the measurements can be relied upon. There's no form to fill in and no list to join: take the build, run it, keep it. It's GPL v2 and built in the open — for golfers, coaches and researchers alike. Watch the repo if you want to hear when something lands, and bring questions to the issue tracker.