Rides not completing correctly

[Ash]

I'm experiencing a problem with my Ergvideo files.

The videos don't always run until the end, leaving 1 or 2 seconds on the clock when the video has finished. Below are some example screen shots taken once the ride is over:










Now, ordinarily this wouldn't be a problem, after all, what's 1 second from a 2 hour ride!

However, where it is a problem is with the 20 minute threshold test. It's not possible to get 20 minutes of data.

Below is the 'End of file' after the 20 minute threshold test is complete, following export using Coach software:



The highlighted number is the 1000ths of a second the the ride ran for. As you can see, it falls short of 120,000.

When this file is then imported into Cycling Peaks WKO+, it doesn't show the 20 minutes because the file isn't 20 minutes long, so II'm having to look for my best 19s instead of best 20s!

I can't determine if this problem is the Ergvideo software or not, however it is odd that the rides don't complete, as per the screenshots.

Can you point me in the right direction of a fix Paul?

Thanks.

[ergvideo]

one second? I'm not gonna lose sleep over that. Sorry, truth is better than some spun, insincere excuse, right?

No fix for your wko+ problem right now. The answer on threshold power is given by ErgVideo, average power can be gleaned from the data in wko+ as well as Racermate's files.

Again, to be honest, doing a fix for something as small as a minor incompatibility with yet another third product, really isn't going to be a high priority and wouldn't be reason for an update. Put another way, what is the difference you see between your best 19 minutes and your best 20minutes-1 sample? Or maybe 19.5 minutes? Significant? If it's more than a few watts, you are holding back too much in your 19 minutes!

I have a new release coming out meant to address Win7 and MR2009, but I am delaying it until the Win7 RC1 comes out and I can do some exhaustive testing with it on my own, since the Win7 Beta showed a problem that I expect to be fixed in RC. Then I have to do a minor beta cycle on this build with my regular beta guys. I'll throw in a fix for this, but if the current fix causes a beta fail, I'm ripping it out rather than finding another way and thus gating beta-pass on an unnecessary change. Sorry, I won't publish a schedule on this. It's better to be honest than raise hopes needlessly. I hope it's within a month, but won't say for sure. Depends on how much beta soak I can get.

Paul