synch problem

[sickmint79]

i'm sure i have the right data and vid files, yet i can't synchronize them from a karting event i attended. i get them looking close, they get out of synch, and i make adjustments along the way, however i never get anywhere near it being actually done. it seems like these iterations have to yield a good final result, however my video keeps outpacing the data, like it is actually being played back more quickly. is this possible??

[MarkVaden]

Hi,

What format is your video in? Also which logger are you using? Is it possible to get your video and data? How big is the video file? If it is reasonably sized you can email me at mark@chasecam.com

Thanks,
Mark

[sickmint79]

the raw vid is from the pdr100. the camera got jacked and i didn't notice til later, i used avidemux to rotate the video 90 degrees though, that one is in xvid. the data logger is racechrono.com. the video files are kinda big, too big for a mailbox and a pistol to upload but they're there now.

original vid: http://mike.developer10.com/CH0N0003.MPG
demux xvid: http://mike.developer10.com/ra1.mpg
data: http://mike.developer10.com/20090531-1250-route-export.csv

[BroussalM]

Hi,

Just a way to think about your problem.

I download your .csv file and look at it into the Synchronization frame of Dashware. I see an odd thing.
Try to go to the timing 1024:58 of your datas ( not easy !)
To move your karting, with the button 0.1s by 0.1s, go to :
1024:58.2 > move
1024:58.3 no move
1024:58.4 no move
1024:58.5 > move
...
1024:59.1 > move
1024:59.2 no move
1024:59.3 > move
At that moment the karting move on only each 0.2s instead of 0.3s for the majority of the laps.

You find the same thing at :
1025:01.4 > move
1025:01.5 no move
1025:01.6 > move

And you find this in all of your laps. Nor specialy on a curve where you could stop for something, its everywhere and not at a special place.

I make an other experience.
On my video, I put a gauge with my time data ( scale 0.1s ) and your time data ( scale 0.2s ) the result is that when:

0.10.00 (my time)
2.09.601 (your time)
...
0.20.000 (my time)
2.16.600 (your time)
...
0.30.000 (my time)
2.23.601 (your time)

When the gap is 10s for me, your's is only 7s !
If you have a video lap in 60s, your .csv is on the 42s of your data.

I don't know how work Dashware for it's owne timecode, but the logic would be that it read each line for a scale of 0.1s. Your 0.2s by line could be the problem.
Anyway with the non according time code video Dashware and your datas, you can't synchronise.

I think there is something to find in that way.

Hope its help you
Regards
Michel

[MarkVaden]

Hi,

We found the problem and it is a bug in DashWare. We will be releasing a new version of DashWare within a couple of days, that will fix this bug, and others, as well as include some new features.

-Mark

[sickmint79]

interesting, what is the issue? something specific in my type of timing data that was throwing things off that people didn't run into with other data sets?

[MarkVaden]

We have some code that tries to generate an index into the csv from a time. Then we iterate the appropriate direction until we get the exact time. With most loggers we generate the correct index without iterating. With your logger we needed to iterate, but we had a bug in the iteration code that was making us return before we found the correct row. Thanks for posting the data - it was a really big help in finding the bug. We will have a new release soon with some new features, new codecs (faster and better quality), and some other bug fixes.

Thanks,
Mark