Dashware & RaceStudio2 (AiM SoloDL) weirdness

[mid-corner fun]

Are you guys having any luck syncing SoloDL data into Dashware?

I'm finding that Dashware's calculated lap times are at least 1-2 seconds slower than what RaceStudio reports (I believe RaceStudio, it's in line with my usual lap times collected previously via trackmaster) and after a few laps the video/data sync goes to hell even though it looks good on lap 1.

I know there are alternatives out there but I've spent too much time tweaking the Aim data profile and making templates to look elsewhere.

[yandy]

Originally Posted by mid-corner fun

Are you guys having any luck syncing SoloDL data into Dashware?

I'm finding that Dashware's calculated lap times are at least 1-2 seconds slower than what RaceStudio reports (I believe RaceStudio, it's in line with my usual lap times collected previously via trackmaster) and after a few laps the video/data sync goes to hell even though it looks good on lap 1.

I know there are alternatives out there but I've spent too much time tweaking the Aim data profile and making templates to look elsewhere.

I don't have this problem, except that Aim gives an laptime of x:yy:zzz and Dashware likes to round down on the last part, so a 1:45:313 will be 1:45:24 for some reason, but the video is always in sync.

I can send you my Dashware profile if you'd like to try that. Let me know.

Recent videos on my youtube channel in signature if you want to confirm.

Thanks

[mid-corner fun]

Originally Posted by yandy

I don't have this problem, except that Aim gives an laptime of x:yy:zzz and Dashware likes to round down on the last part, so a 1:45:313 will be 1:45:24 for some reason, but the video is always in sync.

I can send you my Dashware profile if you'd like to try that. Let me know.

Recent videos on my youtube channel in signature if you want to confirm.

Thanks

thanks, you got pm. I may have a potential solution though, found this post on what appears to be the same issue, I'll try syncing on the 2nd lap tonight:

Originally Posted by radiantm3

There's some sort of pause or glitch between the first and second lap of data. If you sync them up on the first lap, they'll be messed up after that lap (when the timer starts actually counting). So I just sync at the first corner of the 2nd lap (first timed lap). Should be good from there on.

[yandy]

Originally Posted by mid-corner fun

thanks, you got pm. I may have a potential solution though, found this post on what appears to be the same issue, I'll try syncing on the 2nd lap tonight:

I'll email you the profile later, but yes, I probably should've mentioned, I never sync the first lap anyways, since that's usually coming out of the pits and such. i always sync from the start/stop line of the second lap.

[yandy]

by the way, there seems to be a new version that "may" fix some issues as well... 1.4.2

DashWare 1.4.2:
Added the ability to trim data from the start and/or end, similar to the video trimming.
Improved TCX/GPX file import for cyclists.
TCX parser deals with lack of distance and speed better.
GPX parser deals with more extension formats, including reading cadence.
GPX parser now also supports Trail Tech Voyager extensions.
ChaseCam gave us another fix for ChaseCam data extraction problems.
Improved AiM data support to use beacon times to maintain a perfectly accurate data sync.
Updated Starlane data profile to also handle ; as separator.

[mid-corner fun]

Originally Posted by yandy

I'll email you the profile later, but yes, I probably should've mentioned, I never sync the first lap anyways, since that's usually coming out of the pits and such. i always sync from the start/stop line of the second lap.

Yup, that seems to be it, syncing on 1st lap seems to screw things up. I setup my own track & start line via GPSManager that triggers on T1 right after pit-out, I guess that didn't work out that well under this scenario.

I'm now down to ~0.2-0.3 discrepancy like you mentioned, will try the new version tonight.