Issues with GoPro 11 videos and RaceRender

[Howitzer214]

I'm having 2 issues GoPro11 videos with RaceRender.

First, when I add the video file to RaceRender, it does not prompt me that it found telemetry data. I know the data is there as I can extract it separately outside of RaceRender. I'd like to not have to do multiple steps if possible though.

Also during preview for editing/clipping, the video is insanely choppy/laggy and I really can't even use it because it's so slow. The program itself is what goes unresponsive. My resources are not the issue as CPU, memory and disk usage all stay very low during this.

The GoPro videos are HEVC/h.265 - I have HEVC codecs installed and the videos themselves play perfectly on their own. If I convert the video to h.264 and add that to racerender, the preview functions great and I'm able to seek through the video.

The GoPro videos themselves are 4k/120fps and I've tried with sizes from 3-10GB.

Any help/tips appreciated, thanks.

[HoboBob]

Unfortunately, I think you've already taken the best steps that you can to mitigate your issues without an update to RaceRender directly from HPtuners. Those of us on the forums have been asking for a number of features particularly related to performance; and better H.265 support and telemetry extraction (particularly with regard to data validation) would fit right in with those requests. If you have the data, I can definitely help with custom gauges/display objects, but updates to the program itself require someone from HPtuners to implement...

I'm glad you're able to extract the telemetry data externally since others have had issues with that. And I have also found that converting to H.264 has been the best way to handle dealing with the videos in RaceRender itself even though some people have had success with the HEVC Video Extensions. I've personally found that HyperSmooth is very disorienting in a quick transition motorsports setting such as autocross; so I run my H.265 videos through Davinci Resolve to stabilize the video relative to the car (except using the auto-zoom functionality instead of doing it manually):


That allows me to perform my conversion to H.264 as part of my processing prior to RaceRender. That would also strip out any telemetry, but I record that through a separate app (like TrackAddict or RaceChrono) so that I can get OBD2 data from the car in addition to a nicer GPS that doesn't have as many issues as the GoPros tend to have.

[[CpD]bob]

My Hero 9 black just sunk, so had to switch to Hero 11 Black.

GoPro shitmakers keep the traditions:
It appeared now they add NMEA log to LRV file only unless you use 1080p@60 and normal bitrate setup (switch to high - no log in MP4)
GPS lag is like 1.2s
Looks like they switched GPS refresh rate from 18Hz to 10Hz, and RaceRender forces wrong refresh rate, even if I disable "Boost sample rate" checkbox in data setting.
So, the naughty effect is that position marker hitches.
GoPro Hero 11 black - attention on position marker (Boost sample rate disabled) https://www.youtube.com/watch?v=-kZBe4-2Jrs (Boost sample rate enabled) https://www.youtube.com/watch?v=wc6Uq4hrJYU
GoPro Hero 9 Black - https://www.youtube.com/watch?v=pirr_wUEerU - position marker runs smooth.

RaceRender 3.7.3

Any ideas how to deal with it?


UPD: G-force indicator in lower-right demonstrates the issue perfectly - compare Hero 9 and Hero 11 videos

[HoboBob]

My Hero 9 black just sunk, so had to switch to Hero 11 Black.

GoPro shitmakers keep the traditions:
It appeared now they add NMEA log to LRV file only unless you use 1080p@60 and normal bitrate setup (switch to high - no log in MP4)
GPS lag is like 1.2s
Looks like they switched GPS refresh rate from 18Hz to 10Hz, and RaceRender forces wrong refresh rate, even if I disable "Boost sample rate" checkbox in data setting.
So, the naughty effect is that position marker hitches.
GoPro Hero 11 black - attention on position marker (Boost sample rate disabled) https://www.youtube.com/watch?v=-kZBe4-2Jrs (Boost sample rate enabled) https://www.youtube.com/watch?v=wc6Uq4hrJYU
GoPro Hero 9 Black - https://www.youtube.com/watch?v=pirr_wUEerU - position marker runs smooth.

RaceRender 3.7.3

Any ideas how to deal with it?


UPD: G-force indicator in lower-right demonstrates the issue perfectly - compare Hero 9 and Hero 11 videos

It seems like RaceRender could really use an update to handle the new refresh rate for GoPros...but there are ways to handle it outside of RaceRender.

It seems like the latest updates (especially related to the Hero 10) updated the GPS rate like you mentioned. Others have had success sticking with the old firmware:
https://forum.hptuners.com/showthrea...-latest-update
https://goprotelemetryextractor.com/...on-the-hero-10

I've typically found it better to get my data from an app like TrackAddict instead of relying on GoPro extraction, but others have found ways to do it outside of RaceRender. Telemetry Extractor (https://goprotelemetryextractor.com/free) might be a way to get that data without needing to setup a bunch of command line extraction tools, but it can be done without spending money if you're familiar with the setup (https://www.reddit.com/r/gopro/comme...mment/htb6f5l/).

[[CpD]bob]

I see.

I had to buy Hero 11 and it required update from the start (downloaded 2.01), and, according to the thread you linked, it is 10Hz as same issue is described.
And looks like there is no any setting in RaceRender to deal with it still, right?

My version is 3.7.3 - use it for a long time and can see no updates in download section. Looks like the app is abandoned.

[[CpD]bob]

Got you workaround

Step 1 - open video file, racerender adds data source
Step 2 - right click on data source - export data - csv
Step 3 - new project again, select video, select exported csv file as data source.

After that everything works as it worked before - position marker is fine, G-meter is fine.
But it adds another annoying step, and can be easily fixed inside RaceRender itself.

[[CpD]bob]

So, for race render - no updates planned?

[sportbikehawk]

I know this is an old thread, but thought this may be of interest for anyone having issues with GoPro 11.

The ".LRV" (Live Preview) files written by the GoPro camera contain the GPS data. They are lower resolution than the mp4 file so are tiny in comparison, so I use these for quick transfer and analysis at the track between sessions. You can copy these off the SD Card, or write your own script using the GoPro Camera API, and just rename them with .mp4 as the file extension, e.g. GL020101.LRV -> GL020101_LRV.MP4 although RaceRender seems to work fine without having to rename.

I've only recently starting using this technique, so I don't know if the LRV files contain the same amount of telemetry data as the MP4 files, but so far I haven't noticed any differences for the channels I'm using (time, speed, position, acceleration, lean angle) and as noted above, perhaps now it is only the LRV file that contains the telemetry data (probably due to the data transfer requirements of the 5K video).

Having the data in the LRV file means an extra step to render a high-resolution video, but for some use cases it actually works better having it in a separate file, and easier to manage with the smaller file size.