This is nuts. This is a BUG. It’s not some config thing. I have tried everything to fix this in an existing project but it is SET THIS WAY PERMANENTLY.
For me the experience is that my count-in tempo is ~120 and my song is 161.
If the only fix for this is to create a NEW PROJECT then THERE IS A BUG YOU NEED TO FIX.
I have toggled the Tempo Track on and off and THIS IS NOT THE PROBLEM. THERE IS A BUG .
BUG TITLE:
The COUNT-IN TEMPO IS > OR < THE BASE TEMPO when the Tempo Track IS DISABLED.
Get a tester on this please. Here are the vectors of attack. Seriously…
- Create a new project.
- Change the tempo.
- Unchange the tempo.
- Keep f******* around with ANYTHING TEMPO until the following state is achieved:
The COUNT-IN TEMPO IS > OR < THE BASE TEMPO when the Tempo Track IS DISABLED.
Seriously, this should take a good tester less than a day to reproduce. After than you can work out how to trace the spaghetti.
You have to fix this stuff. It is simply not acceptable to have 2 bars of count-in at 120 bpm and the song at 161.
AGAIN PLEASE. THERE IS NO TOGGLING OF TWIDDLES THAT FIXES THE PROGRAM’S ERROR. THIS IS NOT A USER PROBLEM. THIS IS A BUG.