If Velogic Studio can't find a valid skeleton from 7 (or 8) dots, it will instead show you red dots for the markers it did find.
You can watch as the rider pedals and see if one of the markers is occasionally not being shown as a red dot. If you notice that, adjust the problematic marker so that the camera can see it better.
If you see additional red dots in the scene (like the one on the front wheel rim above), you may need to obscure it e.g. by covering with masking tape. Note that Velogic Studio can cope with some additional reflections, particularly if they're nowhere near a valid marker position; but if there are many additional reflections, or they are near a valid marker position, you will need to cover it up.
Check marker placement
- Shoulder marker placed too high
- Wrist marker rotated too far away from camera
- Heel marker (if used) too far down on the shoe
Check correct number of dots selected (7 or 8)
There's a configuration setting on Step 1 which tells Velogic Studio whether you're using 7 markers, or 8 (including a heel marker). Make sure that the setting matches the actual number of markers you're using.
Look for other reflections highlighted as red dots
- Logos or tabs on shorts, jersey and shoes
- Shiny parts on the bike
- Alloy rims
We have a lot of filtering in the detection process to eliminate the extra reflections and the high grade markers (the material printed on the VF-Tape is night-vision rated) are part of how we distinguish between wanted and unwanted reflections.
Unusually large/small/unusually-proportioned rider?
To help Velogic Studio filter out unwanted reflections, it has some internal rules to make sure that the skeleton formed by the markers could reasonably form a human body. Some of the rules are around proportionality, and some involve sizes of body segments.
Sometimes you may encounter a situation where a rider breaks one of our proportionality rules (more likely with very short or very tall riders). If you are seeing 7 (or 8) red dots, all in the correct place, but Velogic Studio is not producing a wireframe/skeleton, this may be the case for you.
To help us refine the rules, please submit a sample file which we will then investigate and use to tune the rules. See "Submitting a file for us to access" below.
Camera too far away?
If the camera is positioned more than around 8' from the plane of the bike, the dots may be too small for the camera to recognize.
Submitting a sample file for us to assess
If you are having issues with Marker Detection we have a simple process for submitting files for analysis.
Before you begin the process please ensure that the system has been calibrated and the bike measured (this data is saved in the file submitted and will help us troubleshoot).
When ready please click on the dropdown at the top left of the liveview:
Then click “Send a sample”
This popup will appear:
Click “Next” for the consent form. You will need to ask the rider if they consent to their data and image being used in our development process. The files will never be shared outside velogicfit.
Click “Next” to indicate what size upload you wish to provide. Note that the minimal option can sometimes mean that we can’t identify your issue. However, you will not be able to do anything else with the system while it is uploading so do not choose the full sample option if it means you will be waiting for 20mins for the upload to complete.
When you have selected a sample size, click Next and finish the wizard.
If your issue is urgent, please get in touch with us to let us know that you’ve submitted a sample, and what the problem was.
Here’s a video of the “Submit Sample” process: