Wrong tempo after fermata if tempo change added in front

I recall a number of other related bugs being fixed quite a while back; I'm kind of surprised this one hadn't been noticed until now. I believe the issue will turn out to be in Score::fixTicks().

Score::fixTicks() was not being called from TempoText::textChanged(). Submitted a PR, works now.

There is a PR here https://github.com/musescore/MuseScore/pull/2470

but I can't reproduce the bug, I don't see how that could fix it. Can some explain?

lasonic: https://musescore.org/en/node/100776- marc's comment. The problem was that if a tempo change was made *after* the fermata was added, then this tempo change was not getting reflected in the measures after the fermata. To reproduce, change tempo in https://musescore.org/sites/musescore.org/files/fermata_test.mscz. Changing time stretch or saving and reloading the file would make it work though.

The fix solved this problem.

I should have posted it on https://musescore.org/en/node/100776 perhaps, but since this issue had the link here, I posted here

Here are precise steps:

1) my first score
2) fill first two measures with quarter notes
3) add fermata to last quarter note of first measure
4) change time stretch of fermata to 2
5) add tempo text to first note of first measure, quarter = 800
6) play

Result: first measure plays very quickly (800 bpm), then there is a long pause at the fermata (too long - it's scaled according to the default tempo, I think), then the second measure resume at the default tempo instead of at 800 bpm.

The PR will fix this, I tested it on similar reproductions

Fixed in branch master, commit f010c8bb85

fix #100791 - call fixTicks when Tempotext is being changed

Change fix- tempo text and inspector changes

Delete line

Fixed in branch master, commit 24fe175ec5

Merge pull request #2470 from akhisud/fermata

fix #100791 - call fixTicks when Tempotext is being changed

Fixed in branch 2.0.3, commit ea71b87d5d

fix #100791 - call fixTicks when Tempotext is being changed

Change fix- tempo text and inspector changes

Delete line

Workaround. If you save the sore and reopen it, the things work fine.

Sometimes helps only saving.

Same problem happen, if someone change the relative tempo.

Automatically closed -- issue fixed for 2 weeks with no activity.