Any update Nate?
It must be getting closer to “early release” now ![]()
I was listening to the latest Wahoo podcast and they allude to the fact that distance on an indoor trainer is irrelevant and “you didn’t actually go anywhere”
Around the 2min mark.
We all know that already and its been mentioned numerous times in this thread. But many people log miles and want to continue to do so as close to real speed as possible.
Yeah, I plan to listen when I can, but it sounds like the same old info / opinion that’s been well beaten already. As said, there’s more than one way to look at this topic.
Edit after listening: Nothing burger. Same opinion as stated above and is one point of view. They are specifically focusing that podcast on training data, so the values they focus on do make sense for that context. Their dismissal of speed/distance in that light is one thing, but as covered well above, that is not the only way people can use the S/D data outside of that scope.
In short, we all have opinions which is great. Some want this data, others don’t. TR seems interested in refining their implementation related to that data (via Nate’s more recent comments). Great if they do for those that want it, and great if they also include an option to exclude the data for those that don’t.
It’s possible to make TR settings that likely satisfy people from both camps in ways better than the current state. If they do that, I welcome the changes. Simple as that.
The approach of allowing the users to decide themselves if they want mileage calculated seems like the best of both worlds. This whole argument seems kind of like the Android vs iOS argument, both sides have valid points and neither side is likely to convince the other side to switch viewpoints.
This is not a lie.
You moved 0 miles.
BUT
some may argue that they want to keep track of usage of chain and other drivetrain component.
Completely agree that both sides need to have the option. Currently only one side has the option.
- That’s not entirely true at present. Some people have successfully applied the Zero Wheel Size option (mentioned several times above) to get no S/D data output. Sadly, it does not work in all cases, so the request for direct ‘Exclude S/D Data’ control makes sense.
Edit:
-
And to make it clear for those that may have missed it above, Nate already acknowledged they have plans to address this. It appears their stated goals should satisfy the requests shared in this topic.
-
Point being that we just need to have patience. There’s no need to convince TR that change needs to happen, because they already said it’s planned.
Another status point mentioned in a separate topic: