Unfortunately, due to business restriction not much time for flights. Proud owner of a Q500 4k for the last one year. I am really happy i found copilots to my hobby. 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.This is Lawrence from Piraeus, Greece and i am a newbie.
#Racerender mp4#
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). GL020101.LRV -> GL020101_LRV.MP4 although RaceRender seems to work fine without having to rename.
You can copy these off the SD Card, or write your own script using the GoPro Camera API, and just rename them with. 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. The ".LRV" (Live Preview) files written by the GoPro camera contain the GPS data. I know this is an old thread, but thought this may be of interest for anyone having issues with GoPro 11. Telemetry Extractor ( ) 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 ( ). 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. Others have had success sticking with the old firmware: It seems like the latest updates (especially related to the Hero 10) updated the GPS rate like you mentioned.
#Racerender update#
UPD: G-force indicator in lower-right demonstrates the issue perfectly - compare Hero 9 and Hero 11 videosIt 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. GoPro Hero 9 Black - position marker runs smooth. GoPro Hero 11 black - attention on position marker (Boost sample rate disabled) (Boost sample rate enabled) So, the naughty effect is that position marker hitches. 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. It appeared now they add NMEA log to LRV file only unless you use and normal bitrate setup (switch to high - no log in MP4) My Hero 9 black just sunk, so had to switch to Hero 11 Black. 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.
That allows me to perform my conversion to H.264 as part of my processing prior to RaceRender. 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):
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'm glad you're able to extract the telemetry data externally since others have had issues with that. 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. 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. 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.
0 kommentar(er)
