RaceCapture RaceRender Guide - Revision history

Sbarton: /* Known Issues */

2019-06-13T18:50:24Z

Known Issues

← Older revision		Revision as of 18:50, 13 June 2019
Line 109:		Line 109:
	* If you find RaceRender performing terribly slow you may be affected by a timing issue in your RaceCapture log. Rarely, usually right in the beginning of a log if it happens, you can have timestamps that are.. out of order. Events that seem to go back in time. RaceRender expects all the timestamps to go in chronological order and when they don't it has a hard time processing the data. The fix is pretty easy. Open the logs and visually inspect the first page's worth of values in the "Utc" column. These values will be really large numbers as they are time in Unix epoch time, but they should normally go up in value (the value is the number of seconds since I believe a date in the 70s, I forget and I'm a Unix professional :D). If you see any going out of order, you can re-order them or simply delete the entire lines since a handful of data lines won't affect your video rendering results much. Alternatively you can use the GEMS conversion script I wrote found in the Autosport Labs Forums here: https://forum.autosportlabs.com/viewtopic.php?t=3731. Just use the initial perl script conversion and use that output file as your input for RaceRender. This works because that script makes sure to re-order any out of order timestamped log entries. This isn't the first suggestion because using the script takes a bit of technical know-how with setting up a Windows Unix environment and getting packages like Perl.		* If you find RaceRender performing terribly slow you may be affected by a timing issue in your RaceCapture log. Rarely, usually right in the beginning of a log if it happens, you can have timestamps that are.. out of order. Events that seem to go back in time. RaceRender expects all the timestamps to go in chronological order and when they don't it has a hard time processing the data. The fix is pretty easy. Open the logs and visually inspect the first page's worth of values in the "Utc" column. These values will be really large numbers as they are time in Unix epoch time, but they should normally go up in value (the value is the number of seconds since I believe a date in the 70s, I forget and I'm a Unix professional :D). If you see any going out of order, you can re-order them or simply delete the entire lines since a handful of data lines won't affect your video rendering results much. Alternatively you can use the GEMS conversion script I wrote found in the Autosport Labs Forums here: https://forum.autosportlabs.com/viewtopic.php?t=3731. Just use the initial perl script conversion and use that output file as your input for RaceRender. This works because that script makes sure to re-order any out of order timestamped log entries. This isn't the first suggestion because using the script takes a bit of technical know-how with setting up a Windows Unix environment and getting packages like Perl.

	If you need to clean up the headings on your log file and remove any rows that do not have latitude or longitude, you can upload your log file [http://www.mytrackschedule.com/RCLogs/ here].		*If you need to clean up the headings on your log file and remove any rows that do not have latitude or longitude, you can upload your log file [http://www.mytrackschedule.com/RCLogs/ here].


	--[[User:Jpf11\|Jpf11]] ([[User talk:Jpf11\|talk]]) 00:12, 23 June 2017 (UTC)		--[[User:Jpf11\|Jpf11]] ([[User talk:Jpf11\|talk]]) 00:12, 23 June 2017 (UTC)

Sbarton: /* Known Issues */

2019-06-13T18:50:11Z

Known Issues

← Older revision		Revision as of 18:50, 13 June 2019
Line 108:		Line 108:
	=== Known Issues ===		=== Known Issues ===
	* If you find RaceRender performing terribly slow you may be affected by a timing issue in your RaceCapture log. Rarely, usually right in the beginning of a log if it happens, you can have timestamps that are.. out of order. Events that seem to go back in time. RaceRender expects all the timestamps to go in chronological order and when they don't it has a hard time processing the data. The fix is pretty easy. Open the logs and visually inspect the first page's worth of values in the "Utc" column. These values will be really large numbers as they are time in Unix epoch time, but they should normally go up in value (the value is the number of seconds since I believe a date in the 70s, I forget and I'm a Unix professional :D). If you see any going out of order, you can re-order them or simply delete the entire lines since a handful of data lines won't affect your video rendering results much. Alternatively you can use the GEMS conversion script I wrote found in the Autosport Labs Forums here: https://forum.autosportlabs.com/viewtopic.php?t=3731. Just use the initial perl script conversion and use that output file as your input for RaceRender. This works because that script makes sure to re-order any out of order timestamped log entries. This isn't the first suggestion because using the script takes a bit of technical know-how with setting up a Windows Unix environment and getting packages like Perl.		* If you find RaceRender performing terribly slow you may be affected by a timing issue in your RaceCapture log. Rarely, usually right in the beginning of a log if it happens, you can have timestamps that are.. out of order. Events that seem to go back in time. RaceRender expects all the timestamps to go in chronological order and when they don't it has a hard time processing the data. The fix is pretty easy. Open the logs and visually inspect the first page's worth of values in the "Utc" column. These values will be really large numbers as they are time in Unix epoch time, but they should normally go up in value (the value is the number of seconds since I believe a date in the 70s, I forget and I'm a Unix professional :D). If you see any going out of order, you can re-order them or simply delete the entire lines since a handful of data lines won't affect your video rendering results much. Alternatively you can use the GEMS conversion script I wrote found in the Autosport Labs Forums here: https://forum.autosportlabs.com/viewtopic.php?t=3731. Just use the initial perl script conversion and use that output file as your input for RaceRender. This works because that script makes sure to re-order any out of order timestamped log entries. This isn't the first suggestion because using the script takes a bit of technical know-how with setting up a Windows Unix environment and getting packages like Perl.

			If you need to clean up the headings on your log file and remove any rows that do not have latitude or longitude, you can upload your log file [http://www.mytrackschedule.com/RCLogs/ here].


	--[[User:Jpf11\|Jpf11]] ([[User talk:Jpf11\|talk]]) 00:12, 23 June 2017 (UTC)		--[[User:Jpf11\|Jpf11]] ([[User talk:Jpf11\|talk]]) 00:12, 23 June 2017 (UTC)

Jpf11: /* Guide to getting your RaceCapture data into your video with RaceRender */

2018-02-27T18:08:56Z

Guide to getting your RaceCapture data into your video with RaceRender

← Older revision		Revision as of 18:08, 27 February 2018
Line 4:		Line 4:

	Written by John Freund ([https://www.facebook.com/john.freund.209 https://www.facebook.com/john.freund.209]		Written by John Freund ([https://www.facebook.com/john.freund.209 https://www.facebook.com/john.freund.209]

			[https://www.facebook.com/johnfreundracing/ https://www.facebook.com/johnfreundracing/]

Jpf11: /* Guide to getting your RaceCapture data into your video with RaceRender */

2018-02-26T03:17:05Z

Guide to getting your RaceCapture data into your video with RaceRender

← Older revision		Revision as of 03:17, 26 February 2018
Line 1:		Line 1:


	= Guide to getting your RaceCapture data into your video with RaceRender =		= '''Guide to getting your RaceCapture data into your video with RaceRender''' =

			Written by John Freund ([https://www.facebook.com/john.freund.209 https://www.facebook.com/john.freund.209]

Jpf11 at 00:12, 23 June 2017

2017-06-23T00:12:28Z

← Older revision		Revision as of 00:12, 23 June 2017
Line 105:		Line 105:
	=== Known Issues ===		=== Known Issues ===
	* If you find RaceRender performing terribly slow you may be affected by a timing issue in your RaceCapture log. Rarely, usually right in the beginning of a log if it happens, you can have timestamps that are.. out of order. Events that seem to go back in time. RaceRender expects all the timestamps to go in chronological order and when they don't it has a hard time processing the data. The fix is pretty easy. Open the logs and visually inspect the first page's worth of values in the "Utc" column. These values will be really large numbers as they are time in Unix epoch time, but they should normally go up in value (the value is the number of seconds since I believe a date in the 70s, I forget and I'm a Unix professional :D). If you see any going out of order, you can re-order them or simply delete the entire lines since a handful of data lines won't affect your video rendering results much. Alternatively you can use the GEMS conversion script I wrote found in the Autosport Labs Forums here: https://forum.autosportlabs.com/viewtopic.php?t=3731. Just use the initial perl script conversion and use that output file as your input for RaceRender. This works because that script makes sure to re-order any out of order timestamped log entries. This isn't the first suggestion because using the script takes a bit of technical know-how with setting up a Windows Unix environment and getting packages like Perl.		* If you find RaceRender performing terribly slow you may be affected by a timing issue in your RaceCapture log. Rarely, usually right in the beginning of a log if it happens, you can have timestamps that are.. out of order. Events that seem to go back in time. RaceRender expects all the timestamps to go in chronological order and when they don't it has a hard time processing the data. The fix is pretty easy. Open the logs and visually inspect the first page's worth of values in the "Utc" column. These values will be really large numbers as they are time in Unix epoch time, but they should normally go up in value (the value is the number of seconds since I believe a date in the 70s, I forget and I'm a Unix professional :D). If you see any going out of order, you can re-order them or simply delete the entire lines since a handful of data lines won't affect your video rendering results much. Alternatively you can use the GEMS conversion script I wrote found in the Autosport Labs Forums here: https://forum.autosportlabs.com/viewtopic.php?t=3731. Just use the initial perl script conversion and use that output file as your input for RaceRender. This works because that script makes sure to re-order any out of order timestamped log entries. This isn't the first suggestion because using the script takes a bit of technical know-how with setting up a Windows Unix environment and getting packages like Perl.


			--[[User:Jpf11\|Jpf11]] ([[User talk:Jpf11\|talk]]) 00:12, 23 June 2017 (UTC)

Jpf11 at 23:10, 22 June 2017

2017-06-22T23:10:49Z

← Older revision		Revision as of 23:10, 22 June 2017
Line 101:		Line 101:

	'''10.''' Check the output! I usually have to re-render my video about five times because I miss things or want to tweak things. I may have not quite syncrhonized the video, or maybe gauges were misaligned, or something. Always double/triple check the rendered output.		'''10.''' Check the output! I usually have to re-render my video about five times because I miss things or want to tweak things. I may have not quite syncrhonized the video, or maybe gauges were misaligned, or something. Always double/triple check the rendered output.


			=== Known Issues ===
			* If you find RaceRender performing terribly slow you may be affected by a timing issue in your RaceCapture log. Rarely, usually right in the beginning of a log if it happens, you can have timestamps that are.. out of order. Events that seem to go back in time. RaceRender expects all the timestamps to go in chronological order and when they don't it has a hard time processing the data. The fix is pretty easy. Open the logs and visually inspect the first page's worth of values in the "Utc" column. These values will be really large numbers as they are time in Unix epoch time, but they should normally go up in value (the value is the number of seconds since I believe a date in the 70s, I forget and I'm a Unix professional :D). If you see any going out of order, you can re-order them or simply delete the entire lines since a handful of data lines won't affect your video rendering results much. Alternatively you can use the GEMS conversion script I wrote found in the Autosport Labs Forums here: https://forum.autosportlabs.com/viewtopic.php?t=3731. Just use the initial perl script conversion and use that output file as your input for RaceRender. This works because that script makes sure to re-order any out of order timestamped log entries. This isn't the first suggestion because using the script takes a bit of technical know-how with setting up a Windows Unix environment and getting packages like Perl.

Jpf11 at 22:35, 22 June 2017

2017-06-22T22:35:21Z

← Older revision		Revision as of 22:35, 22 June 2017
Line 73:		Line 73:
	'''6.''' Now that we have the data fields mapped we need to synchronize the data to the video. The easiest way to do this is by using the Synchronization Tool. The button is just below the Input Files section of the main RaceRender video preview screen. Clicking it will open a popup for you to adjust starting position of either the video file or the data file, whichever has more data time-wise than the other at the start. This takes some finesse and can be quite tedious to get quite right but should be self-explanatory after playing around. You'll be playing with starting positions and offsets, and then in the main preview screen using the video playback controls at the bottom to see how things are looking by watching a bit of your previewed video.		'''6.''' Now that we have the data fields mapped we need to synchronize the data to the video. The easiest way to do this is by using the Synchronization Tool. The button is just below the Input Files section of the main RaceRender video preview screen. Clicking it will open a popup for you to adjust starting position of either the video file or the data file, whichever has more data time-wise than the other at the start. This takes some finesse and can be quite tedious to get quite right but should be self-explanatory after playing around. You'll be playing with starting positions and offsets, and then in the main preview screen using the video playback controls at the bottom to see how things are looking by watching a bit of your previewed video.

	[[File:RaceRender ~~syncrhonization~~.png]]		[[File:RaceRender synchronization.png]]

	Here are some tips to make this easier:		Here are some tips to make this easier:

Jpf11 at 22:28, 22 June 2017

2017-06-22T22:28:09Z

← Older revision		Revision as of 22:28, 22 June 2017
Line 84:		Line 84:

	'''8.''' Trim your video to just what you want rendered in your final output, like perhaps your fastest lap. On the preview screen use the video controls to figure out just where you want to start and end your video. To the right of those controls are two flags, one green and one red. Find the start position in your video preview, pause the preview playback, then click the green flag to select the start position. Do the same with the red flag to select the end position.		'''8.''' Trim your video to just what you want rendered in your final output, like perhaps your fastest lap. On the preview screen use the video controls to figure out just where you want to start and end your video. To the right of those controls are two flags, one green and one red. Find the start position in your video preview, pause the preview playback, then click the green flag to select the start position. Do the same with the red flag to select the end position.

			[[File:RaceRender trimming.png]]

	'''9.''' Render your video! In the File menu select Create Video File from Project. You may be prompted to save your project, I would do so in case you realize you need to fix some things and re-render your video. After that you'll be brought to the Create Video File screen. Here's what settings I personally use:		'''9.''' Render your video! In the File menu select Create Video File from Project. You may be prompted to save your project, I would do so in case you realize you need to fix some things and re-render your video. After that you'll be brought to the Create Video File screen. Here's what settings I personally use:

Jpf11: /* Guide to getting your RaceCapture data into your video with RaceRender */

2017-06-22T22:08:30Z

Guide to getting your RaceCapture data into your video with RaceRender

← Older revision		Revision as of 22:08, 22 June 2017
Line 26:		Line 26:
	'''1.''' Install RaceRender 3.5.8 or newer		'''1.''' Install RaceRender 3.5.8 or newer

	'''2.''' '''(Optional)''' ~~Download~~ the basic ~~RaceCapture~~ template ~~found here~~ to where RaceRender3 Templates are stored. On Windows this is:		'''2.''' Download the template/profile files referenced in this guide here and extract the files from the archive: [[File:RaceCapture and RaceRender workflow files.zip]]

			'''3.''' '''(Optional)''' Move the extracted file ''"Project - _6RaceCapture - basic template.rrt"'' to where RaceRender3 Templates are stored. On Windows this is:
	C:\Users\USERNAME\Documents\RaceRender 3\Templates		C:\Users\USERNAME\Documents\RaceRender 3\Templates
	where "USERNAME" is the Windows user you are logged in as.		where "USERNAME" is the Windows user you are logged in as.

	'''3.''' ~~Download the~~ RaceRender Data Profile ~~found here~~. This can be saved wherever you like but I suggest:		'''4.''' The other extracted file should be named with a filename like "RaceRender Data Profile - RaceCapture*.rrlc", including a date. Use the latest version present if there are multiple. This can be saved wherever you like but I suggest:
	C:\Users\USERNAME\Documents\RaceRender 3		C:\Users\USERNAME\Documents\RaceRender 3
	Remember this location for later.		Remember this location for later.

Jpf11 at 22:00, 22 June 2017

2017-06-22T22:00:52Z

← Older revision		Revision as of 22:00, 22 June 2017
Line 9:		Line 9:
	RaceRender software can be found at http://racerender.com		RaceRender software can be found at http://racerender.com

	~~Here~~'~~s an example~~ showing what you can do with ~~RaceRender and~~ your RaceCapture ~~Data~~:		'''Screenshot showing what you can do with your RaceCapture data in RaceRender:'''

	[[File:RaceRender Example Output.png]]		[[File:RaceRender Example Output.png]]

	''Source Video:'''		'''Source Video:'''

	{{#evu:https://www.youtube.com/watch?v=GkKPAN-c_mE}}		{{#evu:https://www.youtube.com/watch?v=GkKPAN-c_mE}}
Line 77:		Line 77:
	* Use major events. Things like specific corners where you brake really hard, or places you know you shifted from one gear to another and can see the shift happen in your video. Look at the data showing on the screen like speed and rpm, and get them to match what you see is happening in the video. These help you not only get close, but can help you really fine tune the synchronization.		* Use major events. Things like specific corners where you brake really hard, or places you know you shifted from one gear to another and can see the shift happen in your video. Look at the data showing on the screen like speed and rpm, and get them to match what you see is happening in the video. These help you not only get close, but can help you really fine tune the synchronization.
	* If you're useing a GoPro try RaceCapture's feature for automatically starting GoPro recording when datalogging begins. This will get your data VERY close from the start!		* If you're useing a GoPro try RaceCapture's feature for automatically starting GoPro recording when datalogging begins. This will get your data VERY close from the start!


	'''7.''' '''(Optional)''' Add some more visual displays of your data! Add more gauges and map them to data fields captured via your RaceCapture. A great one is to add a Throttle gauge as most people have this input (shown in the examples at the top of this page). Experiment! You can do this with the Add button on in the Display Objects section (bottom right) of the preview window. Once you select a gauge face type, select the new object in the Display Objects list and double-click to open its properties. In the properties you'll need to change the Input to the appropriate field from your RaceCapture. Additional Configuration might be required.		'''7.''' '''(Optional)''' Add some more visual displays of your data! Add more gauges and map them to data fields captured via your RaceCapture. A great one is to add a Throttle gauge as most people have this input (shown in the examples at the top of this page). Experiment! You can do this with the Add button on in the Display Objects section (bottom right) of the preview window. Once you select a gauge face type, select the new object in the Display Objects list and double-click to open its properties. In the properties you'll need to change the Input to the appropriate field from your RaceCapture. Additional Configuration might be required.
Line 93:		Line 94:
	* Video Bitrate: 64000kbps (totally arbitrary but I kept going up and up until the video quality looked "good enough" to me. results in a big file on disk but these days I don't care about disk space much)		* Video Bitrate: 64000kbps (totally arbitrary but I kept going up and up until the video quality looked "good enough" to me. results in a big file on disk but these days I don't care about disk space much)
	* Audio Bitrate: 128kbps (this is what my GoPro is recording audio at. Not great to be honest.)		* Audio Bitrate: 128kbps (this is what my GoPro is recording audio at. Not great to be honest.)


	'''10.''' Check the output! I usually have to re-render my video about five times because I miss things or want to tweak things. I may have not quite syncrhonized the video, or maybe gauges were misaligned, or something. Always double/triple check the rendered output.		'''10.''' Check the output! I usually have to re-render my video about five times because I miss things or want to tweak things. I may have not quite syncrhonized the video, or maybe gauges were misaligned, or something. Always double/triple check the rendered output.