Cb plays in wrong octave when generated by "Realize chord symbols"

[MarcSabatella]

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce

1. Create an empty score for piano
2. Add Ddim7 chord symbol to first bar
3. Right-click, Realize chord symbols
4. Click each note one at a time

Result: the Cb (technically Cb5 but enharmonic with B4) sounds an octave too low (like B3)

Supporting files, videos and screenshots

cb.webm

What is the latest version of MuseScore Studio where this issue is present?

OS: Debian GNU/Linux 12 (bookworm), Arch.: x86_64, MuseScore Studio version (64-bit): 4.5.0-250501335, revision: github-musescore-musescore-8b8d44b

Regression

Yes, this used to work in MuseScore 3.x and now is broken

Operating system

Debian 12

Additional context

We've had quite a few kind of similar wrong-octave-on-Cb bugs over the years, so I'm not surprised by this - more surprised to find it worked in MU3, actually.

Checklist

• This report follows the guidelines for reporting bugs and issues
• I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
• I have attached all requested files and information to this report
• I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible