Metronome bug

K15R Hey! I would love to take a look at the metronome not working for you. Please let me know the following info which will help me investigate into this more:

• Has the metronome ever worked? If so, when did you notice that it stopped working?
• What do you have your watch settings set for the metronome? I understand that you have it set for 170 bpm, but what is the Alert Frequency and do you have Sound & Vibe enabled?
• Please upload a preview of what the metronome sounds like, submit the video using this link. 
  • To get a preview you would go into Run > Run Settings > Metronome, scroll down to the bottom and select Preview

**

I did not test it before so i have no clue if it ever worked.

settings are: 170bpm, beep only, every 2nd beep

i uploaded a sound file which was during an active run, the video is without having a run active (i assume the cpu has some cycles to spare when not doing gps recording

Forerunner 970 - Metronome timing is irregular
I can confirm the same issue on my Forerunner 970 running software version 17.33.
The metronome does not maintain evenly spaced beeps. Instead, it seems to "catch up" by emitting bursts of beeps after longer gaps.
The total cadence appears correct (e.g. 180 spm on average), but the timing between individual beeps is inconsistent.
Additional observations:
Bluetooth headphones connected
Audio metronome enabled
Music playback is completely normal and uninterrupted
Garmin Coach workout active
Issue occurred throughout an entire run, not just once
I have noticed occasional instances of this behavior in previous runs as well, but recently it became much more frequent
Because I regularly train with a 180 spm metronome, the irregular timing is very noticeable and makes the metronome difficult to use for cadence training.

Thanks

I can confirm the same issue on my Forerunner 970 running software version 17.33.

The metronome does not maintain evenly spaced beeps. Instead, it seems to "catch up" by emitting bursts of beeps after longer gaps.

The total cadence appears correct (e.g. 180 spm on average), but the timing between individual beeps is inconsistent.

Additional observations:

• Bluetooth headphones connected
• Audio metronome enabled
• Music playback is completely normal and uninterrupted
• Garmin Coach workout active
• Issue occurred throughout an entire run, not just once
• I have noticed occasional instances of this behavior in previous runs as well, but recently it became much more frequent

Because I regularly train with a 180 spm metronome, the irregular timing is very noticeable and makes the metronome difficult to use for cadence training.
The issue affects cadence-based training because the metronome becomes unreliable even though the average cadence value is correct.
Thanks.

By the way, why there's no metronome available for cycling activities? 

Cadence is an important metric for cycling, so the metronome would be as useful as it is for any sports with cadence.

Assi Can you upload a video of what you hear with the metronome and upload it here. 

• To get a preview you would go into Run > Run Settings > Metronome, scroll down to the bottom and select Preview

Can you also tell me the exact settings you have for the Metronome - specifically the BPM,  Alert Frequency, and Sound & Vibe?

9970217 I can get this feedback sent internally to our team that you would love to see this implemented!

Please, thank you!

Hi,

I uploaded a text file named “Metronome Bug Times”, where you can see the issue in detail.

My metronome settings are:

180 BPM

Alert every 4th beat

Sound & Vibe: Tone

I have been using the Forerunner 970 for about 60 days. Roughly speaking, I first noticed this issue about 14 days ago.

I can honestly say that using the metronome has been the most significant boost to my running performance, so I’m really looking forward to having it work correctly again.

If I may ask, is it possible that an algorithm was recently added to the metronome — something that tries to lock onto the runner’s footstep pattern in order to help synchronize cadence when the runner loses sync — instead of using a pure fixed-timing tick calculation?

Thanks.