Blast Vision looks for small objects moving like a hit ball, so it can occasionally register a “false swing” even when no ball was actually hit. This is a normal part of how the camera-based detection works, and you can simply delete the false swing from your session.
Why This Happens
The app is scanning for any small object that moves in a way similar to a struck ball. Several common situations can be mistaken for a hit ball, including:
- A practice swing with no ball
- A pitched ball crossing the frame
- Someone walking in front of the camera
- Background movement near the hitting area
- Shadows moving across the ground
Blast Motion is continually working to reduce these false detections, but because the system relies on visual movement, occasional false positives are expected.
How to Fix It
If a false swing appears in your session, simply delete it:
- Open the session where the false swing was detected.
- Locate the swing that doesn’t match an actual hit.
- Delete the false swing entry.
This keeps your swing data accurate and prevents the false detection from affecting your metrics.
FAQ
Why does Blast Vision think I hit the ball when I didn’t?
The app detects any small object moving like a ball, so practice swings, pitched balls, people walking by, or shadows can occasionally trigger a false detection.
Do I need to contact support for a false swing?
No. False swings are expected occasionally and can be resolved by simply deleting them from your session.
Will false swings affect my real swing metrics?
Only if left in your session data. Deleting the false swing keeps your recorded metrics accurate.