Tempo adjusted in one project: Suddenly, it's also present in the other project

Hi everyone,

I recorded my new album two weeks ago using Ardour 9.7. I have to say it was pretty difficult: lots of display errors, and occasional crashes that resulted in lost takes made things challenging. I wanted to report one problem because it seems very strange to me and I need help to fix it:
Before each new song in the studio, I worked with the same pre-created template for rehearsing. As soon as we started recording afterward, I saved the project with the song name using “Save As.” For the next song, I reopened the old template, and so on. During the recordings on different days, I made commits via Git the whole time, which allowed me to track down the problem. The problem I’m facing now is that one song has the wrong tempo—one that I didn’t set or change anywhere. I don’t know if saving the project as “Save As” was the source of the problem.

The problematic song I recorded was at 180 BPM. It stayed that way until we recorded another song (some days later) at 61.666 BPM

I see that the song, which is supposed to be at 180 BPM, is now also at 61.66, and what’s really strange is that the MIDI tracks are now set to 61.666 and they sound correct (just wrong click). So if I reset the project to 180, all the MIDI tracks are, so to speak, broken. To fix this, I’d go back to Git, clean up the MIDI session, export it, switch to git-head, change the tempo, and then import it again. Are there perhaps better ways to do this? I searched the forum for ways to change the tempo without stretching the MIDI, but didn’t find anything. It would also have been very helpful to preserve data like the positions in the MIDI recordings, but exporting and importing will cause that to be lost—along with a lot of the cleanup work I’ve already done, since I noticed the problem so late.

Does anyone see a good way to fix this problem? Or maybe how it came about?
I’m including three versions of the Ardour file from the Git history here:

  • Version 01 where the BPM was still correct (180)
  • Version 02 from a few days later, when we recorded the vocals and it suddenly became 61.66.
  • Version 03 as it is now (61.66) as well → Should now be set back to 180.
    Downloadlink: bug_ardour_bpm - TheGood.Cloud