So, I've had the K2 installed on my bike a few weeks now. I've got a significant issue with missing recording times that I've created a separate post for. Here are a few strange things that I've seen that I'd like to see if anyone has suggestions for.
1. Front/Rear video timing differences.
So, when i watch my videos back in Dashcam Viewer I've noticed that sometimes the rear video isn't shown and have worked out that this is because the front and rear camera file names need to be the same (except for the F/R). My video sometimes (not always but enough for it to be annoying) don't have this - meaning I have to manually rename the files to get them to show (top left circle - the other one was pointing out that my loop times are all over the place):
Question 1 - Is this a bug that needs fixing or is it something that I can rectify?
2. GPS all over the place
So, I like a good bit of GPX file-age. I really like visualising the ride in Dashcam Viewer on the map. The problem is I get these weird lines on the map which suggests drop outs in the GPS signal (or something). I've got my GPS receiver in full sight of the sky. Here's how it displays:
You can make out the track but that isn't workable.
Question 2 - what is wrong with the embedded GPS information in the MP4 for it to display like that?
3. Embedded speed information is slightly out.
So, I like having the speed embedded in the video file but it's always slightly off. Here's the bike when it's just come to a stop:
The GPS information in the MP4 is spot on and accurate but the embedded video isn't. Again, it might only be a second or so but wrong is wrong.
Question 3 - Is this a bug in the writing of the GPS information to the video file that Innovv need to fix, or is it something that I can rectify myself?
Thanks for your hep. If I should have created three topics for this then apologies and I will do.
Tracking this thread as I have the first issue as well.
Hi Mike
1. Front/Rear video timing differences.
I get the same in the old V0.57, which I still use because I like the index in the file names. Sometimes the names differ by one second like yours.
I think this happens because the process, which creates the files, gets the current time for each file individually. Instead of getting the time only once and then use this time for both files.
I think they do something like this...
CreateFile (<CurrentDate_and_Time>+"_"F) CreateFile (<CurrentDate_and_Time>+"_"R)Instead of this...
Set Filename = <CurrentDate_and_Time> CreateFile (Filename+"_F") CreateFile (Filename+"_R")So it can happen that the F-Video gets a different filename than the R-Video.
Not really a bug, but a little bit inelegant.
2. GPS all over the place
I tested this and I don't see those lines. Neither in Dashcamviewer nor in Google Earth when importing the GPS data as gpx or kml. The points where the K2 lost and regained GPS receiption are directly connected by a straight line.
But my videos are from V0.57. Maybe the V.070 does something different here.
The effect you have looks like the GPS coordinates resets to 0 when the GPS looses receiption.
Could you send me a example video, so I can check it?
I've got my GPS receiver in full sight of the sky.The GPS receiver of the K2 is not comparable to the receivers used in navigation units like Garmin or TomTom. They are of better quality (better antenna, more channels), as they are essential parts for the unit to work. For the K2, the GPS receiver is more a "nice to have". So even with free view to the sky, you will get (short) outages.
I think it is a question of costs. You can buy gps receiver modules for 6€, but also for 90€.
3. Embedded speed information is slightly out.
To my experience this happens when the K2 looses GPS receiption. In the video, the speed freezes to the last value, but in the GPS information it records 0.
Here the speed freezes at 120 km/h, but GPS shows 0 km/h. Obviously, I am not parking at the autobahn at this moment :-) Beside that, I did not see any differences between video speed and gps speed. But I must admin, that I use the Dashcam Viewer very rarely.
Hi Frostie, many thanks for taking the time to help.
1. Inelegant, you're right.
2.
To find a clip with the lines I've zoomed in and realised that, linked to my other post that you've also kindly responded to https://www.innovv.com/forum/innovv-k2/missing-recordings , the outage is in the 8-10 second gap in recording:
The video nor the extracted .gpx file will upload but here's the offending part of the extracted gpx file:
<trkpt lat="54.0338364" lon="-0.3008245">
<ele>0.0</ele>
<time>2020-09-12T14:03:37Z</time>
<speed>24.3</speed>
</trkpt>
<trkpt lat="54.0340347" lon="-0.3009918">
<ele>0.0</ele>
<time>2020-09-12T14:03:38Z</time>
<speed>23.7</speed>
</trkpt>
<trkpt lat="0.9005672" lon="0.0050165">
<ele>0.0</ele>
<time>2020-09-12T14:03:38Z</time>
<speed>44.0</speed>
</trkpt>
</trkseg>
</trk>
</gpx>
Hopefully this issue will go away with the new card I've put in.
Also, maybe I'd be better off recording in TS format, concatenating all the files together and using the separate GPX file I generate using my Samsung A9 (never lets me down) for the whole ride? Is it possible to precisely align the GPS and video files in Dashcam Viewer?
3. For me it's all the time (note in the picture above - still 2mph out). Maybe I should try v0.57 of the firmware and then I can check like for like with your experience. I presume there's a modified bitrate version in your filestore?
Hi Mike
<trkpt lat="0.9005672" lon="0.0050165"> <ele>0.0</ele> <time>2020-09-12T14:03:38Z</time> <speed>44.0</speed> </trkpt>Yeah. That's 0,0. Right in the Gulf of Guinea. I know this position from my hobby some years ago (building and flying drones). They sometimes switched to this position, too, which had funny site effects.
Maybe this switch to 0,0 is why you K2 calculates a speed of 158 km/h at that moment. From 85 km/h to 158 km/h within the blink of an eye. That's a decent acceleration :-)
The GPX file of my video in the moment where the speed freezes looks like this
<trkpt lat="51.3624763" lon="7.0632753"> <ele>0.0</ele> <time>2020-09-06T15:45:02Z</time> <speed>33.6</speed> </trkpt> <trkpt lat="51.3624763" lon="7.0632753"> <ele>0.0</ele> <time>2020-09-06T15:45:03Z</time> <speed>0.0</speed> </trkpt> <trkpt lat="51.3624763" lon="7.0632753"> <ele>0.0</ele> <time>2020-09-06T15:45:04Z</time> <speed>0.0</speed> </trkpt>It also freezed the coordinates and therefore calculates a speed of 0.
That the video keeps the last speed is something I already complained some month ago.
I did only check the gpx of this video to see what coordinates the K2 records when it looses GPS. So it may be that, in some videos, it switched to 0,0 like yours, too.
Checking more videos with Dashcamviewer is a little bit laborious for me, as I use Linux and there are only Windows and MacOS Versions. So I have to run it in a virtual machine, where it runs really clumsy.
Is it possible to precisely align the GPS and video files in Dashcam Viewer?I don't know. I never played around with Dashcamviewer, because of the things mentioned above.
Maybe I should try v0.57 of the firmware and then I can check like for like with your experience. I presume there's a modified bitrate version in your filestore?Of course there is a modified V0.57 version ;-)
Thanks. I'll try the new card, a few more rides with different settings/firmware and report back in a week or so.