Lyric hyphen and melisma insertion not working on Estonian keyboard on Musescore 4.0.0 rev 5485621
Reported version
4.0
Type
Functional
Frequency
Few
Severity
S3 - Major
Reproducibility
Always
Status
GitHub issue
Regression
Yes
Workaround
Yes
Project
I have failed to insert hyphens and melismas between lyric syllibles while using the Estonian keyboard (which I need to use, since the lyrics include glyphs not available in the stock MacOS "international" keyboard). This was not an issue in Musescore 3. I have also tried binding the shortcut for both melismas and hyphens to be something completely different but that didn't work either.
Can't help but wonder if this is an issue on other keyboard layouts as well.
OS: macOS 11.5, Arch.: x86_64, MuseScore version (64-bit): 4.0.0-223472200, revision: 5485621
Comments
See also https://github.com/musescore/MuseScore/issues/14914 and https://github.com/musescore/MuseScore/issues/12601
As per the above links Japanese keyboards are affected too
And as per https://musescore.org/de/node/341608 German ones too (here the underscore is Shift+dash)
Workaround seems to be to use 2 underscores
I have the same problem with lyrics (Estonian keyboard). I have not found a solution via threads linked here. Alt+"-" gives me the hyphen and then I can move on to the next note/syllable by [space], but that way the "-" stays close to the first syllable and does not get situated beautifully between the syllables.
I have the same problem with Estonian keyboard on mac. I can not insert hyphens between syllables. The "-" key does nothing.
In reply to I have the same problem with… by allankasuk
A temporary solution: I switched my keyboard to an alternative one (from Mac Settings) and now it works. It's a bit annoying but at least I can have - between lyrics... 🤷🏼♀️
Hello! Unfortunately in MuseScore 4 a hyphen doesn't work, but it works good in MuseScore 3. But the file, created in 4 ver. doesn't open in 3 ver. So, you need to save file in xml formate, and then open it in 3rd version.
Hi
Sad to see that the issue still persists in Musescore 4.2, as it did a year ago.
OS: macOS 11.5, Arch.: x86_64, MuseScore version (64-bit): 4.2.0-233521125, revision: eb8d33c
Yes, the corresponding issues on GitHub are still open.
This issue tracker here though has been discontinied, so not much point to continue here...