Please keep Circuit Tools Support as is

nikoelt

Hello,

I noticed in one of the posts that you are considering discontinuing support for the .vbo (Circuit Tools) Export Format due to a crash issue with the latest version.

I would like to bring to your attention that the export functionality works flawlessly on the macOS version. Additionally, if users download an older version of the RaceChrono Pro software from here https://circuit-tools.software.informer.com/versions/, it also works on Windows.

I have backed up the current version of RaceChrono Pro in case you decide to drop support for this format by deleting the export functionality, but I sincerely hope you will reconsider and continue supporting it since it continues working as is

All the best,

kegori

Hi nikoelt, in case CT discontinuing with RaceChrono exports, do you have any other software to analyze the data on PC?

Thanks!

MiguelQ90

Hola vi su hilo de conversación y si funciona solo hay que cambiar los formatos de los archivos exportado en el RaceChrono en el archivo vbo y listo me llevo varias pruebas pero lo hice funcionar a la perfeccion con le video y vuelta ideal en estos dias voy a publicar un video o dejar algún manual de como funciona, son varios pasos pero vale la pena Saludos desde chile

Cali_Chuck

++1 for keeping this exactly the way it is (unless you want to go back and add video support :smile: ).

I routinely import RaceChrono generated .vbo files into Circuit Tools Windows for more detailed analysis than is possible on a mobile device.

I also sometimes manually hand process GoPro video to view in Circuit Tools along with the RC export data but it is very cumbersome to get the time points correct.

Anyway, this is a very very very useful feature and VBO support should stay.

dustinsterk

+100, please do not remove this!

Cali_Chuck

In light of the Circuit Tools 3 problem discussion, I wanted to repeat my strong support expressed back in April to not remove VBO export.

First, while I sometimes do see the CT3 file checksum error, it is hit or miss. I find that disabling automatic ideal lap generation reduces or eliminates the error. So CT3 is NOT a reason to deprecate support.

But the biggest reason to keep it is I finally just figured out how to properly export VBO with attached videos from RaceChrono that are opening just fine in Circuit Tools 2 and 3. All this time I have been using a 3rd party utility to manually join the VBO and MP4 files, when it looks like I was just doing the export procedure wrong in RC.

I never really dug into video export given all the user comments in this forum about how Vbox video export was broken and won't be fixed. But in current 9.1.3 I am getting perfect synchronized video exports. Trick is to set the Video Channel on the export screen.

So please please keep the VBO export function.

Adonis

Agreed, please don’t remove vbo exports. It works with circuit tools on Mac OS, circuit tools for iOS, and circuit tools 2 for windows.

aol

I was never going to remove the .VBO export, but I was considering removing the video indexing on the exports.

@Cali_Chuck OK, so it still works? Then there's no need to remove the video indexing either.

Cali_Chuck

I can confirm that I have produced 6 VBO+MP4 output pairs in RC 9.1.3 in the last two weeks that all open fine in both CT2 and CT3. I tested proper synchronization of laps by opening up 6 different lap video windows side by side and they all advance in sync.

Further, the GPS position shown in the track map diagram corresponds exactly to the video position.

I made a close track buddy of mine aware of this - who is a SW engineer and has written some complicated code to produce VBO Files. He reports also being able to export and view some of his most recent Laguna Seca sessions in Circuit Tools using RaceChrono 9.1.3.

Maybe it was broken at some point - not sure - but it's absolutely working now. I now understand that the mistakes I was making when attempting this last year were (1) not specifying an overlay and (2) also not specifying a video channel. Stumbled into it completely by accident because I was doing some footwork training with my race coach so we put another GoPro in the footwell for the first time and I had to go build a PIP overlay for RC. That's when I found the "video channel" selector popup in the export screen which until that point I had had no reason to try. Presto.... suddenly Circuit Tools opens the file with the video.

Would be good to get some other confirmations from the community.

menugrand

Yea I will echo the comment that data and video works great in CT2 so long as you make sure you have the video channel selected when you export the VBO file from Racechrono. It seems to default to off regardless of whether there is a video file there or not. I have not been able to stop the checksum error in CT3 popping up however which is quite annoying...

Cali_Chuck

One idea here to improve takeup of the feature... seems to me that RC should throw a GUI warning if a user attempts to do a VBO export without specifying a video channel to remind user that if his/her intention was to get video that they have to set one.

Could also be addressed by maybe being more explicit in on the VBO option export page with a message to effect that "Video export supported but requires choosing a video channel".

Certainly a note like that would have gotten me to a working outcome a full year before I stumbled into it by accident.