Tempo set in New Score other than quarter note doesn't reflect supposed BPM value; uses "quarter = ...BPM" instead of "desired = …BPM"

[cgpqci]

Describe the bug Setting tempo while in New Score to anything other than quarter note/crochet + metronome doesn't actually reflect real supposed BPM once done creating score and instead yields BPM value macthing the number in written tempo.

To Reproduce Steps to reproduce the behavior:

1. Create New Score
2. In "Additional score information" section, set tempo with any duration other than a quarter note/crochet + any desired metronome value.
3. Click "Done."
4. Select tempo on first measure and check Properties.
5. See error.

What it yields:

What it's supposed to be:

Platform information OS: Windows 10 Version 2009, Arch.: x86_64, MuseScore version (64-bit): 4.0.0-223072007, revision: github-musescore-musescore-2c34155

[MarcSabatella]

I think the issue mentioned above is the same thing, and I just got another report of this from a user.

[zacjansheski]

Combining https://github.com/musescore/MuseScore/issues/15845 with this issue

[shubham-shinde-442]

I Would like to work on this issue.

[rpatters1]

This looks like it could be an issue I can do, if you wish.

[rpatters1]

I am not able to reproduce this issue in either 4.4.2 (macOS release) or the master branch. Could it have gotten a fix along the way somewhere? Or are there extra non-documented steps to reproduce? I am using macOS, and though this is a Windows issue I saw some of the linked issues were on mac and Linux.

See next comment.

If need be I can get a Windows dev environment running.

[rpatters1]

Never mind. Now I see the issue. Okay, off to work.