BPM Labelmaker and Rhythm Track No Longer Lining Up?

So, this is quite curious. In my Dozen or so years of using Audacity I’ve never had this happen (or I simply didn’t notice it, although I find that a bit hard to believe…). Long story short, I went to make a “click track”/ rhythm track like I do every day, and then I went to make the BPM labels so I can make exact edits, of course, and they’re not lining up for some reason. It’s the oddest thing; the BPM labels start out just a touch ahead of the click lines, then they line up perfectly towards the middle, then they drift to lining up AFTER the click waveform. It’s the darndest thing. I use Audacity for all my pre-pro and rely HEAVILY on this feature, so getting this sorted pronto is an absolute must. I’ve looked in the settings of the Rhythm Track feature and the BPM label maker and everything is zeroed out - No swing or anything.

Can anyone shed some light on this? I am still using a legacy version of Audacity (Version 2.4.2) but that shouldn’t make a difference right?? Been using this exact one for years…

Thanks, all.

Does your version of “BPM Labels” have the option: “Speed Up/Slow Down by … BPM”?
If it does, ensure that it is set to zero.

Yes, Sir - Everything is zeroed out in both the rhythm track maker and the bpm label maker.

I wonder if I should try downloading a different version of Audacity and trying there? This is soo weird. I swear it’s never happened before…

Is there a way for me to attach screen shots here?

Hopefully you can see here. Everything starts out fine, but then drifts off towards the end…


I’m not able to reproduce the problem. They line up exactly from the first to the 1000’th label.

What version did you try it in?

I tested in 3 versions:

  • 2.4.2 (Ubuntu)
  • 3.5.0 (AppImage)
  • 3.7.0 (Built from source)

Hmm… wow. Okay, very interesting.

What could it be then in my case?? Super strange - And I swear it just started…

I am on Windows. Hmm… I wonder if that has something to do with it??

UPDATE: I tried downloading version 3.0 and 3.2 - The problem persisted in 3.0 and 2.4.2, but is resolved in 3.2 - It’s perfect in 3.2

Very odd!

I don’t see any reason why it should, but I’ll check it out on Windows if I get the chance.
In the meantime, someone that uses Windows regularly may be able to test it and comment here.