MS 4 Beta - Added sharp to the chord signature ?!
I have a Mac Monterey OS
This is the version of my MS4: MuseScore 4.0.0.223300403 Nightly
When I wanted to insert a # in a chord abbreviation (for example C#m), I always typed Option + # (attachment 1); now the cursor stops and does not insert the sharp. This problem does not exist if I type, for example, a line text or other texts. Is it a bug? What can I do?
P.S: On MS 3.6.2 inserting the # in the chord abbreviation works well.
Thanks to those who will help me.
| Attachment | Size |
|---|---|
| 1.png | 481.23 KB |
Comments
Sharp signs in chord symbols have always been handled automatically; no need to use Option or any other keys. Just type "#" - the normal number sign (aka "hash tag") and it gets converted to a sharp sign automatically.
In reply to Sharp signs in chord symbols… by Marc Sabatella
On several keyboard layouts # is not directly acessible and requires a key combination.
Such as Option for the o.p. or AltGr for me
In reply to On several keyboard layouts… by frfancha
@frfancha
in fact, in the chord abbreviations (es.: C#m) I have always done Option + # to insert a sharp but now with MS4 this key combination does not make me write the #. This is only in chord abbreviations because in all other written as staff text or system text the key combination works fine always giving me #
In reply to @frfancha in fact, in the… by Claudio Riffero
I see! Best to report this on GitHub so the developers can see it.
In reply to I see! Best to report this… by Marc Sabatella
@Marc Sabatella
I'm so sorry but I don't speak English and it's hard for me to communicate it to GitHub; I would be happy if someone did it for me. Thank you so much.
In reply to @Marc Sabatella I'm so sorry… by Claudio Riffero
You're doing fine with English here! Just put exactly the same information in the GitHub issue you put here, except maybe add that you are using a keyboard that requires Option to get the "#".
It's important that someone who actually experiences the problem be the one to report it, because then if the developers need to ask you questions in the comments on the issue, they can do so, and you will be notified.
In reply to You're doing fine with… by Marc Sabatella
Where is Git Hub?
I really hope someone better than me does.
... actually I have very little time for this.
In reply to Where is Github? by Claudio Riffero
The link is in the original beta announcement, but here it is again: https://github.com/musescore/MuseScore/issues
I understand having limited time - that's true for all of us. That's why it is so important that everyone do their own part in helping here - those who are experiencing an issue are always in the best position to report it. You already took the time to report the issue here, which is appreciated. But in the future, it would be better to take that same amount of time to post to GitHub instead.
Maybe someone else experiencing this can help in this case?
In reply to Sharp signs in chord symbols… by Marc Sabatella
@Marc Sabatella
I have to put C#m
after inserting in C I can't (option + #) insert the symbol on the keyboard #
With MS3.6.8. I've always done this (it's also in the manual)
In reply to @Marc Sabatella I have to… by Claudio Riffero
Please, someone "subscribed" to https://github.com/musescore/MuseScore/issues,
report this bug. Thank you.
In reply to Please, someone "subscribed"… by Claudio Riffero
I can do that for you then, you are welcome!
In reply to I can do that for you then,… by omegaboss805
Thank you! You are very kind
In reply to I can do that for you then,… by omegaboss805
@omegaboss805
...the same problem exists in writing the # in the Basso Continuo.
Grazie!
In reply to @omegaboss805 ...the same… by Claudio Riffero
Looks like a fix is on the way - covers a few other cases as well.
In reply to Looks like a fix is on the… by Marc Sabatella
Perfect!
Thank you!
In reply to Looks like a fix is on the… by Marc Sabatella
@Marc Sabatella
Will it already be solved in an upcoming Nightly?
In reply to Will it already be solved in… by Claudio Riffero
The PR fixing this was merged today, so yes, it should be in the next nightly build.
In reply to The PR fixing this was… by Marc Sabatella
@Marc Sabatella
Thank you, as always you are very kind
In reply to @Marc Sabatella Thank you,… by Claudio Riffero
@Marc Sabatella
With the latest Nightly problem solved!
Grazie!