Troubleshooting Pro
Inconsistent results
Why do successive recordings recommend saddle changes in opposite directions?
If both recommendations are small, within a few millimeters, that's normal variation near your target: hold, and record again. If they're far apart, treat it as a capture problem until shown otherwise. The saddle height recommendation is computed from knee angle and foot angle together at maximum knee extension (MKE). A foot that's in frame on one recording and out of frame on the next changes one of those two inputs, and the recommendation moves with it. The model estimates the position of a landmark it can't see, so an occluded or out-of-frame foot produces a plausible value rather than an error.
Record twice in succession with nothing changed. The readings typically agree within a few millimeters. More than about 10 mm apart, or an Error Recording message, points to the capture: check it and record again before you move the bike.
What does a clean capture require?
Even light with nothing bright behind the rider; clothing that contrasts with the background at the hip and foot; the camera level and square to the bike (the alignment aid in the bottom-left corner of the recording screen shows a green rectangle when it is); and the whole rider and bike in frame for the full recording. The alignment aid reports the device's tilt and rotation only. It doesn't check framing.
What if one of the recordings being compared showed an Error Recording message?
Leave it out of the comparison, correct the cause, and record again; values from that recording shouldn't be acted on. Side-view tracking problems lists the messages and their usual causes.
What if the model consistently misplaces one landmark?
Use marker override: place markers on that landmark, record, then choose ··· → Analysis → Track Markers. It's intended for recordings where lighting, clothing, or anatomy defeat markerless tracking repeatedly or for a fitter who prefers their own landmark placement (see Side-view tracking problems).
Why have saddle height recommendations stopped appearing?
Check Type of Analysis in iOS Settings → BFF Pro. Recommendations are computed at MKE and aren't produced when the Maximum Knee Extension (MKE) switch is off. Turn it on.
Why are all the distances slightly off?
Check crank length. It scales every distance the app measures; angles aren't affected. A Session linked to a bike takes its crank length from the bike and shows it read-only. Edit it on the bike (Frame Info → Crank Length). New recordings use the new length, but recordings you've already made keep their old distances until you reanalyze each one: open it then ··· → Analysis → Reanalyze.
Why did the height recommendation change after a fore/aft change?
Expected. The fore/aft result assumes the height recommendation has already been applied, and the two interact. Record again after each change (one change at a time).
Why did trying a change on screen predict one result and the real change produce another?
Trying a change on screen, including the Toe contact point used to simulate crank length, gives an estimate. Confirm every real change with a new recording.