Data File Length Appears Too Long or Too Short

Helpful tips, solutions, and how-to's
Forum rules
This is a read-only section, consisting of information provided or approved by RaceRender LLC

Data File Length Appears Too Long or Too Short

Postby RaceRender LLC » Thu Aug 22, 2013 12:48 pm

Different dataloggers use a variety of different time formats in the files they export for use with RaceRender. Occasionally, the method in use wont be clear to RaceRender, and it will be interpreted using a different method, which can cause the data file's length to appear too long or too short, as well as prevent correct synchronization with video or other data. The most common cases, and their solutions, are listed below:

1) If RaceRender shows a data file length that is excessively longer than actual, this is often a simple case of the data file's timing being reported in milliseconds, while RaceRender is interpreting it as seconds. It will attempt to detect and adjust for these situations automatically, but some cases can still lead to errors, especially for shorter sessions. That can be resolved if you double-click on the data file under RaceRender's "Input Files" list, go to the "Session Time" selection and choose the "Time" field, and then enter "1000" in the "Time Units Per Second" box on the right. This will force the file's timing to be treated as milliseconds. If the data file's timing is instead in centiseconds (1/100 of a second), you would enter "100" in this box. If it's in deciseconds (1/10 of a second), you would enter "10". Example Screenshot for Milliseconds

2) If RaceRender shows a data file length that is excessively shorter than actual, then the file's timing could be using a larger unit of measure than what RaceRender is interpreting it as. If that's the case, please follow the steps listed in item #1 above, but instead try entering "1" in the "Time Units Per Second" box to force the file's timing to be interpreted as seconds.

3) If RaceRender shows a data file length that is moderately longer than actual, this might be a case of the file's timestamp data being reported in "hhmmss.nnn" format, but being unclear to RaceRender, so it is instead being interpreted as seconds. That would result in the file length being expanded by a 40 second gap once per minute, and a 40 minute gap once per hour. If that's the case, please e-mail a sample of the file to Info@RaceRender.com, and this can usually be resolved with a minor update to RaceRender to recognize that file format's unique situation.

4) If RaceRender shows a data file length that seems to be near the correct length, but plays at a slightly different rate than videos or other data, please see this Knowledge Base article: viewtopic.php?f=6&t=17

5) For other cases, or ones which aren't solved by the above guidance, please e-mail a sample of the file to Info@RaceRender.com, so that the cause can be investigated further and possibly resolved.
RaceRender LLC
by HP Tuners
RaceRender LLC
Site Admin
 
Posts: 313
Joined: Sun May 13, 2012 10:39 pm

Return to Knowledge Base - RaceRender



cron