Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Apps WorkOutDoors: New workout features

One thing I noticed with the latest version of WOD is that after you finish the workout or just open and close the app on the watch, the white circle with arrow icon at the top of the screen is no longer there, as opposed to the previous versions when it stayed there for another minute or so. How come?

Question about Strava: I will probably soon sync my WOD with Strava. What are the recommended settings for Strava File Type (GPX / TCX / FIT)? Any other recommended settings I should be aware of?
 
jon08 said:
One thing I noticed with the latest version of WOD is that after you finish the workout or just open and close the app on the watch, the white circle with arrow icon at the top of the screen is no longer there, as opposed to the previous versions when it stayed there for another minute or so. How come?

Question about Strava: I will probably soon sync my WOD with Strava. What are the recommended settings for Strava File Type (GPX / TCX / FIT)? Any other recommended settings I should be aware of?
Click to expand...
I don't know for sure what may have affected that, but the most likely candidate is the removal of the option to keep the GPS On for a minute after use. By default it was off in recent versions but maybe you had switched it on at some time.

FIT files seem the best for Strava, so they are now the default as of the most recent version of the app. They seem to make it most likely that Strava will respect the distances in the file and it will match the distances in WOD.
 
  • Like
Reactions: jon08
Nope. No breadcrumb trail on the new beta.

(Bonus dog pic)
 

Attachments

  • 1C4D3533-1F55-44B0-BD58-609C20C90135.jpeg
    1C4D3533-1F55-44B0-BD58-609C20C90135.jpeg
    402 KB · Views: 121
  • CFDF9F0E-A0D0-41A7-BF01-F089A5BE808A.jpeg
    CFDF9F0E-A0D0-41A7-BF01-F089A5BE808A.jpeg
    1.2 MB · Views: 131
  • Love
  • Like
Reactions: johnl1275 and NME42
Hey @cfc , I'm still learning the ins ad outs of the app so if this is something that you addressed earlier in the thread then I apologize. I noticed that if I initiate a workout through app and select a fixed time or distance goal then that is how it shows up if I later go to view the workout in the Apple Fitness app. If I do an open workout then it shows properly as seen below. Is there something I can do so that it shows up properly?
 

Attachments

  • unnamed.jpg
    unnamed.jpg
    149.6 KB · Views: 78
Cowboy8467 said:
Hey @cfc , I'm still learning the ins ad outs of the app so if this is something that you addressed earlier in the thread then I apologize. I noticed that if I initiate a workout through app and select a fixed time or distance goal then that is how it shows up if I later go to view the workout in the Apple Fitness app. If I do an open workout then it shows properly as seen below. Is there something I can do so that it shows up properly?
Click to expand...
There is a bug in the current version where it shows "_FixedDistance", which will be fixed in the next version, which will show it as a normal workout. Do you mean that you want to see "Fixed Distance" in the WOD iPhone app?
 
  • Like
Reactions: Cowboy8467
stridemat said:
Nope. No breadcrumb trail on the new beta.

(Bonus dog pic)
Click to expand...
Oh well. Sorry about that. I will take another look. Unfortunately bugs that I cannot reproduce are more difficult to fix.
 
cfc said:
There is a bug in the current version where it shows "_FixedDistance", which will be fixed in the next version, which will show it as a normal workout. Do you mean that you want to see "Fixed Distance" in the WOD iPhone app?
Click to expand...
No, it looks perfectly fine in the WOD iPhone app. It's only when I view my workouts within the Fitness App on my iPhone that it shows "__Fixed Distance" or "__Fixed Time".

I definitely prefer that it simply say "outdoor run", "indoor run", etc. If this is something that is in line to get fixed in the next version then that is perfect.
 
  • Like
Reactions: cfc
Cowboy8467 said:
No, it looks perfectly fine in the WOD iPhone app. It's only when I view my workouts within the Fitness App on my iPhone that it shows "__Fixed Distance" or "__Fixed Time".

I definitely prefer that it simply say "outdoor run", "indoor run", etc. If this is something that is in line to get fixed in the next version then that is perfect.
Click to expand...
Yes, this is fixed in the code and will be fine in the next version.
 
  • Like
Reactions: Cowboy8467
Is it possible to display the HR value (bpm) in the HR zone corresponding color (blue, green, yellow, orange, red)?
 
  • Like
Reactions: sam3k
cfc said:
Yes, all apps do some degree of smoothing to calculate the ascent and descent. Otherwise sensor variances would mean much higher values than expected. However the algorithm vary. If you load exactly the same GPX file into Garmin, Strava etc they can produce very different results due to the smoothing. This is particularly true on relatively flat routes where sensor variance makes more of a difference. With WOD I tried to produce something between Strava and Garmin, but it really depends on the route.
Click to expand...
Just wanted to update that I'm still seeing really low elevation numbers. Compared to the numbers from Garmin, Coros, Strava and the native Apple Workout app, WOD is only crediting about 40-60%. This is across both road and trail runs.

I live in a fairly hilly area with lots of rollers. The other devices and apps seem to capture most of the information when traversing these short ups and downs. Of course, it could be a problem with the AW's baro sensor. The raw elevation charts from the GPX files are a bit crazy. But the native app seems to compensate well enough.

For a recent relatively flat road run loop, WOD calculated 82 ft elevation gain and Garmin gave 187 ft. I'm not saying the Garmin is correct, but the measured max. elevation across the route was 1,032 ft and the min. was 930 ft. 1032 - 930 = 102. Accounting for the rollers, the gain should be something close to double that. On wooded trails where I often cross 2,000+ ft of gain, these numbers are even more exaggerated.

This is my ONLY gripe with WOD. Otherwise, it's been great. However, I'm finding myself going back to the native app for some of my runs as I enjoy seeing those vertical numbers! Anyone else experiencing this?
 
cfc said:
Oh well. Sorry about that. I will take another look. Unfortunately bugs that I cannot reproduce are more difficult to fix.
Click to expand...
I’ve done nothing and they are working this evening. Not even rebooted any of the devices.
 
  • Like
Reactions: cfc
ignas said:
Hey, love the app!

I have run into a couple minor issues:

1. Sometimes the GPS route does not get imported into Apple Health, but it is visible in WorkOutDoors. Is there a way to reimport the workout to Health after it's finished? Right now I end up exporting TCX and then use RunGap to import it, but it would be nice to not use a different app (importing TCX like this adds segments for every km).

2. It feels like average run pace is wrong at the start of the workout, as if it's including time from when I opened the app instead of when I press the button to start. I usually keep the app open for a half minute or so to acquire GPS lock before starting.

I don't mind either too much, but if there's a setting somewhere already, I'd appreciate a pointer.
Click to expand...
Hi @cfc, I don’t know if you have been able to look into the 2nd issue already? This is something that I have also noticed a few times. For normal workouts, this is not that much of an issue. But when I was running a 5k race last Friday, I was total surprised to have 3.24 for my first 1k while the WOD was consistently indicating an average pace of more than 4.00 during that first km. Can send you the file if you want.
The good thing is that all data look normal after finishing the workout.
Issue was first noticed in one of the first betas, but seems to be still present in the latest release. Not sure if it is relevant to this issue, but I’m using a Stryd Power meter.

Apart from this: fantastic app!
 
Celestial Wolves said:
Hi @cfc, I don’t know if you have been able to look into the 2nd issue already? This is something that I have also noticed a few times. For normal workouts, this is not that much of an issue. But when I was running a 5k race last Friday, I was total surprised to have 3.24 for my first 1k while the WOD was consistently indicating an average pace of more than 4.00 during that first km. Can send you the file if you want.
The good thing is that all data look normal after finishing the workout.
Issue was first noticed in one of the first betas, but seems to be still present in the latest release. Not sure if it is relevant to this issue, but I’m using a Stryd Power meter.

Apart from this: fantastic app!
Click to expand...
No-one else has ever mentioned the pace being off at the start but feel free to send me the wkt file if you want.
 
Duffman19 said:
Just wanted to update that I'm still seeing really low elevation numbers. Compared to the numbers from Garmin, Coros, Strava and the native Apple Workout app, WOD is only crediting about 40-60%. This is across both road and trail runs.

I live in a fairly hilly area with lots of rollers. The other devices and apps seem to capture most of the information when traversing these short ups and downs. Of course, it could be a problem with the AW's baro sensor. The raw elevation charts from the GPX files are a bit crazy. But the native app seems to compensate well enough.

For a recent relatively flat road run loop, WOD calculated 82 ft elevation gain and Garmin gave 187 ft. I'm not saying the Garmin is correct, but the measured max. elevation across the route was 1,032 ft and the min. was 930 ft. 1032 - 930 = 102. Accounting for the rollers, the gain should be something close to double that. On wooded trails where I often cross 2,000+ ft of gain, these numbers are even more exaggerated.

This is my ONLY gripe with WOD. Otherwise, it's been great. However, I'm finding myself going back to the native app for some of my runs as I enjoy seeing those vertical numbers! Anyone else experiencing this?
Click to expand...
I may revisit the elevation calculations one day but it isn't high on my list. Sorry about that. The algorithm is slightly biased towards non-flat routes though, because those are the ones where people are generally more interested in the ascent.
 
I've been using the map-only mode often when cycling since my Wahoo ROAM records everything, but have a couple of questions:

1. Is there a way to configure the gradient colors when using a route? It would be nice to be able to do green, yellow, red, dark red to match what my ROAM does.
2. When doing an out and back route, are the gradient colors direction aware? For example when I'm going the out, the gradients are for the climbs in that direction, and doing the back the gradients are for that direction? If not, how does WOD determine how to color them?
 
  • Like
Reactions: cfc
estesbubba said:
I've been using the map-only mode often when cycling since my Wahoo ROAM records everything, but have a couple of questions:

1. Is there a way to configure the gradient colors when using a route? It would be nice to be able to do green, yellow, red, dark red to match what my ROAM does.
2. When doing an out and back route, are the gradient colors direction aware? For example when I'm going the out, the gradients are for the climbs in that direction, and doing the back the gradients are for that direction? If not, how does WOD determine how to color them?
Click to expand...
There is no way to configure the gradient colours at the moment. Sorry about that.

Out and back routes are difficult to handle at the moment. The app draws both aspects of the route but cannot automatically determine whether outward or back have priority, so either could be on top. When I add route following in the future I may add that. To be honest I hadn't even considered it until you mentioned it but will bear it in mind when I do code that functionality.
 
@cfc did a hike couple of days ago, and got a message "Apple Workout considered 1.45km of your workout as invalid". What would be the reason for that?
 
muellered said:
@cfc did a hike couple of days ago, and got a message "Apple Workout considered 1.45km of your workout as invalid". What would be the reason for that?
Click to expand...
The app measures the distance in two ways: using Apple's calibrated distances from the pedometer (which is the default) or by using the GPS.

When the distances differ by more than 10% then it shows this message. It either means that the GPS was poor or that the watch needs calibrating. To check this go to the GPS tab and see the average accuracy. If it is less than about 8m then the GPS was probably ok. If so then the watch needs calibrating as described here:
https://support.apple.com/en-us/HT204516.

If the recalibration doesn't work (Apple's pedometer just doesn't work for some people) then switch to using the GPS for distance. Note that this makes it susceptible to poor GPS signals, such as when you go through tunnels etc.

When the distances are as massively wrong as you are seeing then it usually means that you have done something strange to confuse watchOS. Have you maybe done a different activity (in any app) and told the watch that it was a running activity? I have heard of people doing skateboarding or cross country skiing but have told the watch they were running. This has then made the watch think they have the wrong running stride length, which has affected the distance estimates.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back