Results 1 to 2 of 2

Thread: Racerender3 lost sync to video after GPS lost satellite for several seconds

  1. #1
    Potential Tuner
    Join Date
    Apr 2015
    Posts
    3

    Exclamation Racerender3 lost sync to video after GPS lost satellite for several seconds

    Racerender3 lost sync to video after GPS lost satellite for several seconds and always lag to the video thereafter. When the GPS lost satellite, the red dot on track map stopped suddenly. After the GPS fixed again, the red dot still lag to video and don't catch up to current GPS position.

    How to solve this problem?

    Update: After removed the Lap Timer data in the csv file, it works as normal. The track vs Lap Timer data is not a loop. Is there any trick to record the track map if there is Precise Lap Timers & Separate Lap Info?
    Last edited by zowietek; 04-22-2015 at 10:52 PM.

  2. #2
    HPT Employee Weston@HPTuners's Avatar
    Join Date
    Jul 2014
    Location
    39.735034, -103.894459
    Posts
    868
    If I'm understanding correctly, it sounds like RaceRender is using the lap time data column in the CSV file as the basis for the session's timing, but your session had a GPS problem that caused that to cut out, and then the remaining data timing was skewed as a result.

    The first thing to do here would be to see if there is another timing column in the file that RaceRender can use... If you double-click on the data file in the Input Files list, you can then make a specific selection for "Session Time" and possibly resolve the issue that way. What's available and how well that works will depend on which specific data system you are using, as I've seen time data presented in many wildly different ways.

    If there is no other suitable timing information in the file, then that's a more complicated situation with more complicated solutions... Presumably, it has correct data before the GPS problem, and then there's correct data after the problem but it needs some time adjustment in the middle. In that case you could try the following:

    1) Use the Duplicate feature to make two instances of the data input
    2) Time the first one to be in correct sync before the GPS problem, and trim its end to stop at the time of the problem
    3) Trim the start of the second one so that it only covers the time span after the GPS problem
    4) Use the Join button to make them act as a single combined input
    5) Add a Time Filler in the middle of them to adjust its length to effectively get the second part in proper sync