Re: Video overlay delay
Posted: Fri Sep 13, 2013 3:31 pm
So data is behind - which means you need to increase(!) the sensor delays.
As I assume you have tried all kinds of changes already, I really suggest to start from the beginning. The picture below shows the standard delays for all sensors including video (it is iOS7 already and slightly differs to your view). Please start from here and always change only one value at a time. Try the defaults first. In case both OBD *and* acceleration are behind compared to the video, decrease the Overlay Synchronization for Video (0.5 to 1.0 at a time) and try the overlay again. In case OBD *or* acceleration is behind, increase the respective channel's delay (again, small steps, one at a time). As sensor delays are taken into account while recording, you need to record a new lap to test that.
Delays are the time gap between the real world event (e.g. a certain speed is achieved), and the time this information is processed / stored in LapTimer. It is a frequent error to change values the wrong direction. There are several approaches you to get the clue, I always try it like this: "oh, the speed is behind... it seems my assumption on the time passing between event and arrival is still to optimistic - because it is late... so I need to make it more pessimistic - which is increasing it".
- Harry
As I assume you have tried all kinds of changes already, I really suggest to start from the beginning. The picture below shows the standard delays for all sensors including video (it is iOS7 already and slightly differs to your view). Please start from here and always change only one value at a time. Try the defaults first. In case both OBD *and* acceleration are behind compared to the video, decrease the Overlay Synchronization for Video (0.5 to 1.0 at a time) and try the overlay again. In case OBD *or* acceleration is behind, increase the respective channel's delay (again, small steps, one at a time). As sensor delays are taken into account while recording, you need to record a new lap to test that.
Delays are the time gap between the real world event (e.g. a certain speed is achieved), and the time this information is processed / stored in LapTimer. It is a frequent error to change values the wrong direction. There are several approaches you to get the clue, I always try it like this: "oh, the speed is behind... it seems my assumption on the time passing between event and arrival is still to optimistic - because it is late... so I need to make it more pessimistic - which is increasing it".
- Harry