Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[MU4 Issue] Wrong key signature when i add a transposition instrument in this score #15314

Closed
Gai-Luron opened this issue Dec 18, 2022 · 5 comments · Fixed by #15479
Closed
Assignees
Labels
P2 Priority: Medium

Comments

@Gai-Luron
Copy link

Gai-Luron commented Dec 18, 2022

1 - Open this file : Test Score.zip
image

2 - Add new Alto Saxophone 2
image

3 - Result in 3 Sharps key signature Instead of 1
image

OS: Windows 10 Version 2009, Arch.: x86_64, MuseScore version (64-bit): 4.0.0-223510501, revision: github-musescore-musescore-5485621

@oktophonie oktophonie added the P2 Priority: Medium label Dec 20, 2022
@mike-spa
Copy link
Contributor

We can reproduce the issue only on the file you attached, but not on newly created scores. Now, because of the nature of the problem, if the file was created with any build preceding the fix (which happened in #14849), the issue will be still there because it was saved into the file. It would be great if you can try to grab the latest nightly build from the top of the list here and let us know if you can reproduce it on a newly created file

@Gai-Luron
Copy link
Author

Gai-Luron commented Dec 21, 2022

Hello,
To reproduce from scratch with last nightly (same issue in previous versions )

  1. Create a new score from scratch with Flute, Oboe , Clarinet and Sax Alto
    image
  2. Choose Bb keys signature
    image
  3. Result in this score
    image
  4. Select Key signature and press key "Suppr" result strange, no key signature for all instruments even tranposing instruments
    image
  5. Add Again Bb signature to restore initial score. This seems Good
    image
  6. Add a new Sax Alto instrument
    image

Ouppss that no good. Key signature is inconsistent

OS: Windows 10 Version 2009, Arch.: x86_64, MuseScore version (64-bit): 4.0.0-223550502, revision: github-musescore-musescore-5485621

@oktophonie
Copy link
Contributor

oktophonie commented Dec 21, 2022

Thanks for this! (I tried it myself now and can reproduce the problem)

Regarding deleting a key signature (step 4) - this is also what 3.6 does, and at first I thought it was removing the key signature and putting it into 'open/atonal' mode, but it actually isn't. This is addressed by #15503 which will prevent the initial key signature of a score from being deleted: instead it must be explicitly replaced.

@Gai-Luron
Copy link
Author

Gai-Luron commented Dec 21, 2022

Thank's for the answer. Ok for the Atonal mode, but if I put on a key signature again, this atonal mode must disapear, isn't it?.
The first time i remove the key signature was by mistake .

@mike-spa
Copy link
Contributor

@Gai-Luron thanks for your help in figuring this out! The linked PR should fix it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 Priority: Medium
Projects
Status: Done
MuseScore 4.1
  
Done
Development

Successfully merging a pull request may close this issue.

3 participants