

You'll want to check out the user guide, of course, but then you're free to install, boot it up, and start letting your computer read your face and type for you. No account needed for IBM, but youll have to sign up for AWS to use Polly. Polly has some great voices, very natural sounding. Just started attending track events in my Focus RS. The first thing, and the one that prompted an account to ask: I recorded my first outing but I am experiencing some strange behavior. Any ideas what might be happening there? Not a super big issue since it works in RaceRender. The other thing I've noticed is that my throttle indication, even if I select percentage, it doesn't accurately reflect the current throttle position. When I finally hit WOT coming out of a turn, it jumps up, but then settles back down to about 50%, even if I'm on the long straight where it's 100% floored for quite a bit.

One last thing, I'm sure this is in the documentation somewhere, but I haven't been able to dig it up yet.
#Racerender gear how to#
In TrackAddict, I can Gear+1 to accurately reflect the gear my car is in, but when in RaceRender, I can't quite figure out how to do that. When viewing the videos in TrackAddict on my phone, the OBD speed is WAY off. It has me doing 5-6mph when I'm doing 30-40, and then goes the other way as well, sometimes showing 60-70mph when I'm only doing 50.
#Racerender gear Pc#
I thought it might be because I do have one of the generic $15 OBDII adapters, however, if I export that video to my PC and watch in RaceRender, it's spot on. Any ideas what might be happening there? Not a super big issue since it works in RaceRender.This is most likely a difference between the OBD and GPS reported speeds, with one app using one and the other app using the other. GPS speeds can jump around like that if there's poor signal conditions (in which case your driving line data might look a bit rough too), and OBD speeds may do similar if there's communication or compatibility issues with the OBD-II adapter or vehicle. In TrackAddict, most everything will be based on GPS speeds, although its in-app video player can be switched to show the OBD speed instead. In RaceRender, it should default to the OBD speed (tends to be better for detecting gearing), but you can switch between the two by double-clicking on the data file in the "Input Files" list, going down to the "Vehicle Speed" selection, and choosing a specific data field. The first speed in the list will be GPS, and the second will be OBD.Īssuming the OBD-II adapter and vehicle ECU are reporting properly, this is likely the actual throttle plate position, rather than your throttle pedal input. This was simpler with the old cable throttles that were a direct relationship to your throttle pedal input, but in many modern vehicles, it can have a mind of its own. The engine computer is using your throttle pedal input to determine how much engine torque output it thinks you want, applying various other adjustments to that, and then commanding the engine controls accordingly. The best way to overcome this is to change the OBD channel selection to one of the Throttle Pedal options, assuming that your vehicle offers this. What's available for this varies widely between different cars, so that's why we don't have it selected by default.I’m not an expert, but I’ve used both a GoPro and a Virb. About the best way to get the overlay that I know of is to use the Virb software.
#Racerender gear software#
I think that even TR uses the Virb software to get the overlay, but then they use Davinci Resolve for all of the slick editing (picture in picture, cuts, replays, slo-mo, audio overlay…) they do.

used to use (and maybe still does?) Dashware to get his overlays, but I found that system to be rather cumbersome. You can view his video here, though, to see his workflow. I found that the GoPro was just kind of a slow process, and aligning the video with the track from the. Fit file was rather a pain, particularly for a crit.
