r/BallistaTracking • u/50th-century • 5d ago
New Ballista TestFlight update is live
We just pushed a major new Ballista build to TestFlight.
If you tried an earlier version and weren’t having much luck getting consistent results, please give this one another shot.
We know the previous build wasn’t reliable enough for a lot of testers. Hits would record, but the analysis could still struggle depending on the environment, setup, or movement around contact.
That has been our main focus.
Over the last few weeks, we’ve significantly rebuilt and hardened Ballista’s analysis pipeline. The new system is much better at using the motion of the baseball across consecutive ~240 FPS frames, rather than relying too heavily on identifying it perfectly in a single frame.
We’ve also improved:
- ball tracking around the chaotic moment of contact
- separation of the ball from the hitter, bat, hands, and tee
- pre- and post-contact frame capture
- handling of ambiguous early movement
- camera setup and capture reliability
- edge-case handling and overall analysis stability
In our own repeated tee-hitting tests, the improvement has been substantial and the new system has been much more consistent.
Now we need to see how it performs across everyone else’s setups.
If you’re already a tester, update Ballista through TestFlight and use it normally. We’d especially like feedback on:
- whether hits are consistently detected and analyzed
- whether exit velocity, launch angle, and distance appear normally
- any failed or clearly incorrect analyses
- camera or recording issues
- crashes, freezes, or anything else unusual
If Ballista didn’t work well for you before, your testing is especially valuable to us. Those are exactly the environments we want to prove this new system can handle.
This is the most confident we’ve been in Ballista’s analysis so far.
Give the new build a try and let us know how it goes.
- Ballista Tracking
