Back to Blog
So the software needs to catch up the increasing number of cores available in CPUs. I believe one issue is that RR3 only is using about 12-14 threads instead of the possible 24 threads. This dropped my testing video render from 28 minutes to 24 minutes. We recommend using short video clips or images to represent your message visually. That doesn't mean it's perfect, though there are still opportunities for further improvement that I'd like the pursue. I went from a 6-core intel 8700K running at 100 to a 12-core AMD 3900X running at 60. Add up to 30 seconds of video at a time to each slide. GoPro GPS Quick Fix (Paid) - Modifies your video files to enable gauges / performance stickers in GoPro Quik. GoPro Telemetry Extractor (Free/Premium) - Extract, visualize and convert any data stream (sensor) to other formats. While traditional video editors and encoding tools are able to make use of extensive optimizations and parallelization, RaceRender is compositing many things together, with the possibility of varying levels of transparency, so often times it just has to wait for some tasks to complete before it can start on others that could be impacted by its results. Telemetry Overlay Windows / macOS / Linux (Paid / Trial) - Add customizable gauges to GoPro (and other cameras) videos. For the most part, we'll fire up as many threads as you have CPU cores (current max is 32 threads for core renderer), and try to use all of them, but there are always going to be some tasks that don't lend themselves to parallelization, or that have such small units of work that it would take more resources to manage splitting it up than to just do it on one core. However, when the game is frozen the sound keeps playing only the video is affected. In order to get lap counts and times, as well as draw a cleaner track map (based on one selected lap), you may need to. My game freezes randomly from time to time for like 1 - 3 seconds, then it gets back to normal, but the process repeats itself every now and then. RaceRender can usually estimate speed, heading, and G-force from the GPS data, when they are not otherwise provided or supported from the data file. Usually in these cases, the primary issue is a single-threaded bottleneck, such as waiting on file storage I/O, OS functions, or there are also a few things internal to RR that could be the culprit too. This dropped my testing video render from 28 minutes to 24 minutes. Few seconds random freezes from time to time.
0 Comments
Read More
Leave a Reply. |