Harry wrote:My plan is as follows:
Users can start video recording manually. When LapTimer triggers, video recording is started latest. Afterwards LapTimer records video continuously - as long as at least double the space of the video is available on the device. Every time a lap is timed, both start and end point are stored in sync with the video. This start and end point can be used later to synchronize the overlay. Video recording is stopped either by he user, or when the video view is closed, or when the minimum space requirements are not met anymore. The video is transferred to the photo library. During overlay creation, the user can select the time to be displayed ahead of start (if available) and past finish (if available).
Sounds reasonable? Bad news is, this is scheduled for v15.![]()
- Harry
Hi Harry
So are you saying we can start video recording manually, so say when in the pits just before setting out onto track. The lap times will still be recorded when passed start/finish or ref points on the loaded track etc. but it shall be just one long continous video which only stops when the users selects so or space runs out.
I think this is what you are saying yes?
For me the most important criteria is:-
1. Manual recording, so I can basically record my entire session which could be 10 minutes or 30 minutes depending how long I spend out on track, so a manual start/stop is crucial.
2. Been able to overlay GPS, G-Force and OBD data onto my recorded videos.
3. Yes its a nice bonus to have the software note lap times and load the track and show the cars GPS location on track etc, but its not crucial, I am more interested in being able to record my track days by having good quality video with the OBD data overlayed, anything else is just a bonus.

If so sounds good to me, whats the ETA for v15?