Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Generally the watchOS pedometer is the best source of current pace when running, which is why it is the default. The other options are only for when the Pedometer is not working (which was the case a few years back).

Glad you like the app!
Please give me a hint. What value should I choose for over-tempo alarm? what is the smoothest value? Rolling Pace? 10min?
 
Please give me a hint. What value should I choose for over-tempo alarm? what is the smoothest value? Rolling Pace? 10min?
As I say, the pedometer is the best for current pace. Most people do not need to use rolling pace or any smoothing.
 
  • Like
Reactions: Defencer
As I say, the pedometer is the best for current pace. Most people do not need to use rolling pace or any smoothing.
These questions remind me of a thing that I find a bit complex in WorkOutDoors. Say I want to do an interval run alternating between different pace targets and I want to be notified when I go too far above or below that pace. Do I always need to manually specify the lower and upper bound? Or could I give WOD the exact target pace (e.g. 5’15” km) and specify in some setting that the lower and upper bound are 10” below and 10” above whatever the target pace is?
 
  • Like
Reactions: zrr
These questions remind me of a thing that I find a bit complex in WorkOutDoors. Say I want to do an interval run alternating between different pace targets and I want to be notified when I go too far above or below that pace. Do I always need to manually specify the lower and upper bound? Or could I give WOD the exact target pace (e.g. 5’15” km) and specify in some setting that the lower and upper bound are 10” below and 10” above whatever the target pace is?
Sorry, that is not possible. You need to specify a range using a minimum and a maximum rather than a middle value and a span.
 
Could you please show the highest and lowest numbers of the route on the workouts?
 
Last edited:
Hello everyone! @cfc How to recalculate the distance from the sensor Stryd. After all, during training, the distance and pace are reproduced from the sensor, and after training, the GPS recalculates.Laps=km
I ran 14km, finished the training, and shows 12km after the recalculation.
 

Attachments

  • IMG_7937.png
    IMG_7937.png
    381 KB · Views: 30
  • IMG_7938.png
    IMG_7938.png
    569 KB · Views: 24
  • IMG_7937.jpeg
    IMG_7937.jpeg
    229 KB · Views: 25
  • IMG_7939.jpeg
    IMG_7939.jpeg
    201.5 KB · Views: 24
Last edited:
Hello everyone! @cfc How to recalculate the distance from the sensor Stryd. After all, during training, the distance and pace are reproduced from the sensor, and after training, the GPS recalculates.Laps=km
I ran 14km, finished the training, and shows 12km after the recalculation.
There is definitely something strange going on there judging from the straight line in the middle screenshot.

Please could you send the wkt file for that workout to info@workoutdoors.net and I will take a look. To do this tap the Export button 3 times quickly.
 
  • Like
Reactions: Defencer
Hi all. I must confess I am anxiously awaiting the next release, particularly the navigation.

Any thoughts from @cfc whether we will see this in early 2025 ??
 
I am hoping to release a first beta (probably more of an alpha) in the next month or so. It then depends on how testing goes as to when it is released to the App Store.
Happy new year! That’s exciting news! I and many other I’m sure will be eagerly awaiting this alpha (beta) to help you test it.
 
I too am waiting for navigation to arrive. Any screenshots to share in the meantime?
Sorry, not yet. After I read your post I started taking some screenshots to publish here but then remembered just how long it takes to get good screenshots!

Also I realised that the sample routes that I am using are great for coding and testing but don't look the best for screenshots.
 
Sorry, not yet. After I read your post I started taking some screenshots to publish here but then remembered just how long it takes to get good screenshots!

Also I realised that the sample routes that I am using are great for coding and testing but don't look the best for screenshots.
Well ... if you released an Alpha soon there would be no reason for screenshots. 😃
 
  • Like
Reactions: cfc
Sorry, not yet. After I read your post I started taking some screenshots to publish here but then remembered just how long it takes to get good screenshots!

Also I realised that the sample routes that I am using are great for coding and testing but don't look the best for screenshots.
Worth a try :cool:
 
  • Like
Reactions: cfc
Unsure if this has been reported, but for awhile now all my workouts start with my heart rate as a weirdly high level, and it takes 10-20 seconds for WorkOutdoors to correct to the actual heart rate. This does not appear to be a bug with the OS or sensor locking down as checking the heart rate app shows the correct value right before I start.
Screenshot 2025-01-08 at 10.00.17 AM.png
 
  • Like
Reactions: Roger39
Unsure if this has been reported, but for awhile now all my workouts start with my heart rate as a weirdly high level, and it takes 10-20 seconds for WorkOutdoors to correct to the actual heart rate. This does not appear to be a bug with the OS or sensor locking down as checking the heart rate app shows the correct value right before I start.
View attachment 2470357
The watch can take a while to get a reading but that is usually overcome by showing the start screen with the HR so you can wait for a reading. Are you sure the heart rate is showing the correct value before you start? If so then I don't know what is happening. Sorry.
 
The watch can take a while to get a reading but that is usually overcome by showing the start screen with the HR so you can wait for a reading. Are you sure the heart rate is showing the correct value before you start? If so then I don't know what is happening. Sorry.
I do wait for a HR reading on the start screen but that problem happens to me as well sometimes.

Other issue: the action button is not working on the start screen for any workout, I have everything set up even tried rebooting the watch, it helps for a while but then it start failing again.
 
The watch can take a while to get a reading but that is usually overcome by showing the start screen with the HR so you can wait for a reading. Are you sure the heart rate is showing the correct value before you start? If so then I don't know what is happening. Sorry.

If it hasn't gotten a lock yet it should report nothing rather than an erroneously high heart rate. Having that value blanked out at the start of the run was the prior behavior and it's perfectly fine/expected. It was so jarring the first time this happened that I thought I was having a heart attack.

Going through logs, it seems like it started on Dec 25th and has happened on every run since. Don't recall seeing this issue before, and haven't altered the way I used the app or watch. Also confirmed it's not the watch/sensor by seeing the expected value in the HR app at the beginning of several runs while this high HR reading is happening in WorkOutdoors.

Is there a way to get logs to you to investigate?
 
Last edited:
I do wait for a HR reading on the start screen but that problem happens to me as well sometimes.

Other issue: the action button is not working on the start screen for any workout, I have everything set up even tried rebooting the watch, it helps for a while but then it start failing again.
The action button has always been flaky but it is outside of the control of the app. Sometimes it seems that rebooting is the only fix.
 
  • Like
Reactions: Dovales
If it hasn't gotten a lock yet it should report nothing rather than an erroneously high heart rate. Having that value blanked out at the start of the run was the prior behavior I noticed and it's perfectly fine/expected. It was so jarring the first time this happened that I thought I was having a heart attack.

Going through logs, it seems like it started happening on Dec 25th and appears to have happened on every run since. I don't recall seeing this issue before, and haven't altered the way I used the app or watch.

I've confirmed it's not the watch/sensor as I validated my HR is reporting correctly in the HR app at the beginning of several runs while this high HR reading is happening in WorkOutdoors.

Is there a way to get logs to you to investigate?
The latest version of the app is much older than that. Please could you send me wkt files for a workout before the 25th December and a workout with the problem. I can then see if you are using different versions of the app or of watchOS.

To do this tap the Export button 3 times quickly and send the resulting files to info@workoutdoors.net
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.