Completely custom data file format support?

Hi there - Looking at moving from an orphaned product to RR3, but my data is from a completely custom logging system that has 16 channel tyre temps, engine data, brake and TPS analog inputs, GPS speed and accelerometer data - it might also get things like ride height, pitch/roll/yaw and heartrate in the future.
I have had a quick look around and can't quite tell whether using any version of RR3, is it possible to completely define a custom format, mapping the metrics that match to RR3 supported values, and having new bespoke values able to be used by custom gauges?

This is a sample of my current file header and first couple of entries of the logfile.
Logtime,GPStime,Distance,difflaptime,LapDistance,L astLapDistance,Lap,Kph,Heading,Latitude,Longitude, Altitude,Satellites,Fixstatus,LF0,LF1,LF2,LF3,LF4, LF5,LF6,LF7,LF8,LF9,LF10,LF11,LF12,LF13,LF14,LF15, LFbrake,RF0,RF1,RF2,RF3,RF4,RF5,RF6,RF7,RF8,RF9,RF 10,RF11,RF12,RF13,RF14,RF15,RFbrake,LR0,LR1,LR2,LR 3,LR4,LR5,LR6,LR7,LR8,LR9,LR10,LR11,LR12,LR13,LR14 ,LR15,LRbrake,RR0,RR1,RR2,RR3,RR4,RR5,RR6,RR7,RR8, RR9,RR10,RR11,RR12,RR13,RR14,RR15,RRbrake,RPM,TPS, Coolant,MAP,SPKADV,AFR,BATTV,oilpressure,fuel,oilw arn,brakelight,looptime
0.51,610927398.5,0.024,0,0,0,0,0,0,-43.89835739,171.7355652,121,9,4,12.5,13.5,15.5,16, 15.5,15,15,15,14.5,15,15,14.5,15,15,15.5,15.5,0,12 .5,13.5,15.5,16,15.5,15,15,15,14.5,15,15,14.5,15,1 5,15.5,15.5,0,16.5,16.5,16.5,16.5,16.5,16.5,16.5,1 6.5,16.5,16.5,16.5,16.5,16.5,16.5,16.5,16.5,0,16.5 ,16.5,16.5,16.5,16.5,16.5,16.5,16.5,16.5,16.5,16.5 ,16.5,16.5,16.5,16.5,16.5,0,1176,0,84,34,0,121,14. 6,68,3,0,0,0
0.56,610927398.9,0.04,0,0,0,0,0,0,-43.89835739,171.7355652,0,0,3,12.5,13.5,15.5,16,15 .5,15,15,15,14.5,15,15,14.5,15,15,15.5,15.5,0,12.5 ,13.5,15.5,16,15.5,15,15,15,14.5,15,15,14.5,15,15, 15.5,15.5,0,16.5,16.5,16.5,16.5,16.5,16.5,16.5,16. 5,16.5,16.5,16.5,16.5,16.5,16.5,16.5,16.5,0,16.5,1 6.5,16.5,16.5,16.5,16.5,16.5,16.5,16.5,16.5,16.5,1 6.5,16.5,16.5,16.5,16.5,0,1180,0,84,34,0,121,14.7, 71,4,0,0,14

An example of the current generated overlay is on this video.

http://www.youtube.com/watch?v=pPGDq8zeUKs

As I say, the SW I am currently using is find, but it's not being maintained at all anymore so I am looking for a supported alternative.

Cheers - Neil G

Looks like your data is in a CSV format that should work... You would most likely need to double-click on the data file in the Input Files list, then set the "Session Time" selection to either Logtime or GPStime (I'll add automatic detection of these to our next update), but it should automatically pick up on lap, kph, heading, lat/lon/alt, rpm, tps, and brake. You could apply a data overlay template to get you started, and then add custom displays for anything else you want to see by clicking the "Add" button under the "Display Objects" section, choosing the display type you want, setting the Field selection to the desired data channel, and then using the properties box to adjust the display to your liking. Advanced and Ultimate editions will have more capability for customizing displays, but you can get a feel for much of it in even the Free edition.

Most displays will only take one channel as its input, so your 16-channel tire temps would require multiple displays, or if you're good at writing code, it could potentially be done with the scripting capability in our Enhanced Display Objects.

One of the awesome things about RaceRender is that it simply treats each column of data as a generic field. There are recommended column names, but RaceRender can usually guess which column maps to which standard field (for Tachometers/Speedometers/G's/etc). So you shouldn't have any issues with RaceRender not viewing your 64 tire temperature columns. Having a CSV file with all of your data makes everything much easier.

As you probably already know, another awesome thing about RaceRender is the ability to create custom gauges and [with programming experience] custom enhanced scripts. The temperature portions you might be able to do with simply by adding many individual bar gauges (one per temperature portion) or you could try to get fancy and create a custom gauge that reads each of the 16 corresponding fields and displays them appropriately. Recreating everything that you have exactly as you have it in your video would definitely be possible, but it would likely take quite a bit of work (especially since there isn't currently an easy way to gradient through multiple colors like blue->purple->magenta->red->orange->yellow; you could do it by drawing a gradient at each step between those two colors though). But, on the other hand, everything can be customized, so you're not beholden to that specific template. You could make everything look just like your dash, replicate your favorite racing series's graphics, or just go generic.

One note: I'm not sure how easy it is for you to switch between videos on your current software, but it would take a little getting used to on RaceRender. You could have each of your three videos overlayed on top of each other, add a timeline segment when you want to switch and then change the top level video's Active flag to Hidden. When you want to switch back, you'd need to add another timeline segment and set it back to Active.

Thanks for the detailed answers! I'm sure I could handle the coding to create the scripting for the enhanced display objects (I built the hardware and wrote all the logging/lap timing/CANbus/tyre temp stuff from scratch)...

I currently use Dashware to export a 4k overlay set of PNGs and do the multicam editing in Davinci Resolve - it has a really great option for multicam editing, plus I also need to import an audio file from a digital recorder... While I haven't yet, the next iteration of editing will include a 10-20% audio mix from whatever the active gopro is as well as the good digital audio recording. Resolve also has brilliant 1080 -> 4k upsampling which is necessary to make Youtube use a decent bitrate for POV material.

Certainly looks like RR3 will do everything I need. I have bought RR before at some stage in the past so I'll go see what version that was :-) Not averse to buying it again if I need to for V3

Cheers - Neil G

Ah, it was RR2 Deluxe in 2013!

Also, the reason for the gradient bars in the current overlay is a limitation of Dashware - I would prefer just 16 separate coloured boxes to make a static tyre temp display... A quick look at the docs linked above makes it look pretty simple.
Cheers - N