Dashcam Viewer for Mac and Windows

[traveler]

I haven't received any Viofo A229 Pro videos for testing with Dashcam Viewer so I can't speak to GPS compatibility. However, it appears some folks have had luck, and others not. Not sure what's going on there, but if a Viofo A229 Pro user can send me a handful of raw "non-working" sample videos of varying length (1-5 minutes), I will add it to my ToDo list (https://wetransfer.com). In general, shorter videos tend to have less problems in DCV than longer ones so I recommend using 1-3 minute file lengths.

 

[Karagandinez]

If I try to play a video shot on firmware V1.0_231009, then Dashcam Viewer closes before starting to play the video.
If I open a video shot on firmware V1.0_231123, then Dashcam Viewer plays it without speed and coordinates.
If I open a video shot on firmware V1.1_240103, then Dashcam Viewer plays it back showing the speed and coordinates.

 

[Karagandinez]

Video shot on firmware V1.2_240227 Dashcam Viewer plays back without speed and coordinates.


Video from Mini 2 shot on firmware V1.0_231116 in the same place Dashcam Viewer plays back with speed and coordinates.

 

[TheSpanishInq]

Video shot on firmware V1.2_240227 Dashcam Viewer plays back without speed and coordinates.

Does exiftool show GPS data on that file?

 

[Karagandinez]

Does exiftool show GPS data on that file?

There is a speed stamp on the video, which means there should be GPS data too.

 

[TheSpanishInq]

I'm not sure if that's the case. The speed stamp is recorded with the video, I presume Dashcam viewer looks at metadata, embedded in the video. If there is a bug in the cam's firmware, it could very well be the stamp is updated, but the metadata isn't .

 

[traveler]

@TheSpanishInq is correct--just because there is a speed stamp on the video doesn't mean that the raw GPS data is embedded in the video. And even if there is embedded speed data, it doesn't mean that the it will match the video speed stamp. I've seen dashcams in which the embedded speed and the speed stamp are different at the same playback time, most likely because the video speed stamp data was a moving average value.

 

[Devedikeni]

I solved the problem of Dashcam Viewer Plus not being able to process GPS information in 10-minute videos with the following method.

First of all, I extracted the GPS data in the 10-minute video with the command line below.

Exiftool installed
I opened cmd.

"D:\Exiftool\A\exiftool.exe" -p "D:\Exiftool\A\gpx-fmt.txt" -ee "D:\Exiftool\A\1.MP4">"D:\Exiftool\A \1.gpx"

I copied it to a directory so that the video name and GPS name are the same.

I opened DATAKAM PLAYER and selected the relevant video file. Datakam player processed gps data.

I clicked on Datakam Player's "Export Track" menu. From the incoming menu
"GS600, Q3 (.dat)"
I chose .

I saved this file with the dat extension in the same directory, with the same name as the video name.

I opened dashcam viewer plus and selected the video file. Both the GPS information and the map of the 10-minute video worked.

 

[TheSpanishInq]

That's quite a work-around! Thanx for sharing.
Did you upload the 10-minute file to the we-transfer site of Dashcam viewer? This way they can analyse the file and maybe fix the issue so you don't have to perform all these step in the future.

 

[Karagandinez]

@TheSpanishInq is correct--just because there is a speed stamp on the video doesn't mean that the raw GPS data is embedded in the video. And even if there is embedded speed data, it doesn't mean that the it will match the video speed stamp. I've seen dashcams in which the embedded speed and the speed stamp are different at the same playback time, most likely because the video speed stamp data was a moving average value.

I have given you a link to this video file.
You can download it and see what is in it and what is not.

 

[Devedikeni]

That's quite a work-around! Thanx for sharing.
Did you upload the 10-minute file to the we-transfer site of Dashcam viewer? This way they can analyse the file and maybe fix the issue so you don't have to perform all these step in the future.

They haven't gotten back to me yet. I'm waiting for an answer to my message. When they answer my message, I will share it with you.

 

[traveler]

They haven't gotten back to me yet. I'm waiting for an answer to my message. When they answer my message, I will share it with you.

@Devedikeni please resend me a new WeTransfer link to your 10minute video. I must have missed it. Thanks!

 

[traveler]

I have given you a link to this video file.
You can download it and see what is in it and what is not.

@Karagandinez thank you for the A229 (f/w V1.2_240227) front camera sample videos. I loaded these into Dashcam Viewer 3.9.7 and the GPS data was recognized. See screenshot below.

If you're still having trouble viewing the GPS data, please try the following:.

1. Try clearing the cache (under Advanced Preferences). Then reload your videos.
2. Try a hard reset as described here.

John

 

[Karagandinez]

If you're still having trouble viewing the GPS data, please try the following:.

1. Try clearing the cache (under Advanced Preferences). Then reload your videos.
2. Try a hard reset as described here.

I'll try to do this later.

But why when I upload a video shot on firmware: V1.1_240103 Dashcam Viewer 3.9.7 works without problems?
I didn’t do anything with Dashcam Viewer 3.9.7... I didn’t clear the cache or reset it.

 

[Karagandinez]

I'll try to do this later.

But why when I upload a video shot on firmware: V1.1_240103 Dashcam Viewer 3.9.7 works without problems?
I didn’t do anything with Dashcam Viewer 3.9.7... I didn’t clear the cache or reset it.

View attachment 72223

After the video from A229 Pro on firmware V1.1_240103, I took the video file from VS1 and Dashcam Viewer 3.9.7 played it with the route.

 

[Devedikeni]

@Devedikeni please resend me a new WeTransfer link to your 10minute video. I must have missed it. Thanks!

I sent a new video to the e-mail address support@dashcamviewer.com, the sharing link is below.

Thanks

The sharing link is valid for 21 days.

https://lifeboxtransfer.com/s/22b1e1eb-1f29-4085-83a2-554aec8129ad

 

[PedroN]

I have a little question:
I have the newest Dashcam Viewer Plus 3.9.7 (registered). I try to play the files from my Viofo A119 V3 but I can't see any GPS data (time, speed and map). Are the A119 V3 files not compatible with the Dashcamviewer?
I tried searching the forum but I can't see the forest because of all the trees

 

[TheSpanishInq]

According to the hardware compatibility list (HCL) on the home page of dashcamviewer it should be compatible (not many trees there... )

• Viofo A119, A119S, A119G V3 (TS format)

Which @Kremmen seems to confirm

FYI: Just tested my footage from A119V3 under 3.9.7 and the map is fine

Does exiftool show GPS data in the video files?

Looks like the 1m samples I have from my A229 Pro can be processed with ExifTool.
exiftool -ee <filename> will show the GPS data, if available.

 

[PedroN]

It's a bit hit and miss, the data is in the files but most of the times the map reports "Sorry we have no imagery here" if I then zoom out the map shows the red dot in the Gulf of Guinea (right under Ghana). Believe me I'm still in the Netherlands as far as I know.

Edit: I found the problem I think. It seems that the filenames are giving the problems, the filenames were e.g.: 20240515141018_000046.MP4, thus YYYYMMDDHHMMSS_######.MP4.
I renamed al files in Totalcommander as 01.mp4, 02.mp4 etc. Now ALL files will show the data in Dashcam Viewer.

So my suggestions is the the long filenames are giving the problems (?)

I attach some screenshots:

 

[TheSpanishInq]

So my suggestions is the the long filenames are giving the problems (?)

That would be odd, as the video content IS shown. You'd expect a 'File not found error' or 'Filename too long'.
Are the files stored in a path with a very long name?

In the old days the total length, i.e. the full path name of a file, including folders, should not exceed 260 characters. C:\something\etc\very long or very much paths\filename.mp4
But current versions of Windows shouldn't have that limit anymore, if you modify the Windows registry:

Maximum Path Length Limitation - Win32 apps

Maximum path length limitation.

learn.microsoft.com

If you're not comfortable with that, try to move the files to a folder with a shorter name, e.g. C:\temp\videos.

Unless of course the path length isn't the problem, then it could be a bug in Dashcam Viewer...

Note: Dashcam Viewer is 64-bit application. I assumed these wouldn't have this limit, but I'm not so sure now...

Edit: in de Dashcam Viewer FAQ there is an issue mentioned with de A119. Do you have the latest firmware installed?

Dashcam Viewer | FAQ

Have any questions about Dashcam Viewer? Visit our FAQ page where we list answers to our customers top questions.

dashcamviewer.com