Musescore 3.7 Evolution bugs
Hello Jojo. A bug, not present in previous versions, was somehow introduced in MU3.7.
In other versions, if we select the last note of a measure and press the keyboard shortcut of a longer duration, automatically the same note is generated tied in the next measure.
Example: Suppose in a 4/4 measure we have two half notes, C and D. If we select D and press 7 (shortcut to whole note) automatically another half note D appears in the next measure and already tied to the D at the previous measure.
Now, at the latest appimage builds of MU3.7, whenever I try to do this the program crashes.
Comments
Still works that way for me, on Windows 11 and a self built one
In reply to Still works that way for me by Jojo-Schmitz
Is it possible to find a hint of what's going on here?
In reply to Still works that way for me by Jojo-Schmitz
Have you tried the appimage?
Mine is the appimage in the latest kubuntu version.
In reply to Have you tried the appimage?… by fernandoamartin
I can't try the AppOmage, as I'm not using Linux.
One difference (on top of being a differet OS of course) is that the AppImage is using Qt 5.9, I doubt though this playing a role here
In reply to Have you tried the appimage?… by fernandoamartin
But feel free to report this on GitHub, https://github.com/Jojo-Schmitz/MuseScore/issues/new
Is there a fix for the small font tempo bug yet ?
![tempo.jpg]( "tempo.jpg")
I know the workaround is to change the font to Leyland.
In reply to Is there a fix for the small… by rothers
Is that a 3.7 bug or in 3.6.2 too?
Whatever: report on GitHub, see above
Edit: thanks for https://github.com/Jojo-Schmitz/MuseScore/issues/359
Today, just as an experiment, I delete all Musescore files from .config and .local/share, therefore erasing all user configurations and starting with a brand new config solved the issue. It may have been some corrupted configuration or some bug related to configurations that hits too rarely to be noticed.
In reply to Today, just as an experiment… by fernandoamartin
I guess with that we can close the issue. Until someone finds a way to reliably reproduce it
In reply to I guess with that we can… by Jojo-Schmitz
Hope it doesn't bother you, but right now I tried to extend a note in the 2nd voice (the green one) beyond the measure and it happened again. I also tried at the fourth voice (the pink one) and the same. However when doing so in the first voice (blue) everything is ok. Can you or anyone out there try it in a score with multiple voices and see if the same happens? It works at first voice but not in second and so forth.
In reply to Hope it doesn't bother you,… by fernandoamartin
Works in 3.6.2 Windows 10
This is due to:
https://github.com/Jojo-Schmitz/MuseScore/pull/315 backporting https://github.com/musescore/MuseScore/pull/21447.
Worked for 4.x but not in 3.x. Should either be reverted/removed or try to "reimplement" what the guy was trying to do.
In reply to This is due to: https:/… by worldwideweary
Great! You found the reason.
Now can you fix it Jojo?
In reply to Great! You found the reason… by fernandoamartin
I'll try
In reply to Great! You found the reason… by fernandoamartin
@worldwideweary is on it, see https://github.com/Jojo-Schmitz/MuseScore/pull/364