Urgency of tempo problem
The fact that MS3, buggy or not, interprets tempo changes differently than does MS2 means that I cannot use it for any new scores, or even adjust old scores to play properly in it, because as soon as the bug is fixed they will break (i.e., the tempos will be misinterpreted in the other direction). For that reason, I would like to urge the tracking-down and fixing of this bug with additional urgency. I can't really post new scores with managed tempo (nor can anybody else, even if they don't realize it). Being able to play MS2 scores properly is of singular importance.
Comments
Can you please include the link to the specific issue you are talking about? I just saw a tempo-related bug reported today, was able to reproduce in the attached score but not one I created myself (in 2.3.2).
In reply to Can you please include the… by Marc Sabatella
https://musescore.org/en/node/279045 thanks, confirmed there by @jm6stringer.
In reply to https://musescore.org/en… by [DELETED] 1831606
Ah, not an actual issue in the tracker, which is why I couldn't track it. Please file it there with the score and steps to reproduce the problem.
In reply to Ah, not an actual issue in… by Marc Sabatella
Here's some "tracker action", a key notion for organists.... https://musescore.org/en/node/279296
In reply to Here's some "tracker action… by [DELETED] 1831606
Or rather #279296: Stretched-fermata timing mishandled in 3.0 Beta (entered as "[#279296]")