Fastest lap issue

[Marcus]

Sorry guys, I don't want to cross post but I realised I placed my original question in the wrong section and figured you might nowt have seen it.

Here it is anyhoo.....

fastest lap won't work thread (http://www.chasecam.com/forum/showthread.php?p=1420&posted=1#post1420)

[Rolf]

No problemo. I replied in your original thread since there is more information there.

[sickmint79]

i'll hijack this and ask about my own fastest lap questions --

my fastest lap is displaying the fastest lap in the data. is this what it is supposed to do, or is this supposed to display the fastest lap so far during playback? and be updated when new faster laps are created?

fast lap, same pos - time diff kicks out an error when i include it in a gauge and try to add it to my project. i added it as a decimal. error is: index was out of range. must be non-negative and less than the size of the collection. parameter name: index.

[Marcus]

my fastest lap is displaying the fastest lap in the data. is this what it is supposed to do, or is this supposed to display the fastest lap so far during playback? and be updated when new faster laps are created?
This is how it's coded. I also would prefer it to be a "Fastest lap so far" kind of parameter. In my mind having the fastest lap show right at the beginning of the footage makes the whole thing kinda redundant. We want to see the lap time fall as we get faster [or not] through the video right?

fast lap, same pos - time diff kicks out an error when i include it in a gauge and try to add it to my project. i added it as a decimal. error is: index was out of range. must be non-negative and less than the size of the collection. parameter name: index.
That should be a time, not decimal....

[Dmitriy]

actually for the video I rendered the fastest lap only showed until 1 lap was complete then it showed them correctly.

[BroussalM]

Hi Marcus,

Could you explain me why you want this "faster lap so far"? It could have an interest also for me, but I don't understand the purpose.

With the "faster lap" and it's number at the beguinning of the video, you wait that lap and have a better concentration specialy on that one.
If you have "faster lap so far", you are obliged to wait the end of the video to be sure that the best lap is run, playback to it's number and look again to see why is it so fast.
There is some more suspense, but I don't see why it could be better?

About the lap time, I'm going to used 3 things ( I told you I don't have GPS data )
Current lap time / previus lap time and best lap time. I compare these 3 times and have a good view of my progress (or not) laps after laps.

As you have GPS you can creat splits to see exactly where you are faster or slower in your laps. It's certainly very interesting!

Sure you'r right, all the gauge input with a "< ...time...> " into their ref are not decimal but time.

Cheers
Michel

[Marcus]

well it's a case of personal preference of course. But for me, if the fastest lap time is displayed in frame#1 then I think it's a waste of dashboard space and certainly not dynamic. You could just have the fastest lap time in the title and use the space on the dashboard for something else no?

The other thing is this, say you have a 30 minute raw footage with data. You might not want to make the finished video 30 minutes so choose an interesting part of say 4 laps long. Now the fastest lap time displayed on the dash might not even be one of the laps shown in the finished video!

About suspense or tension - would you be as interested in watching qualification runs for F1/Nascar/Sportcars or whatever if you knew the best time before the cars started to run???

[BroussalM]

Hi Marcus

"About suspense or tension - would you be as interested in watching qualification runs for F1/Nascar/Sportcars or whatever if you knew the best time before the cars started to run??? "
GOOD TOUCH ! :D
My "suspense" was a little bit provoque...

At that time I can't try but you could delete in the colomn Time of your file .csv the data you don't want and just keep what you need during the 10'of your last video. So you get the best time of that part. I try asap.

Cheers
Michel

[sickmint79]

it seems that we could get the behavior (fastest lap of session) by manipulating the csv by hand

[Marcus]

Honestly i don't see how. The CSV is parsed all the way through by Dashware as soon as it's opened, so wherever that fastest lap is, it'll find it and post it in Frame#1

[BroussalM]

Hi,

You said :

"The other thing is this, say you have a 30 minute raw footage with data. You might not want to make the finished video 30 minutes so choose an interesting part of say 4 laps long. Now the fastest lap time displayed on the dash might not even be one of the laps shown in the finished video!"

You can change what you want by hand into your .csv. I test and it's working fine.
First of all, into Excel make a copie of your original .csv call "lap time delete.csv" for exemple.
Locate the 4 most interesting laps ( it's not during that laps you get your best time ) Locate them into the .csv. It's purhaps the most difficult of the work. Help yourself with the differents lap times.
After, just delete the values into your lap time column, before and after those 4 laps time. Dashware will can't get anything but your fast lap time of those 4 laps.
Of course it's not the absolute solution for you, the best lap time of those 4 laps is display on the first image, but it could be interesting.

It's a good solution when a sensor work during a practice and not during the race. You can copie and exchange the value from the both .csv. The most important is doing something which seems real.
I'm used to change value on all my .csv for the gears.

The .csv is only a value file, if you want to believe your friends you can run at 350 MPH with your bike, get a video ( prefer to speed up when playback...), creat a .csv with your owne values, used Dashware and make a good joke !

Cheers
Michel

[Marcus]

Yea, I see that Michel.
It's my contention that the fastest lap should update lap by lap. That's how you see the fastest lap anywhere else on the planet, be it during the race, qualification or just practice.
If you remove parts of the CSV file Dashware will still read the remainder and post the fastest calculated lap time at frame #1, so you don't achieve anything other than ensuring that time is in the video footage (at some point).

The other way this whole feature reflects is in the "same place diff time" parameter. It's always referring to the fastest lap, so it has little use on a dashboard as the values it's showing are compared to a lap feasibly in the future, so you learn nothing from it.

i believe Mark & Rolf are looking into adding more control over the timing functions for a later release.. That'll be sweet !!