Metric modulations AKA relative tempos don't set tempo right
Reported version
3.0
Priority
P2 - Medium
Type
Functional
Frequency
Many
Severity
S4 - Minor
Reproducibility
Always
Status
GitHub issue
Regression
Yes
Workaround
Yes
Project
Came up in #277292: support percent values to set the tempo
Metric modulations AKA relative tempos like quarter note equals dotted quarter don't set playback tempo right, but always to 120 BPM, the default.
bee7755, Windows 7, self-built using MSCV
Comments
it is a regression vs. older development builds, these relative tempo markings did work back when they got implemented.
Came up again in https://musescore.org/en/node/291274
Relates to #272381: [EPIC] Tempotext issues
Workaround is of course to calculate the tempo yourself and set via Inspector. Downside is that you need to re-caculate if the tempo before it changes
Tempo is also recalculated correctly after starting/ending editing its text or after adding another tempo marking before this metric modulation. The issue is that is not updated correctly when initially adding metric modulation to a score.
Came up again in https://musescore.org/en/node/308448
and again in https://musescore.org/en/node/317579
Workaround (still) is to 'pretend' to edit it
Again in https://musescore.org/en/node/321032
Another workaround is to toggle "Follow Text" iin Inspector (off and back on), that seems to cause a recalculation
See https://github.com/musescore/MuseScore/issues/15655
In the updated 4.0, setting the metronome speed to a dotted crochet value seems to ignore the complex value, for example in a 6/8 setup, and interpret the dotted crochet as a single quaver, i.e. three times too slow. Equally, when the tempo relates to a minim, the system seems to interpret the minim as a crochet and plays back twice as fast as it should do. The examples I used were minim = 80. It seemed to interpret that as a crochet = 80 and dotted crochet = 65 where it seemed to interpret that as a quaver = 65.