Hero 8 Black - GPS data is present in files, but apps say it isn't and won't display gauges

[kajuna]

@ricardoc8871 The signal quality depends on many factors. You can send me a Hero7 and a Hero8 file and I can compare the GPS quality for you. You can find my email at the bottom of this page: https://goprotelemetryextractor.com

If the files are too large, you can send me .LRV files that usually are next to the .MP4 files. If you don't have them, you can use the extractor to send me CSV files (Set "GPS Fix" to "Any" and "GPS Precision" to 10000) https://goprotelemetryextractor.com/free

[ricardoc8871]

@kajuna  Podes dar-me o teu email para enviar os arquivos?

[kajuna]

app@prototyping.barcelona

[kajuna]

@ricardoc8871 The GPS path of your file looks good, but the "GPS Precision" and "GPS Fix" columns report bad values some times. Filming inside the car you are not guaranteed to get good GPS data. That might be the reason Quik mobile is not showing any data. If your Hero7 recorded better quality data might just be a coincidence, but I could not test that, as the Hero7 file you sent does not contain any metadata (it's a copy, not the original)

There is also the problem of Quik desktop not being compatible with Hero8 yet, but that has beeen addressed earlier in this post.

Please follow advice from this post to get good GPS data https://community.gopro.com/t5/GoPro-Metadata-Visualization-GPS/GoPro-GPS-not-working-Performance-st...

[madmbker]

Just to add to @kajuna 's post.

I exported the GPS data from two videos of mine using https://goprotelemetryextractor.com/free as .CSV format.

I've just checked with Quik, and a video with precision of average around 870 wouldn't allow gauges in Quik. However a video that did work had precision around 126-178. I can only conclude there's some average or max precision set somewhere between 200 and 800, above which gauges won't be allowed in Quik.

You could in theory write a piece of software to modify that precision in the file to force quik to accept semi-garbage GPS lock :D. I'm sure the threshold they've chosen is reasonable, because the video that wouldn't allow gauges was visibly inaccurate (squiggly line where I was walking straight), vs the one that would allow gauges looked perfect. However it would help if the message didn't say "no gps data found" instead something like "Poor GPS lock in data not suitable for gauges".

Also shameless link to a video that had a good GPS lock and would have allowed gauges in Quik, very impressed with the quality of 2.7k 60fps Superview + hypersmooth (protune high bitrate) :D: https://www.youtube.com/watch?v=X4abqIrJT50. The video that didn't allow gauges was taken near my house with a few buildings / trees overhead.

[fireyflash16]

same here.... gopro 8 .... no gauges....  buggy software as it best

[kajuna]

@madmbker Thanks for the analysis. Tweaking the precision data to trick Quik into accepting the data is a cool idea. It would take some work as it requires modifying binary data and reattaching it to the mp4, but I'll keep the idea in mind. It could be sn addition to the Telemetry Extractor ;-)

[estwickg26066]

Video telemetry is so important to me, I'm beginning to regret buying the Hero 8. The gopro telemetry extractor lite software is so inaccurate, there's no point in using it.